Although I agree with you about that being the more common way, I had trouble with tooling before when I did that.
It turns out that the code in Maven's build helper that converts Maven conventions to OSGi conventions (which is supposed to switch the "-" to a ".") only switched the first one. The result was that the build framework that generated the MD5 and sha1 signatures (and maybe others too), would generated signatures that were named ... 3.0.0.alpha-02, (it switched the 1st one, not the second, from a "-" to a ".") while the eclipse packaging for P2 update sites converted the version to 3.0.0.alpha.02 (switching both of them). This resulted in a ping from Henk saying we didn't have signatures that matched, etc., and Jira https://issues.apache.org/jira/browse/UIMA-5285 Maybe there's a better way to fix this... -Marshall On 2/14/2017 6:22 AM, Richard Eckart de Castilho wrote: >> On 14.02.2017, at 04:48, Marshall Schor <[email protected]> wrote: >> >> The SVN tag is here: >> https://svn.apache.org/repos/asf/uima/uimaj/tags/uimaj-3.0.0-alpha02/ > Just a generic feedback at this point: I think the version should be > "3.0.0-alpha-02" > instead of "3.0.0-alpha02". Having the additional dash before the numeric > suffix seems to be the common way to do it: > > - > http://books.sonatype.com/mvnref-book/reference/pom-relationships-sect-pom-syntax.html > - > https://docs.oracle.com/middleware/1212/core/MAVEN/maven_version.htm#MAVEN8855 > > Cheers, > > -- Richard > > >
