Community
Participate
Working Groups
Each time you open the preference dialog the first time in a new Papyrus instance (or each time you start a new Papyrus instance in case you use an Oomph based installation), a warning is logged in the error log: org.eclipse.ui Warning Tue May 16 13:57:59 CEST 2017 Invalid preference category path: org.eclipse.papyrus.infra.properties.ui.propertyview (bundle: org.eclipse.papyrus.uml.properties, page: org.eclipse.papyrus.uml.properties.multiplicityEditorProperties)
This is happening when using the latest nightly build of Papyrus Oxygen.
New Gerrit change created: https://git.eclipse.org/r/101186
*** Bug 519599 has been marked as a duplicate of this bug. ***
Gerrit change https://git.eclipse.org/r/101186 was merged to [master]. Commit: http://git.eclipse.org/c/papyrus/org.eclipse.papyrus.git/commit/?id=c33ad8357629c224ffb015c6e81df9e1dde64501
New Gerrit change created: https://git.eclipse.org/r/101618
Gerrit change https://git.eclipse.org/r/101618 was merged to [streams/3.0-maintenance]. Commit: http://git.eclipse.org/c/papyrus/org.eclipse.papyrus.git/commit/?id=9403e2c6658b6e731e5f36e88dc0a5573e380aca
Thx Géry for the patch. It will be available for Oxygen.1
I have tried to test this on the Photon track, but there seem to be something strange going on with the p2 repos. When checking the contents of http://download.eclipse.org/modeling/mdt/papyrus/updates/nightly/photon/ which I assume is the "right" p2 repo to use for the nightly builds, the version of the org.eclipse.papyrus.uml.properties bundle has the version 3.0.0.201707191432. But when checking the latest build on Hudson, https://hudson.eclipse.org/papyrus/job/Papyrus-Master/3925/artifact/repository/ the version of the same bundle is 3.0.0.201707200958. Aren't http://download.eclipse.org/modeling/mdt/papyrus/updates/nightly/photon/ supposed to be updated with the latest build? Or is it some delay or some separate build that performs the copy?
Papyrus-RT has a dependency on this bug and we would like to know in which Papyrus release we can find the fix so we can verify whether it also fixes the problem in Papyrus-RT (no target milestone is set for this bug at the time this comment was made...).
(In reply to Peter Cigehn from comment #8) > I have tried to test this on the Photon track, but there seem to be > something strange going on with the p2 repos. When checking the contents of > http://download.eclipse.org/modeling/mdt/papyrus/updates/nightly/photon/ > which I assume is the "right" p2 repo to use for the nightly builds, the > version of the org.eclipse.papyrus.uml.properties bundle has the version > 3.0.0.201707191432. > > But when checking the latest build on Hudson, > https://hudson.eclipse.org/papyrus/job/Papyrus-Master/3925/artifact/ > repository/ the version of the same bundle is 3.0.0.201707200958. > > Aren't > http://download.eclipse.org/modeling/mdt/papyrus/updates/nightly/photon/ > supposed to be updated with the latest build? Or is it some delay or some > separate build that performs the copy? It seem like the same issue exist for the Oxygen track. When trying to update my Payrus installation based on the Oxygen nightly I don't get the latest build. When checking http://download.eclipse.org/modeling/mdt/papyrus/updates/nightly/oxygen/ you actually have exactly the same version as for Photon, i.e. 3.0.0.201707191432. Something strange is going on here... I guess I have to pull the build result directly from Hudson instead to be able to test this... :(
(In reply to Benoit Maggi from comment #7) > Thx Géry for the patch. > It will be available for Oxygen.1 (In reply to Charles Rivet from comment #9) > Papyrus-RT has a dependency on this bug and we would like to know in which > Papyrus release we can find the fix so we can verify whether it also fixes > the problem in Papyrus-RT (no target milestone is set for this bug at the > time this comment was made...). I guess as Benoit already indicated, the fix will be available in Oxygen.1
(In reply to Peter Cigehn from comment #11) > (In reply to Benoit Maggi from comment #7) > > Thx Géry for the patch. > > It will be available for Oxygen.1 > > (In reply to Charles Rivet from comment #9) > > Papyrus-RT has a dependency on this bug and we would like to know in which > > Papyrus release we can find the fix so we can verify whether it also fixes > > the problem in Papyrus-RT (no target milestone is set for this bug at the > > time this comment was made...). > > I guess as Benoit already indicated, the fix will be available in Oxygen.1 That's a good guess, but it's a pain to have to read all the comments to discover this - especially since a field is provided for that information...and especially since this bug is marked as "Closed Fixed"...
(In reply to Charles Rivet from comment #12) > (In reply to Peter Cigehn from comment #11) > > (In reply to Benoit Maggi from comment #7) > > > Thx Géry for the patch. > > > It will be available for Oxygen.1 > > > > (In reply to Charles Rivet from comment #9) > > > Papyrus-RT has a dependency on this bug and we would like to know in which > > > Papyrus release we can find the fix so we can verify whether it also fixes > > > the problem in Papyrus-RT (no target milestone is set for this bug at the > > > time this comment was made...). > > > > I guess as Benoit already indicated, the fix will be available in Oxygen.1 > > That's a good guess, but it's a pain to have to read all the comments to > discover this - especially since a field is provided for that > information...and especially since this bug is marked as "Closed Fixed"... @Charles: I just added the comment to help the user, I can also keep the bug open/assigned for 5 years like it was done before... To set the target milestone, I need you know what number will be the next version. As this email indicate, I have no clue of the next version number neither of the branch strategy https://dev.eclipse.org/mhonarc/lists/mdt-papyrus.dev/msg04018.html You may ask that directly to the Pic architecture committee :) => I would be happy to see a the answer on the mailing list or on a wiki page.
(In reply to Peter Cigehn from comment #10) > (In reply to Peter Cigehn from comment #8) > > I have tried to test this on the Photon track, but there seem to be > > something strange going on with the p2 repos. When checking the contents of > > http://download.eclipse.org/modeling/mdt/papyrus/updates/nightly/photon/ > > which I assume is the "right" p2 repo to use for the nightly builds, the > > version of the org.eclipse.papyrus.uml.properties bundle has the version > > 3.0.0.201707191432. > > > > But when checking the latest build on Hudson, > > https://hudson.eclipse.org/papyrus/job/Papyrus-Master/3925/artifact/ > > repository/ the version of the same bundle is 3.0.0.201707200958. > > > > Aren't > > http://download.eclipse.org/modeling/mdt/papyrus/updates/nightly/photon/ > > supposed to be updated with the latest build? Or is it some delay or some > > separate build that performs the copy? > > It seem like the same issue exist for the Oxygen track. When trying to > update my Payrus installation based on the Oxygen nightly I don't get the > latest build. > > When checking > http://download.eclipse.org/modeling/mdt/papyrus/updates/nightly/oxygen/ you > actually have exactly the same version as for Photon, i.e. > 3.0.0.201707191432. Something strange is going on here... > > I guess I have to pull the build result directly from Hudson instead to be > able to test this... :( After updating my Oomph setup file for my Papyrus installation to use the repos directly on Hudson instead, i.e. https://hudson.eclipse.org/papyrus/job/Papyrus-Master/lastSuccessfulBuild/artifact/repository/ respectively https://hudson.eclipse.org/papyrus/job/Papyrus-Oxygen/lastSuccessfulBuild/artifact/repository/ to ensure that I get the correct and latest result, I can now verify that the warning is no longer logged when opening the preference dialog. To pity that you cannot trust the "correct" repos anymore, i.e. http://download.eclipse.org/modeling/mdt/papyrus/updates/nightly/photon/ and http://download.eclipse.org/modeling/mdt/papyrus/updates/nightly/oxygen/ I raised a question on the developer mailing list regarding this, see https://dev.eclipse.org/mhonarc/lists/mdt-papyrus.dev/msg04038.html Well, all of these p2 repo issues are out of the scope for this specific bug anyway... :)
(In reply to Benoit Maggi from comment #13) > (In reply to Charles Rivet from comment #12) > > (In reply to Peter Cigehn from comment #11) > > > (In reply to Benoit Maggi from comment #7) > > > > Thx Géry for the patch. > > > > It will be available for Oxygen.1 > > > > > > (In reply to Charles Rivet from comment #9) > > > > Papyrus-RT has a dependency on this bug and we would like to know in which > > > > Papyrus release we can find the fix so we can verify whether it also fixes > > > > the problem in Papyrus-RT (no target milestone is set for this bug at the > > > > time this comment was made...). > > > > > > I guess as Benoit already indicated, the fix will be available in Oxygen.1 > > > > That's a good guess, but it's a pain to have to read all the comments to > > discover this - especially since a field is provided for that > > information...and especially since this bug is marked as "Closed Fixed"... > > @Charles: I just added the comment to help the user, I can also keep the bug > open/assigned for 5 years like it was done before... > > To set the target milestone, I need you know what number will be the next > version. > As this email indicate, I have no clue of the next version number neither of > the branch strategy > https://dev.eclipse.org/mhonarc/lists/mdt-papyrus.dev/msg04018.html > > You may ask that directly to the Pic architecture committee :) > => I would be happy to see a the answer on the mailing list or on a wiki > page. Thanks Benoit. I'll just mark it as "future" on the Papyrus-RT side. I'll bring this up to the Papyrus IC Product Management Committee's attention.
