If you want to build version 1.1.0, then put 1.1.0 in both the manifest and the pom.
Alex Hi Alex, The comparison problem is known to me – we have a plan, that final build will have change 1.0.0 -> 1.1.0. I am asking if there is configuration and how to configure to don’t have .RELEASE at the end of version. Think is that we will also produce builds with snapshots for our internal testing with SNAPSHOT, so I would like just have some think which will remove –SNAPSHOT maven build is some package face or another face if possible. Or is it possible to create build with snapshot but without version which contains snapshot? Thanks, Jan
Currently we have large project, with versioning using snapshots. MANIFEST.MF version – 1.0.0-SNAPSHOT Pom.xml version – 1.0.0. qualifier We are building normal builds with those SNAPSHOT/qualifier used, but our customer wants to have a final build, where is no SNAPSHOT/qualifier used. Is there easy way how to set those values to empty values – in best just by some profile configuration? You can change it to 1.0.0 and 1.0.0 in both places. However note that in OSGi 1.0.0 < 1.0.0.2014… so the empty value is the lowest such value and will not replace any prior builds. Spring use RELEASE as the qualifier and version, so 1.0.0.RELEASE in both places. Alternatively you could use versions such as 1.0.1 in your final release. _______________________________________________ tycho-user mailing list tycho-user@xxxxxxxxxxxhttps://dev.eclipse.org/mailman/listinfo/tycho-user
|