You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bval.apache.org by "Senaka Fernando (JIRA)" <ji...@apache.org> on 2010/06/19 15:49:22 UTC
[jira] Updated: (BVAL-59) Write or reuse an scm-plugin mojo to
capture the svn revision
[ https://issues.apache.org/jira/browse/BVAL-59?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Senaka Fernando updated BVAL-59:
--------------------------------
Attachment: patch.out
Hi all,
The provided patch will add a new manifest header to the MANIFEST.MF file of the bval-core jar by the name Implementation-Build, which will contain the svn revision of the build. Also, the pom.properties file found inside META-INF/maven/org.apache.bval/bval-core/ contains the project's version. Therefore, the ant task would not be required.
Thanks,
Senaka.
> Write or reuse an scm-plugin mojo to capture the svn revision
> -------------------------------------------------------------
>
> Key: BVAL-59
> URL: https://issues.apache.org/jira/browse/BVAL-59
> Project: BeanValidation
> Issue Type: Improvement
> Components: build
> Affects Versions: 0.1-incubating
> Reporter: Donald Woods
> Priority: Minor
> Attachments: patch.out
>
>
> Suggested build improvement from David Jencks -
> I don't think its worth the trouble to use antrun to figure out the svn version. Maven already creates a property file that includes the project version. If anyone really wants this info, I'd hope they would write an scm-plugin mojo to do it.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.