Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [] Colliding version numbers between Oxygen and Photon?



Today I bumped into exactly the same issue once again, and I ended up with a non-working installation for the Oxygen track (since it incorrectly got the Photon version). When looking a bit closer I can see that the time triggered build for both Oxygen as well as Photon happens at exactly 21:43. Could someone be so kind to at least make sure that the time triggered (periodic) builds at least happens at different times to avoid this version number conflict?


This would at least reduce the risk of conflicts like this.


/Peter Cigéhn


From: [] On Behalf Of Cigehn Peter
Sent: den 27 oktober 2017 16:38
Subject: [] Colliding version numbers between Oxygen and Photon?




I have had ”random” issues with my installations of nightly builds for Papyrus Oxygen and Papyrus Photon which have puzzled me for quite some time. I use an own made Oomph setup file and use the Eclipse Installer to manage my installations of nightly builds. And thus I also use a shared p2 bundle pool.


The problem is that from time to time, the UML architecture context gets “lost”, i.e. when trying to create a new model the list of available architecture contexts is empty. Apart from that it also impacts other things like empty palettes in the diagram editors and so on.


When checking a bit closer with the OSGi console I can see the following (in my Oxygen installation):


osgi> lb -s org.eclipse.papyrus.uml.architecture


   ID|State      |Level|Symbolic name

  522|Installed  |    4|org.eclipse.papyrus.uml.architecture (


The bundle is installed but not started. When trying to start it, the following happens:


osgi> start 522

gogo: BundleException: Could not resolve module: org.eclipse.papyrus.uml.architecture [522]

  Unresolved requirement: Require-Bundle: org.eclipse.papyrus.uml.diagram.sequence; bundle-version="[5.0.0,6.0.0)"


This is kind of strange, since this bundle is only 4.0.0


osgi> lb -s org.eclipse.papyrus.uml.diagram.sequence


   ID|State      |Level|Symbolic name

  549|Active     |    4|org.eclipse.papyrus.uml.diagram.sequence (


When checking a bit closer, it turns out that, for the latest nightly builds of both Papyrus Oxygen and Papyrus Photon, the version, including the qualifier, is identical for this plugin, i.e. they both have the version 1.1.0 with the same time stamp 201710270144.


This in its turn I guess causes the shared p2 bundle pool to become a bit confused, and it manages to install the Photon version of the org.eclipse.papyrus.uml.architecture bundle into the Oxygen installation, thus causing the bundle to never load to the unresolved requirement.


When analyzing the bundle pool with the Eclipse Installer, one can indeed see the same version of the bundle being installed in both my Oxygen and my Photon installation:


I am not sure why the time stamps are identical, i.e. both 201710270144. Is a time triggered build that happens *exactly* the same time for both Oxygen and Photon that causes this? Most of the time the time stamps are different, when triggered by commit on its respective branch.


Should the org.eclipse.papyrus.uml.architecture bundle really have version 1.1.0 for both Oxygen and Photon, when it actually have different content and different dependencies with different version ranges?


Or is this just a flaw with how the shared p2 bundle pool in the Eclipse Installer works?


/Peter Cigéhn

Back to the top