-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix Maven issue #14
Comments
thanks for reporting! |
@BenRomberg |
@BenRomberg
I had some trouble getting the examples running with Maven. In particular I had to configure the Maven shade plugin as follows: <configuration>
<createDependencyReducedPom>false</createDependencyReducedPom>
<!-- http://stackoverflow.com/questions/29107376/jersey-problems-with-maven-shade-plugin -->
<transformers>
<transformer implementation="org.apache.maven.plugins.shade.resource.ServicesResourceTransformer" />
</transformers>
</configuration> See https://github.com/bbilger/jrestless-examples/blob/master/pom.xml#L48 Let me know if you have any issues with Maven. |
Thanks @bbilger, works as expected! |
jrestless sounds really promising. Unfortunately it's not straightforward to get it running with Maven.
With the following pom.xml:
The build results in
[ERROR] Failed to execute goal on project ***: Could not resolve dependencies for project ***: Could not find artifact org.glassfish.jersey.containers:project:jar:2.23 in jcenter (http://jcenter.bintray.com) -> [Help 1]
.The problem is that
org.glassfish.jersey.containers:project
is being referenced withincom.jrestless.core:jrestless-core-container
as a dependency. Maven then thinks this is a dependency of typejar
, where in fact it is of typepom
. When trying to download the correspondingjar
file, it gets a 404 from both jcenter and Maven Central and throws the error above.The following workaround fixes the issue:
It would be great if you could fix the dependencies to use
jersey-server
directly instead of relying on theproject
parent POM, so that the workaround is no longer needed in future versions. Thanks!The text was updated successfully, but these errors were encountered: