Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [mdt-papyrus.dev] Papyrus JUnit feature Oxygen update site

Hi Peter. Yes, that's right. The Papyrus Oxygen releases p2 still contains the 3.0.0 version of the Nattable common plugin and the nightly contains the 4.0.0. Previously I was incorrectly assuming that the Nattable 3.0.0 *feature* (in the nightly p2) contained the 3.0.0 plugin, which is not the case. 

I do not know when the version was bumped, so maybe it did not happen before Oxygen.1 after all?

Since our release TP uses the Oxygen releases for the Papyrus SDK and the nightly for the Papyrus Oxygen Developer (which contains the Papyrus JUnit feature), the build fails as the JUnit feature tries unsuccessfully to resolve Nattable 4.0.0. 

So we could theoretically use the Oxygen nightly in our TP, but, for our "release" and "milestones" TP I would prefer that we have a more stable one, which is why I've asked Quentin to publish an integration update site.

--
Ernesto



On Wed, Oct 4, 2017 at 11:21 AM Peter Cigéhn <peter.cigehn@xxxxxxxxx> wrote:
Hi,

Maybe I do something wrong, but when checking with the Oomph Repository Explorer view, there still seem to be something strange. As Ernesto points out, when checking the Oxygen release (and staging) repo, the latest version of the org.eclipse.papyrus.infra.nattable.common bundle is still 3.0.0:

Inline images 1

But when checking the nightly build, it has been bumped to next major version:
Inline images 2

Not sure if this explains the issues that Ernesto have identified, that the dependency on version [4.0.0, 5.0.0) for this bundle cannot be resolved when using the SimRel repo for Oxygen. Sure, if the bumping of major version was made *after* the release of Oxygen.1, and that version 4.0.0 only exist for the nightly builds. But to my understanding the bumping of major version was made before the Oxygen.1 release (at least looking at when https://git.eclipse.org/r/#/c/102439/ was merged, which is the change that bumped the version also on the Oxygen maintenance branch).

How come that the version 4.0.0 of the org.eclipse.papyrus.infra.nattable.common bundle is not actually included in the Oxygen.1 release?

/Peter Cigéhn

On 4 October 2017 at 17:00, LE MENEZ Quentin <Quentin.LEMENEZ@xxxxxx> wrote:

Hi,

 

The main problem is, in this case, that your target depends on a nightly and a release. Of course I do not expect you to move to Photon but as there is no release of the dev tools along the main plugins and these progress with the related nightly (in this case oxygen 3.2.0 for SR2) I would advise you to change, for the time being, your papyrus to the Oxygen nightly.

Of course if that is preferable to you I could also push a milestone integration release (papyrus main plugins) for you to base yourself upon instead of the latest release.

 

As for Nattable, the required plugins are indeed in 4.0.0 (cf [1]) hence the feature should indeed have been changed to reflect this (major+1 in this case).

 

Quentin

 

[1] https://hudson.eclipse.org/papyrus/job/Papyrus-Oxygen/lastSuccessfulBuild/artifact/repository/plugins/

 

 

De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx] De la part de Ernesto Posse
Envoyé : mercredi 4 octobre 2017 16:44
À : Papyrus Project list <mdt-papyrus.dev@xxxxxxxxxxx>
Objet : Re: [mdt-papyrus.dev] Papyrus JUnit feature Oxygen update site

 

Hi, some more questions inline:

On Wed, Oct 4, 2017 at 3:24 AM LE MENEZ Quentin <Quentin.LEMENEZ@xxxxxx> wrote:

Hi Ernesto,

 

This job is not building against photon (Nattable backported the changes in the streams/3.0-maintenance) hence the dependency (nattable is now 4.0.0, even in oxygen ;p).

 

Huh. Well, that's confusing. Any other things that have been backported that we should be aware of?

 

As this feature is not supposed to be released, it is mainly used to run our tests and has some dev tools, there is no “backup”. If you are building against the released 3.1.0 you will have to depend on a local solution, or depend on the nightly. Although there are some talk about cleaning it up and releasing parts of it this is not done yet.

 

We are building against 3.1 now. At the moment there are no plans to move to Photon, so we need to still be able to do maintenance on Oxygen.

 

What is you TP and/or use of the dev tools ?

 

We use the Papyrus JUnit feature for tests, naturally, and we should not have to disable our tests from the build. Our (release) TP includes the following:

 

location "http://download.eclipse.org/modeling/mdt/papyrus/updates/releases/oxygen/" papyrus-release {

       org.eclipse.papyrus.sdk.feature.feature.group

}

 

location "https://hudson.eclipse.org/papyrus/job/Papyrus-Oxygen-Developer/lastSuccessfulBuild/artifact/repository/" eclipse-papyrus-developer-master {

       org.eclipse.papyrus.junit.feature.feature.group lazy

}

 

I see that http://download.eclipse.org/staging/oxygen has Papyrus 3.1 I've also looked at the milestones update sites for 3.x (e.g. http://download.eclipse.org/modeling/mdt/papyrus/updates/milestones/3.1/RC4/) but they all seem to have org.eclipse.papyrus.infra.nattable 3.0.0. I also looked at the Oxygen nightly (http://download.eclipse.org/modeling/mdt/papyrus/updates/nightly/oxygen which points to https://hudson.eclipse.org/papyrus/job/Papyrus-Oxygen/lastSuccessfulBuild/artifact/repository/features/) and it also seems to have nattable 3.0.0 as well. So, nattable was backported to the streams/3.0-maintenance branch but it is not being published in the milestones or nightly update sites? Where is it then?

 

Thanks,

 

--

Ernesto Posse

 

 

 

 

 

 

 

HTH,

Quentin

 

De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx] De la part de Ernesto Posse
Envoyé : mardi 3 octobre 2017 22:40
À : Papyrus Project list <mdt-papyrus.dev@xxxxxxxxxxx>
Objet : [mdt-papyrus.dev] Papyrus JUnit feature Oxygen update site

 

Hello. Is there a stable update site for the org.eclipse.papyrus.junit.feature? Currenlty I only find it in https://hudson.eclipse.org/papyrus/job/Papyrus-Oxygen-Developer/lastSuccessfulBuild/artifact/repository/, but apparently that job is building Papyrus Photon despite the name. 

 

We need the org.eclipse.papyrus.junit.feature for Oxygen for Papyrus-RT, but since our TP gets it from the URL above, our builds fail because the bundle found there requires Photon dependencies (like org.eclipse.papyrus.infra.nattable.common [4.0.0,5.0.0)). Where can we get the old Oxygen org.eclipse.papyrus.junit.feature?

 

Thanks

 

--

Ernesto Posse

Zeligsoft

 

 

--

Ernesto Posse

Zeligsoft

_______________________________________________
mdt-papyrus.dev mailing list
mdt-papyrus.dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev

--

Ernesto Posse

Zeligsoft


_______________________________________________
mdt-papyrus.dev mailing list
mdt-papyrus.dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev

_______________________________________________
mdt-papyrus.dev mailing list
mdt-papyrus.dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev
--
Ernesto Posse
Zeligsoft

Back to the top