Ok cool. Thanks for the explanation. That said wouldn't it be nice that
we put all jelly tags in the mavenhome/lib so that plugin developers can
rely on having them already in the classpath? (I'm sure there must be a
reason for not doing so...) :-)

Thanks
-Vincent

> -----Original Message-----
> From: Brett Porter [mailto:[EMAIL PROTECTED]
> Sent: 15 June 2004 04:46
> To: Maven Developers List
> Subject: Re: cvs commit: maven-plugins/abbot project.xml
> 
> If it is used by the script it is always required. If you are getting
> different
> behaviour on HEAD and 1.0, it's possibly because of a different plugin
> installation set where one puts the tags into root for some reason.
> 
> - Brett
> 
> Quoting [EMAIL PROTECTED]:
> 
> > vmassol     2004/06/14 09:45:07
> >
> >   Modified:    abbot    project.xml
> >   Log:
> >   Added xml jelly tag dependeny as it seems to be required by maven
rc3
> (but
> > not by Maven 1.0 head).
> >
> >   Revision  Changes    Path
> >   1.3       +10 -1     maven-plugins/abbot/project.xml
> >
> >   Index: project.xml
> >
===================================================================
> >   RCS file: /home/cvs/maven-plugins/abbot/project.xml,v
> >   retrieving revision 1.2
> >   retrieving revision 1.3
> >   diff -u -r1.2 -r1.3
> >   --- project.xml   13 Jun 2004 10:08:38 -0000      1.2
> >   +++ project.xml   14 Jun 2004 16:45:07 -0000      1.3
> >   @@ -152,7 +152,16 @@
> >            <abbot.webstart>true</abbot.webstart>
> >          </properties>
> >        </dependency>
> >   -
> >   +
> >   +    <!-- Note: It seems this is required only by some versions of
> Maven
> >   +         (Maven rc3 for example). -->
> >   +    <dependency>
> >   +      <groupId>commons-jelly</groupId>
> >   +      <artifactId>commons-jelly-tags-xml</artifactId>
> >   +      <version>20030211.142705</version>
> >   +
<url>http://jakarta.apache.org/commons/jelly/libs/xml/</url>
> >   +    </dependency>
> >   +
> >      </dependencies>
> >      <reports>
> >        <report>maven-changes-plugin</report>
> >
> >
> >
> >
> >
---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to