How about using the <jar> element of the dependency?
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
Boris Ekelchik <[EMAIL PROTECTED]> wrote on 22/08/2003
09:27:27 AM:
> It's mentioned in JIRA MAVEN-349 issue, but still unresolved in the
current
> HEAD version.
>
> The problem is that webapp war file is generated without version in the
file
> name. So when you declare it as a "war" type dependency in the EAR
> project.xml, maven looks for a WAR artifact which has version number in
its
> file name and of course doesn't find it.
>
> From cvs HEAD:
>
> EJB:
> <j:set var="maven.ejb.final.name"
> value="${maven.build.dir}/${maven.final.name}.jar"/>
> ...
> <ant:jar jarfile="${maven.ejb.final.name}">
>
> EAR:
> <ant:ear destfile="${maven.build.dir}/${maven.final.name}.ear"
>
>
> WAR:
> <ant:property name="maven.war.final.name"
> value="${pom.artifactId}.war"/>
> ...
> <ant:jar
> destfile="${maven.war.build.dir}/${maven.war.final.name}"
> basedir="${maven.war.webapp.dir}"
> update="true"
> index="true">
>
> Would this be a workaround for now?
> <j:set var="maven.war.final.name"
> value="${maven.final.name}.war"/>
>
> Thanks
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
