[
https://jira.jboss.org/jira/browse/JBBUILD-522?page=com.atlassian.jira.pl...
]
Paul Gier commented on JBBUILD-522:
-----------------------------------
Several of the properties, such as java version, os version, have been set in the AS trunk
build. The buildnumber maven plugin was used to get the SCM revision. The maven version
is now the only part that's missing from this.
[
MBUILDHELPER-9|http://jira.codehaus.org/browse/MBUILDHELPER-9] and
[
MNG-4112|http://jira.codehaus.org/browse/MNG-4112] have been created to resolve this
issue using various maven versions (2.0.x, 2.x, 3.x and later).
Set properties related to the build environment in jar.
-------------------------------------------------------
Key: JBBUILD-522
URL:
https://jira.jboss.org/jira/browse/JBBUILD-522
Project: JBoss Build System
Issue Type: Task
Components: Maven
Reporter: Paul Gier
Assignee: Paul Gier
Fix For: Maven Build - Maint 2009
It is useful to have details about the build environment contained in the maven
repository. Either in a text file or inside the deployed jar. The most practical way to
do this seems to be setting properties in the manifest that contains information about
java version, OS, maven version, and svn revision.
The java version and OS can be gathered from standard maven properties. The svn revision
can be set in a property using the buildnumber-maven-plugin. There currently does not
appear to be an easy way to record the version of maven that was used during the build.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira