[
https://issues.apache.org/jira/browse/UIMA-3272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13774653#comment-13774653
]
Marshall Schor commented on UIMA-3272:
--------------------------------------
Seems Maven has a built-in variable for the timestamp:
http://maven.apache.org/guides/introduction/introduction-to-the-pom.html#Available%5FVariables
so that's a start.
We set the final-name in the <build> for some jars, and that's used when the
Jar is generated, but I also know when Maven uploads this to the local .m2
repository, it changes the name to make it more conform to the Maven naming
conventions. May take some investigations to get this to be carried along in
.m2 and other deploys.
> Add timestamp to Eclipse plugin versions
> ----------------------------------------
>
> Key: UIMA-3272
> URL: https://issues.apache.org/jira/browse/UIMA-3272
> Project: UIMA
> Issue Type: Improvement
> Components: Eclipse plugins, ruta
> Reporter: Richard Eckart de Castilho
>
> When we do release candidates, we can currently not upgrade an Eclipse from
> one candidate to the next one from the update site, because the version does
> not change. Many Eclipse bundles bear an additional timestamp after the
> version. It would be great to have this as well for our plugin to facilitate
> RC testing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
