Gradle could not find the loaded dependency packaged as an OSGi package (non-OSGi application)

(Edited for clarification)

My (non-OSGi) application build is in Gradle, and I'm trying to upgrade from a very old version of Jersey (1.1.4.1) to something much newer (1.12?). I do not pretend to know about using OSGi. But when I specify my Gradle dependencies (with $JERSEY_VERSIONset to "1.12"):

[group: 'com.sun.jersey', name: 'jersey-server', version: "$JERSEY_VERSION"]

it loads jersey-server-1.12.jar into my Gradle dependency cache in the bundles directory, and not in the regular jars directory, and then Gradle does not seem to include this jar in its classpath, for example it would, if it were under the "jars" subdirectory.

I found that he fell under the "bundles" because the POM designated him as a jar with OSGi support. I do not think that we will want OSGi-ify of our project. Am I stuck with older versions of Jersey, or is there anything else I can do to get Gradle to see a jersey jar? I would prefer not to manually copy the file to the local repo, if possible, but somehow it depends on the Gradle dependency management capabilities, if it depends on the task.

+3
source share
2 answers

' : 1.1.4.1 1.12, POM , jersey-core.jar . jersey-core.jar . , , jersey-server.jar , ClassNotFoundException , jersey-core.jar.

0

OSGi - . OSGi, . , ?

0

All Articles