Hi, Peter, On 8 April, 2016 at 08:47:02, Peter Cigéhn (peter.cigehn@xxxxxxxxx) wrote: Hi Christian,
I tested the updated the patch set and now the unresolved reference is fixed. Nice...
😁
Regarding the Mylyn issues, I tried just for the sake of it, to import the Papyrus root project also. And now the Mylyn queries seem to be "kick in", and start refreshing. So the Papyrus root project do seem to install the needed connectors.
Okay, thanks for confirming that the issue isn’t in the setup-configuration of the queries, but in the tooling installed. I’ll fix that.
Even though this is more related to the Papyrus setup file, I was just wondering what the purpose of importing a few projects already by the root Papyrus project itself is? They don't seem to belong to any working set either, so they all end up "Other Projects" workingset.. And they don't compile, so you get a bunch of compilation errors, mainly related to unresolved refernces. Is that really the intention with only importing the root Papyrus project? When you are at it, maybe you could take a look at this scenario for the Papyrus setup file as well?
Initially, these projects that were imported at the root were only the org.eclipse.papyrus.junit.utils and org.eclipse.papyrus.junit.framework. Since then, other plug-ins were added that match the same import specification. And there are dependencies added over time that maybe weren’t accounted for in the setup. It’s a lot to keep track of, and hard to notice when you just keep rolling along in the same workspace that you’ve always been using! The idea with importing these by default was to ensure that, no matter what the user is doing, even if just adding new plug-ins that didn’t exist yet in Papyrus, they would have what’s necessary to add JUnit tests for their work. In the case of Papyrus-RT, because we use the same core test framework as Papyrus, it seemed better to include these test plug-ins by default in the PDE Target. So, no matter what you import from Papyrus-RT (even if just the top project), you will have these Papyrus test bundles in your PDE target ready to support your test development.
_______________________________________________ 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
|