Hi,
I have updated the
jersey/maven/jersey-pom.xml
to include:
<dependency>
<groupId>asm</groupId>
<artifactId>asm</artifactId>
<version>3.1</version>
</dependency>
I understand that is the minimum that is required.
I think there may be a bit of flexibility here and we could push the ASM
stuff out a little later, say end of next week, if maven users are
willing to do a manual install in the interim. It would be nice to give
the ASM guys a little bit more time rather than pushing something
temporarily to java.net.
Paul.
Paul Sandoz wrote:
> Aaron Anderson wrote:
>> 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.
>
> Me too.
>
>
>> 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.
>>
>
> I was wondering if that would be considered impolite in terms of Maven
> etiquette. I was advised that if we do this we should use a different
> groupId.
>
> My preference would be to not to do that but... i don't use Maven (yet!)
> and don't want to make it harder for the maven users...
>
> Paul.
>
--
| ? + ? = To question
----------------\
Paul Sandoz
x38109
+33-4-76188109