or autogenerate the content so that it does not break so regularly?
Anything referencing an explicit milestone is just about guaranteed to be broken within 3 months, certainly within a year.
Regards
Ed Willink
On 15/06/2015 14:41, LETAVERNIER Camille wrote:
Hi,
All POMs are configured to use this update site:
<repository>
<id>mdt-ocl</id>
<layout>p2</layout>
<!-- updateFrom("MDT OCL 6.0",0) -->
<url>http://download.eclipse.org/modeling/mdt/ocl/updates/milestones/6.0.0/S201506090403</url>
</repository>
And I’ve had the same error when building Papyrus locally (“Main” and “Extra” I think, but tests were OK), after cleaning my local Maven repository
Also, Eclipse seems to work fine for Main, Extra and Main-Tests (Failing on Extra-Tests for a different mysterious reason)
Ø
However Eclipse projects are prohibited from premature release so you probably shouldn't be trying to install it.
Well, that doesn’t really apply to “building” and “testing”. It’s mostly a matter of communication and “making artifacts visible”.
Camille
On 15/06/2015 12:50, LE FEVRE FRANCOIS wrote:
Hi
That is OCL RC2. The OCL retention policy is two milestones, and in preparation for Mars release dead milestones have been pruned. You should be accessing RC3 or RC4 from milestones or the true release from releases. However Eclipse projects are prohibited
from premature release so you probably shouldn't be trying to install it.
It would appear that the Papyrus maven artefacts are stale.
Regards
Ed Willink
_______________________________________________
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
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2015.0.6030 / Virus Database: 4360/10019 - Release Date: 06/15/15