Closed BillBrower closed 6 years ago
Hi Bill, thanks for giving spring content a try and thanks for the issue. We don't want to publish that parent POM to maven central so we replaced it with the standard spring-boot parent and properties.
You should be good now.
Just FYI. We are just about to publish a few more getting-started guides to demonstrate our renditions and fulltext search capabilities as well as show how integrations with AWS's NLP services are possible to help to categorize documents and improve search results even further. Stay tuned!
Anyways, let me know if this fixes your issue and we will close.
Hi Paul, thanks for getting back to me so fast! Where did you change it? I looked at the samples again but the last change was four days ago.
I updated the code for getting started examples Bill.
So are you following out getting started guides here and here? Or are you trying to use our examples here?
I originally thought you were following the getting started guides as they did reference spring-eg-content-commons
and that should not be fixed. If you git pull
you should see the latest. If you are using the examples then I think folks usually just git clone
the entire repo and import into their IDEs, or that is the intention anyways. We can update the docs to make that more clear if necessary. Let me know.
_Paul
Both. I tried following the getting started guides initially and added spring-content-fs-boot-starter
and spring-content-rest-boot-starter
to my pom file but I got this error when I tried to start my spring boot app:
java.lang.IllegalStateException: Failed to load ApplicationContext
.
.
.
Caused by: java.lang.NoSuchMethodError: org.springframework.data.web.config.HateoasAwareSpringDataWebConfiguration: method <init>()V not found
So I started looking at the examples because I figured the getting started guides must be missing some small config detail. Then I added spring-hateoas
to my pom file and added this config to my Application class:
@Configuration
@EnableFilesystemStores()
public static class AppConfig {}
to match the configuration in the examples but neither of those things fixed the error.
That hateoas error looks familiar and was due to different spring-boot versions. i.e. spring-content compiled against one version and the application using it spring-content trying to use another version. In my case though it was spring-content compiled against spring-boot 2 and the application using it attempting to use spring-boot 1.5.x.
The getting started guides should now be fixed. If you git pull
the gettingstarted-spring-content
repo you should see the references to spring-eg-content-commons
are now gone. Those changes are mirrored on the web too.
Let me know if you are still having an issue. Perhaps we can jump on slack or something?
I bet it is a version mismatch. We're on spring-boot 2.0.1.RELEASE
. I'd happy to jump on slack! Is there a dedicated slack for the project?
There is. It is spring-content
on cloudfoundry's slack. You can come and find us there.
But it is almost certainly that. The next release that is currently on master 0.1.0-SNAPSHOT will be our first 2.0 release. Should be out end of this week, or next.
Awesome, I'll upgrade when the next release comes out and let you know if I'm still having issues. Thanks Paul!
I'm following the examples for Spring Content Rest and Maven downloads
spring-content-fs-boot-starter
andspring-content-rest-boot-starter
just fine but it cannot find version0.0.1-SNAPSHOT
ofspring-eg-content-commons
[1] Could you upload it to the Central Repository?[1] https://search.maven.org/#search%7Cga%7C1%7Cspring-eg-content-commons