[
http://jira.codehaus.org/browse/CONTINUUM-581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_121924
]
Geert Pante commented on CONTINUUM-581:
---------------------------------------
I noticed in the debug log, the following command line for a simple maven2
build:
/usr/local/maven2/bin/mvn --batch-mode --non-recursive
-Dcontinuum.project.lastBuild.state=10 -Dcontinuum.project.nextBuild.number=1
"-Dcontinuum.project.group.name=Tst Base Pom"
-Dcontinuum.project.lastBuild.number=0 clean install'
So you have at least:
continuum.project.lastBuild.number
continuum.project.nextBuild.number
continuum.project.lastBuild.state
continuum.project.group.name
> Share continuum build number to underlying build project
> --------------------------------------------------------
>
> Key: CONTINUUM-581
> URL: http://jira.codehaus.org/browse/CONTINUUM-581
> Project: Continuum
> Issue Type: New Feature
> Components: Core system
> Reporter: Alex Boisvert
> Fix For: Future
>
>
> It would be nice if Continuum shared its build number with the underlying
> build projects (e.g. Ant/Maven{1,2})
> What I'm trying to do is generate artifacts with the following naming
> convention:
> myproject-1.0-123.zip
> where 1.0 is the version number defined in Maven (e.g. pom.xml), and 123
> is the Continuum build number. Artifacts could be .zip, .jar, .war, etc.
> I guess one way to do this is to pass the build number via an environment
> variable
--
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
