Hi, Ernesto,
Yes, that’s the same problem I had when I erroneously blamed Philip for missing stuff in the setup to kick off this whole thread. 😕
There is an important caveat, though, which is that the state of the local website checkout only matters if you are redirecting the index URI for the Papyrus-RT setup to that local checkout. This is configured by importing the “Oomph Setup” sub-project. If you don’t have this redirection, then you always get the latest from Eclipse.org. And only people who contribute changes to the setup model (who necessarily must test it before pushing it) would or should have this redirection implemented.
On 19 July, 2016 at 14:55:33, Ernesto Posse (eposse@xxxxxxxxxxxxx) wrote:
Hi again.
The EMF
Compare and EGit dependencies are pretty clearly in the main
Papyrus-RT project’s targlet, so unless you’re not importing any
stream of the top ‘Papyrus-RT’ project node, I have no explanation
for why you should be getting these compilation errors. It
should not be necessary to set your PDE Target from the target
definition used by the build.
I finally figured it out. I had not pulled the website git
repo, so my .setup was still behind and it wasn't the version with
the new dependencies.
So, to conclude, there are some undocumented steps that people
need to do whenever a dependency has been updated. For the person
adding the dependency, I've already listed the steps a few messages
ago. For the rest of the team:
1. pull the main git repo *and* the website git repo
2. restart or perform setup tasks
So I would suggest to any committer who adds a new dependency
to give the rest of the team a heads-up here in the mailing list
whenever a new dependency is added.
--
Ernesto Posse
Zeligsoft
_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev
|
