You are viewing a plain text version of this content. The canonical link for it is here.

Posted to users@maven.apache.org by Chris Butler <cb...@mateso.com> on 2003/02/25 19:14:05 UTC

maven beta-8 - not all jelly jars in $MAVEN_HOME/lib

We've got a non-trivial maven.xml.  Some namespaces defined.
Little bits of jelly scripting here and there.

Why didn't all jelly tag libraries get included in the /lib
directory for the new maven beta-8?   I think many are missing.
I'm seeing a lot of org.apache.commons.jelly.tags.X 
classNotFoundExceptions...

Granted, in the 9/30/2002 jelly-SNAPSHOT, everything was included
in the single jar file, but I would think that all nec. jelly jars
would be included in the maven release for beta-8.  

Is there a jar that contains them all now?  
If not, how bout putting subjars in /lib for the beta-8 release?

Jars missing (for me anyway):
- common-jelly-tags-xml
- common-jelly-tags-velocity
- common-jelly-tags-log

Am I just missing something basic here?

chris

Re: maven beta-8 - not all jelly jars in $MAVEN_HOME/lib

Posted by Colin Sampaleanu <co...@exis.com>.

Chris Butler wrote:

>We've got a non-trivial maven.xml.  Some namespaces defined.
>Little bits of jelly scripting here and there.
>
>Why didn't all jelly tag libraries get included in the /lib
>directory for the new maven beta-8?   I think many are missing.
>I'm seeing a lot of org.apache.commons.jelly.tags.X 
>classNotFoundExceptions...
>
>Granted, in the 9/30/2002 jelly-SNAPSHOT, everything was included
>in the single jar file, but I would think that all nec. jelly jars
>would be included in the maven release for beta-8.  
>
>Is there a jar that contains them all now?  
>If not, how bout putting subjars in /lib for the beta-8 release?
>
>Jars missing (for me anyway):
>- common-jelly-tags-xml
>- common-jelly-tags-velocity
>- common-jelly-tags-log
>
>Am I just missing something basic here?
>  
>
Yes, these aren't needed for maven itself, so they are not included by 
default. This speeds things up for people who have no need for them 
(they don't have to make the base maven distro larger, or force a 
download from the repo when they are not used).

Just add them as dependencies, same as any other dependencies.