Hi,
What about building gerrit against the last milestone?
And add only the dependencies that provide new required feature?
We can also create a Hudson job that use all the aggregation repositories
in order to check that everything is fine or not without impacting day to day development.
Regards,
Benoit
De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx]
De la part de Christian W. Damus
Envoyé : jeudi 21 janvier 2016 14:11
À : Papyrus Project list <mdt-papyrus.dev@xxxxxxxxxxx>
Objet : Re: [mdt-papyrus.dev] Oomph install error ?
Can we remove the CDT-dependent bits from the build until this issue is fixed? Or roll the POM back to the previous CDT milestone? We can’t have all of our Gerrit builds
failing because some unrelated component is misconfigured.
On 21 January, 2016 at 07:58:26, LETAVERNIER Camille (camille.letavernier@xxxxxx) wrote:
But...
I’ve updated *all* the repo’s from the release train,
and it seems that the extra build is now failing on the CDT dependency [1]
So Gerrit will still fail on the Master/Neon branch until this
is fixed (Mars is not affected)
[1]
https://hudson.eclipse.org/papyrus/job/Papyrus-Master-Extra/1973/
Camille
Hi,
The WTP update site has been fixed. I’ve updated to Oomph setup
as well as the pom dependencies, so the affected Gerrit builds should work again (Once rebased). Oomph should work as well
Regards,
Camille
The Papyrus PluginProjectEditor (oep.eclipse.project.editors) is already using this mechanism (javax.xml.transform package) for formatting a generated plugin.xml, so it would be
good to use the same for the properties as well.
Ansgar
On 19/01/2016 13:50, Christian Damus wrote:
On Jan 19, 2016, 07:18 -0500, LETAVERNIER Camille
<Camille.LETAVERNIER@xxxxxx>, wrote:
Hi,
It’s used in the EMF-To-XWT transformation to format the resulting
XML (in oep.customization.properties.xwt):
[ERROR] Cannot resolve project dependencies:
[ERROR] Software being installed: org.eclipse.papyrus.customization.feature.feature.group 1.2.0.qualifier
[ERROR] Missing requirement: org.eclipse.papyrus.customization.properties.model.xwt 1.2.0.qualifier requires 'bundle org.eclipse.wst.xml.core 1.1.0' but it could not be found
[ERROR] Cannot satisfy dependency: org.eclipse.papyrus.customization.feature.feature.group 1.2.0.qualifier
depends on: org.eclipse.papyrus.customization.properties.model.xwt 0.0.0
If there’s another XML Formatter available, we could remove
the WTP dependency (It would certainly be a bad idea to generate unformatted XML)
353761: [Property View - Customization] Generated XWT files
are not formatted
https://bugs.eclipse.org/bugs/show_bug.cgi?id=353761
Regards,
Camille
But, if we don't actually need WTP for Papyrus, then it shouldn't be in the setup. It's there now because when I first created the setup, the Papyrus build system (the POMs) had
it as a requirement. I don't know for which component.
On Jan 19, 2016, 06:52 -0500, LETAVERNIER Camille <Camille.LETAVERNIER@xxxxxx>, wrote:
Hi,
It seems that WTP removed their Neon M4 repository (Which is their latest stable version in the Neon Release Train).
So, not much we can do, the error is on their side
You can still use the Neon M4 update site instead:
http://download.eclipse.org/releases/neon
Camille
-----Message d'origine-----
De : mdt-papyrus.dev-bounces@xxxxxxxxxxx
[mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx] De la part de Cedric Dumoulin
Envoyé : mardi 19 janvier 2016 12:33
À : Papyrus Project list <mdt-papyrus.dev@xxxxxxxxxxx
Objet : [mdt-papyrus.dev] Oomph install error ?
Hi all,
I try to do a fresh install of Papyrus, but the oomph process fails
with the following error :
No repository found at
http://build.eclipse.org/webtools/committers/wtp-R3.8.0-I/20151215010029/S-3.8.0M4-20151215010029/repository/
This dependency is declared in the oomph model under "Papyrus Main
Dependencies".
However, I don't what should be the correct value, and how to correct it.
So my questions :
- Is it a problem from the oomph model or from my instalation ?
- What should be the correct value (and why papyrus depends on wtp ? :-) )
- How can we correct that ?
Thanks,
Cedric
_______________________________________________
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
_______________________________________________
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
--
Ansgar Radermacher CEA/DRT/DILS/LISE
http://www-list.cea.fr/index.htm
phone: +33 16908 3812
mailto: ansgar.radermacher@xxxxxx
_______________________________________________
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
|