| Re: [papyrus-rt-dev] Version updated to 0.9.0 |
Hi,Well, I still have the "mental model" of the architecture as I once drew in the the picture here:But sure, if we have practical aspects like what you describe, then maybe we have to accept that the C++ language is used as *the* test language.In the long run though, I think it would be good to create a separate "test language" for those tests that needs a language, to avoid the dependency on a specific target language (if/when we ever get other target languages than C++).But yes, with the current dependency though, the least that could be made is to include C++ in the target platform for the Tooling sub-project, to avoid that you have to bring the C++ sub-project and its source code into your workspace to get the tooling sub-project and its test to compile, even though I still feel that it is an incorrect dependency. I guess I just have to "suck it up", and accept that we need to be pragmatic also... :)/Peter Cigéhn_______________________________________________On 9 March 2017 at 18:00, Christian Damus <give.a.damus@xxxxxxxxx> wrote:One of the aspects of the tooling that we need to test is support for the model’s default language. For all of our test models, that is C++. To remove this dependency, we would have to create a test language in the Tooling tests bundles and use that language in test models. That would be fine, but will be something we have to always remember when creating test models, to use the test language instead of the real C++ language.Maybe, instead, we should update Tooling sub-project in the Oomph setup to include CPP in the target platform?
Cheers,
Christian
On Mar 9, 2017, 11:56 -0500, Peter Cigéhn <peter.cigehn@xxxxxxxxx>, wrote:
Hi,One more aspect that I guess should be fixed as well, is that the tooling tests depend on the C++. I always bump into this issue when I create a new workspace in my development environment, and only bring in the tooling sub-project in the Oomph setup, and then I get compilation error where:Bundle 'org.eclipse.papyrusrt.umlrt.cpp' cannot be resolvedTooling should really not depend on the C++ stuff. So whatever it is in the tooling tests (in org.eclipse.papyrusrt.umlrt.tooling.diagram.common.tests) that depends on C++, then that test should be moved to the C++ tests.To "work-around" this, I have to bring in the C++ sub-project from the Oomph-setup as well, which is doable, but still that dependency is not correct, and probably should be fixed along with the core tests depending on tooling and codegen./Peter Cigéhn_______________________________________________
On 9 March 2017 at 01:11, Christian Damus <give.a.damus@xxxxxxxxx> wrote:
I would add that hiccups in the Core build caused by absence of some Xtext bundles was just another problem that wouldn't have happened if our Core tests didn't require the Tooling and Codegen components. We really need to refactor those tests to make them independent of the tooling.
Cheers,Christian
On Mar 8, 2017, 18:32 -0500, Ernesto Posse <eposse@xxxxxxxxxxxxx>, wrote:
_______________________________________________Hello everyone. This is just to inform that the update to version 0.9.0 has been completed. This includes POM files, MANIFEST.MF files and bundle dependency declarations, for all components (profile, core, common, cpp, tooling, compare, migration and codegen) and their tests.All Hudson jobs are green, except for Gerrit-RCPTT which has been red for 23 days and counting.The updated version is now available on all p2 repos including the nightly.The update took longer than expected due to a failure of the Master-Product job on Monday due to a temporary unavailability of the Papyrus repo. However, thanks to Christian's help and patience, we were able to untangle the job dependency web.Thanks--Ernesto PosseZeligsoft--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
_______________________________________________
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
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
_______________________________________________
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
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