Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [mdt-papyrus.dev] Java, C++, Qompass Designer plug-ins moved?

Hi Christian,

 

You are right. The Qompass sub-team has made a work to refactor the plugins.

 

Remi are on the way to add a note on the Neon roadmap in order to explain the move on the creation of Papyrus components

-          dedicated repository

-          Bugzilla component

-          dedicated update site

-          dedicated developer web site

-          dedicated job HIPP tab

 

At this moment, the following components have been created but are not same status:

-          Sysml 1.4 (done)

-          Robotml (prototype)

-          Moka (prototype)

-          Qompass (just evocation at this end of the week)

 

I hope it clarifies a little. I let the Qompass team give us more information. I have just joined us since latest week.

If you want to join the discussion on the namespace for Qompass, I have created the following ticket

https://bugs.eclipse.org/bugs/show_bug.cgi?id=486041

 

The question is: do we wait your refactoring on Qompass in the extra (new folder) or do we switch to the new repo now?

 

Francois

 

De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx] De la part de Christian W. Damus
Envoyé : lundi 18 janvier 2016 21:15
À : Papyrus Project list <mdt-papyrus.dev@xxxxxxxxxxx>
Objet : [mdt-papyrus.dev] Java, C++, Qompass Designer plug-ins moved?

 

Hi, Team,

Doing a rebase today, I discovered that a whole bunch of plug-ins are deleted or moved:

·         extraplugins/codegen/*

·         extraplugins/java/*

·         extraplugins/qompass-designer/*

and maybe more.

I noticed this because I had all of these projects imported in my workspace in order to include them in all of the bundle-dependency refactorings that I’m doing for Neon.

Whoever is doing these refactorings, please advise the development team what is the disposition of the affected plug-ins. There is also impact on the Oomph set-up model, perhaps the features, the discovery site, and I don’t know what else. In future, it really does help to announce major changes like this on the mailing list, rather than just letting us discover them by happenstance.

(this applies also to the occasional carving out of Extras into separate Git repositories that has been happening throughout the Neon release)

Thanks,

Christian

Attachment: smime.p7s
Description: S/MIME cryptographic signature


Back to the top