[papyrus-rt-dev] Papyrus-RT Build TP Requires Oxygen Component

[Christian Damus <give.a.damus@xxxxxxxxx>]

Hi, Team,

Papyrus 0.8 (and 1.0) are intended to build and release on a Papyrus Neon.x base, as I understand it.  So, why do the Target Platform used by the build and our Oomph Setup model both use the Papyrus Developer Tools from the Oxygen stream for the JUnit framework?

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

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

}

I would expect this to be pulling the repository from the Papyrus-Neon-Developer build.  This actually broke both the developer environment and Gerrit builds for Papyrus-RT today, because of some churn in bundle versions on Papyrus master branch and the circular dependency problem that we have with this Papyrus Developer component.

Thanks,

Christian