[
http://jira.codehaus.org/browse/MOJO-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=151036#action_151036
]
Eric Ladouceur commented on MOJO-993:
-------------------------------------
I checked out the assembly code and added some traces. When execute() is
called, its MavenProject still contains the correct build number. So the build
number is not lost when the assembly plugin is executed. In my project POM, I
am overwriting the <finalName> of my jar by adding the buildnumber to it and
when AbstractAssemblyMojo.setFinalName(String) is called, I see 'null' where
the build number should be. So I guess the problem is inside Plexus or inside
DefaultPluginManager. I am trying to add some traces to those classes, but so
far I haven't been able to have my Maven install pick up my classes instead of
the original ones (I don't want to rebuild Maven entirely, just plugins...)
> ${buildNumber} or ${timestamp} evaluate as null in maven-assembly-plugin
> after created by buildnumber-maven-plugin
> ------------------------------------------------------------------------------------------------------------------
>
> Key: MOJO-993
> URL: http://jira.codehaus.org/browse/MOJO-993
> Project: Mojo
> Issue Type: Bug
> Components: buildnumber
> Environment: OS X 10.4.11
> Reporter: Ellen Strnod
>
> buildnumber plugin runs & logs [INFO] Storing buildNumber: 20080108-131808 at
> timestamp: 1199827088287, but during assembly plugin, the build number
> evaluates as "null" when used as part of the final name:
> <plugins>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-compiler-plugin</artifactId>
> <configuration>
> <source>${JDK_VERSION}</source>
> <target>${JDK_VERSION}</target>
> </configuration>
> </plugin>
>
> <plugin>
> <groupId>org.codehaus.mojo</groupId>
> <artifactId>buildnumber-maven-plugin</artifactId>
> <executions>
> <execution>
> <phase>validate</phase>
> <goals>
> <goal>create</goal>
> </goals>
> </execution>
> </executions>
> <configuration>
> <doCheck>false</doCheck>
> <doUpdate>false</doUpdate>
> <format>{0,date,yyyyMMdd-HHmmss}</format>
> <items>
> <item>timestamp</item>
> </items>
> </configuration>
> </plugin>
>
> <plugin>
> <artifactId>maven-assembly-plugin</artifactId>
> <executions>
> <execution>
> <phase>assembly:assembly</phase>
> </execution>
> </executions>
> <configuration>
> <finalName>${project.build.finalName}-${timestamp}</finalName>
> <descriptor>release.xml</descriptor>
> <outputDirectory>release</outputDirectory>
> <items>
> <item>timestamp</item>
> </items>
> </configuration>
> </plugin>
>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-surefire-plugin</artifactId>
> <configuration>
> <skip>true</skip>
> <testFailureIgnore>true</testFailureIgnore>
> <printSummary>false</printSummary>
> <excludes>
> <exclude>**/*.java</exclude>
> </excludes>
> </configuration>
> </plugin>
> </plugins>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
