Re: [mdt-papyrus.dev] Mavenize Papyrus projects?

[MAGGI Benoit <Benoit.MAGGI@xxxxxx>]

Hi Johan,

 

Short history:

 

Initially, this was a proposition from François [1]

but some committers were against

so François made a prototype [2] and put the committers that were against it as reviewers.

after that I don’t know.

   I wasn’t aware of the slideshare document   

   and don’t know why the patch was never integrated.

 

Regards,

Benoit

 

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

2: https://git.eclipse.org/r/#/c/65585/

 

De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx] De la part de Johan Van Noten
Envoyé : mercredi 15 mars 2017 12:07
À : Papyrus Project list <mdt-papyrus.dev@xxxxxxxxxxx>
Objet : [mdt-papyrus.dev] Mavenize Papyrus projects?

 

Dear devs,

 

Christian has been creating a document (https://www.slideshare.net/cdamus/adopting-maven-nature-in-papyrus-source-projects) way back in the “Mars days”.

Conclusion of this document was that adding the Maven nature to the Papyrus projects would have quite some benefits and would not adversely affect the current workflows:

• Better consistency between workspace (PDE) build and Hudson/Tycho
• Automatic discovery of some misconfigurations
• …

 

Christian’s advice was to integrate it early in Neon.

Unless I overlook something, this is not taken into the Oxygen work yet.

Is it planned anyway? Have the findings of the document been invalidated?

 

Best regards,

Johan

Flanders Make