maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From d...@multitask.com.au
Subject Re: maven.final.name
Date Tue, 26 Aug 2003 02:34:52 GMT
The plugin defines it's own variable. But it's held within it's scope.
--
dIon Gillard, Multitask Consulting
Blog:      http://blogs.codehaus.org/people/dion/


Leo Sutic <leosutic@apache.org> wrote on 26/08/2003 02:07:20 AM:

> When defining a postGoal to jar:jar, I expect the maven.final.name
> variable to point to the recently-created jar file. This is correct when
> jar:jar is invoked directly, but not when it is invoked via 
jar:snapshot.
> jar:snapshot does a <j:set/> of maven.final.name to snapshotSignature.
> However, that j:set is lost to the postGoal.
> 
>   <postGoal name="jar:jar">
>         <ant:echo message="Jar just created: ${maven.final.name}.jar"/>
>     </postGoal>
> 
> log output:
> 
>     jar:snapshot:
>         [echo] Building snapshot JAR:
> commons-attributes-unittest-20030823.185627
>     java:prepare-filesystem:
> 
>     java:compile:
> 
>         .
>         .
>         .
>     jar:jar:
>         [jar] Building jar:
> C:\Home\leo\Private\Apache\jakarta-commons-sandbox\attri
> butes\unittest\target\commons-attributes-unittest-20030823.185627.jar
>         [echo] Jar just created: 
commons-attributes-unittest-2.0alpha.jar
> 
> Question:
> 
>  1. Is this on purpose or is it a bug?
> 
>  2. Is there any other way to get athe name of the jar just created from 
a
> postGoal to jar:jar?
> 
> /LS
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
> 

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message