Re: [mdt-papyrus.dev] discusion relative to maven integration in papyrus

[LE FEVRE FRANCOIS <francois.le-fevre@xxxxxx>]

Hi Christian,

I will not push the constraints plug-ins.

I will let this gerrit commit as it waiting for your test. I do understand it is crucial not to have major impacts on developer community.

Personally, I already import plugins as maven projects. At first I retrieve for instance the infra folder from git as general project and then I right click on it from the workspace view to import all sub-folder as maven projects.

 

If the Oomph setup already includes the m2e tooling, and your test on adding m2e nature are positive,

does it mean that we will not need any internal Eclipse builder as the m2e builder will do the job automatically or in demand?

 

Thanks for the precision.

 

Let me know if you encounter any difficulty that I am not aware of.

 

Francois

 

De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx] De la part de Christian W. Damus
Envoyé : mercredi 18 février 2015 13:09
À : Papyrus Project list
Objet : Re: [mdt-papyrus.dev] discusion relative to maven integration in papyrus

 

Hi, François,

 

I did not suggest that the constraints plug-ins could be pushed with missing source code.  That will put compilation errors in everybody's workspace on references to nonexistent types.  Please, don't do that.  Either the source files remain checked in or they  may be generated by an internal Eclipse builder in the same way as Xtext/Xtend generate to Java.

 

The Oomph setup already includes the m2e tooling to provide the POM editor and its supporting tools.  I did volunteer to try a fully m2e-built workspace, which is only fair because I'm the most vocal in resistance (or, rather, in expressing concern about impact on the Papyrus developer community).  I hope to spend some time this week trying the usual development workflows with m2e.

 

Cheers,

 

Christian 

 

 

On Wed, Feb 18, 2015 at 4:44 AM, LE FEVRE FRANCOIS <francois.le-fevre@xxxxxx> wrote:

Dear all,

 

Thanks for yesterday meeting, I had appreciated the discussion even if I didn’t prepare the arguments for/against m2e/maven (I was not aware of the meeting).

 

If I do understand, we could test the following propositions

 

·         Testing a new architecture

o   Modularize the project

o   by introducing subfolder/project with a pom that groups children modules linked to a given set of plugins (model/edit/editor/test)

·         Testing maven nature

o   Introduce m2e nature and test its usability, impacts on performance

o   If concluding, we could also imagine to integrate the m2e maven plugin directly in the oomph

 

In order to allow us testing the m2e nature impact.

 

As proposed by Christian, I will commit the constraints plugin without the m2e nature.

So people that retrieve the code source, will not have the generated code at retrieve, but could generate it at demand by executing the genmodel workflow through eclipse manual button/action or by executing the mvn install command

 

Francois

 

 

François Le Fèvre

Institut CARNOT CEA LIST – Nano INNOV

CEA Tech/DILS/Laboratoire d’Ingénierie dirigée par les modèles pour les Systèmes Embarqués (LISE),

Point Courrier n°174

91191 Gif sur Yvette CEDEX

T :0169084986

@ :francois.le-fevre@xxxxxx

 

-

LISE: http://www-list.cea.fr/fr/ingenierie-logiciel-et-systeme

Papyrus: https://www.eclipse.org/papyrus/

Blog: http://biocamp.blogspot.fr/

 

<smime.p7s>

 

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