[
https://issues.apache.org/jira/browse/UIMA-3272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13775639#comment-13775639
]
Marshall Schor commented on UIMA-3272:
--------------------------------------
I was able to change the <build> <finalName> element to
${project.artifactId}_${parsedVersion.osgiVersion}.v${maven.build.timestamp}
for Eclipse plugin building. This had the expected result in /target.
However, as previously noticed, the "install" into the .m2 repo dropped the
v190923_1258 timestamp part.
I can get the timestamp to go along with deploy if I set it as the artifact
"classifier". However the separator is "-" rather than ".".
Also, the references to this artifact now have to include the classifier. So
for instance, the eclipse-update-site build, which has a section to copy the
artifacts into the toBePacked directory, would need changing every run, to
specify the classifier.
So, I'm stuck on how to do this in the Maven environment. Suggestions welcome
:-)
> 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
