Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 370575

Summary:	[Papyrus] Avoid using fragments for Papyrus plug-ins
Product:	[Modeling] Papyrus	Reporter:	Camille Letavernier <cletavernier>
Component:	Core	Assignee:	Project Inbox <mdt-papyrus-inbox>
Status:	RESOLVED FIXED	QA Contact:
Severity:	major
Priority:	P3	CC:	rschnekenburger
Version:	unspecified
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:

Description Camille Letavernier

2012-02-03 11:44:41 EST

We have a few problems with fragments in Papyrus sources :

368274: Buckminster error with fragments and source feature
https://bugs.eclipse.org/bugs/show_bug.cgi?id=368274

Moreover, the fragments are not packaged as Jars, which sometimes make it hard to unzip Papyrus on Windows (The file names are too long).

Thus, we should really not use fragments, and keep their name as short as possible if they are really necessary.

Comment 1 Camille Letavernier

2012-02-03 11:49:55 EST

In r7135 on the Branch 0.8.X :

The fragment org.eclipse.papyrus.diagram.common.palette.customization has been transformed to a simple plug-in.

The plug-in org.eclipse.papyrus.diagram.common now provides an extension point for defining a specific Palette Customization Dialog. This extension point should not be used outside of Papyrus, as no priority policy has been defined. The result would be undefined.

The modification has not yet been ported on the trunk.

Comment 2 Camille Letavernier

2012-04-26 05:30:26 EDT

r7974: The previous modification has been ported to the trunk.

Comment 3 Cedric Dumoulin

2012-04-26 09:18:23 EDT

We have decide some time ago to remove tests from regular plugins, and to use fragment plugins for JUnit tests. This is because some tests need to access protected packages that can't be access otherwise.

So, we can't now say that we should not use fragments ....

Comment 4 Camille Letavernier

2012-04-26 09:25:15 EDT

Tests plugins/fragments do not need to be installed and deployed. So, using fragments is not a problem in this case.

The problem is really specific to deployed artifacts.