It would be best if the ASM project updated the central repositories themselves with their latest release. I sent an email to their mailing list requesting that they do so. If this does not happen before Friday then the Jersey ANT build script can be modified to temporarily add the ASM release along with the jersey jar to the java.net repository.
Speaking of dependencies, how about the localizer.jar? I don't see it listed as a dependency any more but it is still in the Jersey lib directory in the trunk and the Localizer classes are still referenced in the javax.ws.rs.core.ApiMessages class in the JSR 311 0.5 API. Shouldn't references to these seemingly implementation specific classes be removed from the JSR API? localizer.jar is not in any maven repository yet so that may need to be added as well.
Regards,
Aaron
Paul Sandoz <Paul.Sandoz_at_Sun.COM> wrote: Hi,
https://jersey.dev.java.net/source/browse/*checkout*/jersey/trunk/jersey/docs/dependencies.html
The core runtime dependencies of from 0.4 to 0.5 have changed. There is
now a dependency on the asm-3.1.jar (i just upgraded from asm-3.0.jar).
For the 0.5 release this Friday we need to update the
maven/jersey-pom.xml file. I am not sure which repository to use to get
the asm jar.
I could use the repo at apache [1], but it only contains up to the 3.0
version (although we could refer to that for the pom as it is backwards
compatible, but i don't like that...).
Or alternatively we could push the asm jars to the java.net repository.
That seems the more expedient approach.
Any advice would be welcome on the best approach to take.
Thanks,
Paul.
[1]
http://repo1.maven.org/maven2/asm/asm/
--
| ? + ? = To question
----------------\
Paul Sandoz
x38109
+33-4-76188109
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_jersey.dev.java.net
For additional commands, e-mail: dev-help_at_jersey.dev.java.net
---------------------------------
Looking for last minute shopping deals? Find them fast with Yahoo! Search.