> Is the dep.type check here really necessary? If the user has added the
> war.bundle property, then I say let it go in there. It could be an
> ejb-client jar file in which case the <type> may not be jar.
>
> > - <ant:lib dir="${maven.repo.local}/${dep.
> > artifactDirectory}/jars/">
> > - <ant:include name="${dep.artifact}"/>
> > + <j:if test="${dep.getProperty('war.bundle')=='true' and
> > dep.type =='jar'}">
> Ditto.
>
For the moment only jars can go into war.
I made this type-sensitive bundling while I was planning
to support also other types of artifacts (e.g. "tld").
Those artifacts sometimes should be bundled is a different way and in some
cases won't go to WEB-INF\lib.
I hope that more complex artifact like "webcomponent" (e.g collection of
css, js, images) will be supported in near feature.
If you feel that current implementation is to strict we can change it.
BTW: It will be nice to have selectors of artifact
Pom.getArtifcats("jar", "war.bundle")
Will return all jars which should be bundled in the war.
Michal
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
