Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [papyrus-rt-dev] Neon.3 and EMF Compare
After a bit of detective work, I realized that the problem seems to be that our 'milestones' and 'release' target platforms use the following update site for EMF Compare: "http://download.eclipse.org/modeling/emf/compare/updates/logical/emf.compare/integration/" which contains EMF Compare 3.3.0.201610271310 while the 'nightly' target platform uses "http://download.eclipse.org/modeling/emf/compare/updates/logical/emf.compare/nightly/latest/" which contains EMF Compare 3.5.0.2017MMDDBBBB. 

So the question is what do we do for our build, both the milestones and the release. @Philip if Papyrus-RT is depending on EMF Compare 3.5 from the nightly update site, are you moving it to the milestones update site?

--
Ernesto Posse
Zeligsoft


On Mon, Mar 20, 2017 at 6:36 PM Ernesto Posse <eposse@xxxxxxxxxxxxx> wrote:
Hello team. We are updating our build jobs to use the milestones target platform, and when doing this we realized that our milestones target definition relied on the Eclipse Neon releases update site ("http://download.eclipse.org/releases/neon/") which needs to be updated to the Eclipse Neon staging update site ("http://download.eclipse.org/staging/neon/"). When doing this and trigger the build we get unstable builds, and in particular we get errors related to the Compare feature. See the Gerrit-Core build #424 (https://hudson.eclipse.org/papyrus-rt/job/Papyrus-RT-Gerrit-Core/424/consoleFull). It shows 18 errors in org.eclipse.papyrusrt.umlrt.tooling.compare.internal.UMLRTDiagramChangeTest, which are NoSuchMethod errors. 

@Philip: does the Neon.3 release of EMF Compare have higher version numbers that the custom branch? Do we need to update our TPs?

Thanks

--
Ernesto Posse
Zeligsoft


--
Ernesto Posse
Zeligsoft
--
Ernesto Posse
Zeligsoft

Back to the top