Comment 1 Shawn Minto 2010-03-04 19:02:46 EST

Should this include the soap package too, or should we create a separate feature for that too?

Comment 2 Steffen Pingel 2010-03-04 21:50:17 EST

I think it makes sense to keep these separate since Axis + dependencies adds a bunch of libraries but we can discuss that before creating the features. There is also the related question of how we are going to distribute (and split) commons UI.

Comment 3 Steffen Pingel 2010-04-23 21:48:35 EDT

The challenge is that each of the commons plug-ins (core, net, ui, soap, xmlrpc) would require a separate feature to satisfy integrators needs or not marked as singletons. The latter won't work as some plug-ins export extension points or are intentionally designed as singletons. To avoid adding five new features we have come up with the following solution:

A new feature org.eclipse.mylyn.commons has been added which includes all commons plug-ins. This feature is provided for update manager compatibility and not categorized on the update site or P2 repository. To avoid conflicts this feature must be the only including the commons plug-ins. All other features should only import all required commons plug-ins. 

That means integrators need to remove all plugin entries from feature.xml files that reference org.eclipse.mylyn.commons.* plug-ins, e.g.:

 <plugin
         id="org.eclipse.mylyn.commons.soap"
         ...
         
And replace the plugin element with an import:

   <requires>
      <import plugin="org.eclipse.mylyn.commons.soap" version="3.2.0" match="compatible"/>
   </requires>

In addition we recommend adding an import for required Mylyn features to ensure that other dependencies are resolved on a feature rather than plug-in level:

       <import feature="org.eclipse.mylyn_feature" version="3.2.0" match="compatible"/>