Eclipse Community Forums: Eclipse Platform » Version semantic of release for both eclipse and maven

Help

Home

Home » Eclipse Projects » Eclipse Platform » Version semantic of release for both eclipse and maven

Show: Today's Messages :: Show Polls :: Message Navigator

Version semantic of release for both eclipse and maven [message #1859267]

Thu, 25 May 2023 09:32

Didier Vojtisek

Messages: 31
Registered: July 2009

Member

Hi

For our developpements, we used to develop eclipse plugin using the .qualifier in all the plugins.

when using tycho, a 1.0.0.qualifier is mapped to 1.0.0-SNAPSHOT

so far so good, we used to deploy those plugins only via update site so we can let the .qualifier all the time.

However, we now wish to make most (or at least a significant subset) of the plugins available in maven central. (we compile each project twice with 2 different pom.xml, one for tycho and use in update site, and one for maven by reproducing the dependencies using only maven central jars)
when doing a release in maven central, this requires to remove the -SNAPSHOT in order to publish it.

But I'm not sure about the real semantic there since (correct me if I'm wrong)
for OSGI :
1.0.0 < 1.0.0.qualifier
and for maven :
1.0.0-SNAPSHOT < 1.0.0

Any suggestion about how to correctly change versions when doing a release ? (removing both the .qualifier/-SNAPSHOT ?, removing only -SNAPSHOT in non tycho version ? , replacing .qualifier/-SNAPSHOT by a fixed buildID everywhere ? ....)
How other project achieve that ?

thanks

[Updated on: Thu, 25 May 2023 09:32]

Report message to a moderator

Re: Version semantic of release for both eclipse and maven [message #1859293 is a reply to message #1859267]

Sat, 27 May 2023 06:07

Ed Merks

Messages: 33227
Registered: July 2009

Senior Member

Yes you are right about the strange version ordering. I'm not sure how everyone else is publishing to Maven. There seem to be different ways. But one thing to note is that you can take the jar that is using the .qualifier expanded name and publish that to Maven just by renaming it.

You can look here how the platform does it:

https://github.com/eclipse-platform/eclipse.platform.releng/tree/master/publish-to-maven-central

They use the CBI aggregator to read a p2 repository and write it as a Maven-compatible repository:

https://github.com/eclipse-platform/eclipse.platform.releng/blob/master/publish-to-maven-central/SDK4Mvn.aggr

The scripts being used are there too.

The jobs that do the work are here:

https://ci.eclipse.org/releng/view/Publish%20to%20Maven/

But I don't think you can read the details without a login...

Ed Merks
Professional Support: https://www.macromodeling.com/

Report message to a moderator

Previous Topic:	IDE Core Dump after glib/webgtk update
Next Topic:	Launching Help from RCP application on macOS

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Mon Oct 14 21:12:21 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter