users@jersey.java.net

Re: New dependency for jersey-pom.xml

From: Joachim Martin <jmartin_at_path-works.com>
Date: Fri, 18 Jan 2008 18:18:52 -0500

FYI looks like asm 3.1 is incompatible with Spring 2.x.

As Paul mentions in his blog post at
http://blogs.sun.com/sandoz/entry/jersey_0_5_is_released,
referring to
http://weblogs.java.net/blog/mhadley/archive/2007/09/integrating_jer.html#36091
the SpringResourceConfigService works, with a small API change in
SpringProvider (new init()
in ResourceProvider).

You would specify SpringResourceConfigService instead of
PackagesResourceConfig and
also exclude asm/asm-3.1 from your jersey dependency:

        <dependency>
            <groupId>jersey</groupId>
            <artifactId>jersey</artifactId>
            <version>0.5-ea</version>
            <exclusions>
                <exclusion>
                    <artifactId>asm</artifactId>
                    <groupId>asm</groupId>
                </exclusion>
            </exclusions>
        </dependency>

Not sure if this breaks any other asm-based code in jersey however.

--Joachim
Joachim Martin wrote:
> I'd like to upgrade to 0.5 but I do not have a local maven repo to
> install 3.1 to for integration builds.
>
> I'm not sure what you mean by "referring" to asm 3.0 "because it is
> backwards compatible."
>
> Do we need 3.1 or 3.0? Or am I missing your point here?
>
> Best for me ;-) would be for you to push 3.1 up to the java.net repo.
>
> Thanks --Joachim
>
>
> Paul Sandoz 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 unsubscribe, e-mail: users-unsubscribe_at_jersey.dev.java.net
> For additional commands, e-mail: users-help_at_jersey.dev.java.net