You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Stuart James Penrose (JIRA)" <ji...@codehaus.org> on 2006/10/17 19:59:54 UTC
[jira] Commented: (CONTINUUM-581) Share continuum build number to
underlying build project
[ http://jira.codehaus.org/browse/CONTINUUM-581?page=comments#action_77884 ]
Stuart James Penrose commented on CONTINUUM-581:
------------------------------------------------
My main use of continuum is with maven2 projects. For my uses it would be nice if continuum created a 'build.properties' file or something similar in every jar/war/ear it creates that has this sort of build-specific information. SCM versioning information would be great here too (sorry, maybe that's beyond the scope of this issue). It's practically a necessity to have this sort of information when tracking builds and relating them to everything else in our environment: build xyz built on xxx-xx-xx from rev xxxx of svn://host/branch.
> 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
> Reporter: Alex Boisvert
> Fix For: 1.1
>
>
> 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