Hi, Benoit,
Inasmuch as the git repository is publicly available for read-only access, these are, of course, already “published”. I suppose it’s a question of whether there is enough perceived value in creating dedicated builds and binary downloads/repositories for these bundles.
Is there provision in the Eclipse Development Process for a p2 repository that maintains a nightly snapshot of bundles but never actually releases them as a formal capital-R “Release”? If so, that might be a good option for these test bundles. It will become even more interesting when the diagram tests generation framework is ready for some kind of more public consumption, because that is a tool that could be especially useful for anyone developing graphical DSLs with Papyrus.
I would say that I don’t think we should include any test bundles, not even these utilities, in the SDK. These are not software artifacts for which we plan features and a release roadmap as we do the for the Papyrus product. I would support a move to publish these test utility bundles and the tests generation framework in their own dedicated repository.
Cheers,
Christian
On Mon, Apr 20, 2015 at 11:59 AM, MAGGI Benoit <Benoit.MAGGI@xxxxxx> wrote:
Hi,
Some people doing customization in Papyrus asked for advices to setup test.
I pointed them to org.eclipse.papyrus\tests\junit\plugins\junit
But sadly these utilities are not “published”
@Christian, @Camille :
-
Do you think it is possible to publish org.eclipse.papyrus.junit.framework and org.eclipse.papyrus.junit.utils ?
-
Do you think it should be independent from papyrus (or part of the sdk feature) ?
Regards,
Benoit MAGGI
