Hi,
Based on the extensive
traffic regarding the development environment, I just for the sake
of it tried updating my own developer environment.
One thing that I could see
was that if I only imported the top level Papyrus-RT project, then
I got a bunch of projects in the "fallback" working set "Other
Projects", i.e. a bunch unit test projects (which in its turn had a
few dependency errors, apart from the numerous lifecycle errors
discussed elsewhere on the mailing list).
I checked the setup file,
and saw that the Projects Import task and the Working Sets task
does not really have matching rules. The working set has a rule
.*/tests/junit/framework/.* whereas the related import imports
everything
under ${papyrus-rt.git.clone.location/tests/junit}
I would expect that the
projects being imported should match the related working sets rule,
right?
Christian, any
opinions?
I tried patching the setup
file and changing the Projects Import task to only import from
${papyrus-rt.git.clone.location/tests/junit/framework}. Then the
dependency error got removed, and no projects ended up in the
"Other Projects" working set (which I would always be empty if we
have matching Projects Import and Working Sets task definitions in
the different Oomph projects).
/Peter Cigéhn
_______________________________________________
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