Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [mdt-papyrus.dev] [JUnit framework] Neon version

Hi Céline,

 

Funny enough this very topic was discussed yesterday during the weekly meeting. Currently the way this is constructed/organized does not seem to please everyone and the developer tools are indeed not released/synchronized with a specific version of Papyrus.

I think the main reason as to why it is not in the main repo is that the tests are not published and therefore the tools to make them work are not because they won’t serve any purpose by themselves.

 

As to when a decision/consensus on this topic will be taken and acted I do not yet know.

 

Quentin

 

De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx] De la part de Céline JANSSENS
Envoyé : mardi 30 août 2016 10:50
À : Papyrus Project list <mdt-papyrus.dev@xxxxxxxxxxx>
Objet : [mdt-papyrus.dev] [JUnit framework] Neon version

 

Hello everyone,

Papyrus RT is based on the neon.x version of Papyrus. And for the Junit test it depends on the Papyrus Junit Framework that is currently available only in Papyrus Developer component.

This causes dependency/compatibility issues for Papyrus RT!  Where can we find a neon.x version of this framework ?

By the way, why this framework is in such a component (Developer) , if Junit test depends on it, it should be included in the main repo?!

If we add the framework in the main repo, a neon.x version can be deployed as well as the other neon commit on maintenance branch. Isn't it?

 

Best regards

Céline

 

 

--

 

 

 

Céline JANSSENS
Software Engineer
+33 (0)2 44 47 23 23

 

Mail : cej@xxxxxxxxxxx


6 rue Léonard De Vinci - BP 0119 - 53001 LAVAL Cedex - FRANCE
www.all4tec.net

 


Image supprimée par l'expéditeur. Avast logo

L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.
www.avast.com

 


Back to the top