Eclipse/MylynPackaging

= Eclipse Mylyn >= 3.5.0 Packaging Guide =

As of release 3.5.0, Eclipse Mylyn is a new top-level project at eclipse.org. In addition, Mylyn decided to split their only project prior to 3.5.0 into several sub-projects. Those Mylyn sub-projects are as follows:


 * 1) org.eclipse.mylyn
 * 2) org.eclipse.mylyn.commons
 * 3) org.eclipse.mylyn.contexts
 * 4) org.eclipse.mylyn.tasks
 * 5) org.eclipse.mylyn.versions
 * 6) org.eclipse.mylyn.builds
 * 7) org.eclipse.mylyn.docs
 * 8) org.eclipse.mylyn.reviews

For Fedora we aimed for one SRPM per sub-project. Due to dependencies, this is not entirely true, but matches for the most part. The Fedora SRPMs for upstream Eclipse Mylyn >= 3.5.0 are as follows:

These SRPMs produce the following binary RPMs:

And here is the mapping of upstream Eclipse Mylyn features to Fedora's binary RPMs:

Recommended Packaging Order for Future Eclipse Mylyn Upstream Releases due to Dependencies
We recommend to package Eclipse Mylyn upstream releases in the following order (this is a known to be working):


 * 1) eclipse-mylyn-commons
 * 2) eclipse-mylyn
 * 3) eclipse-mylyn-context
 * 4) eclipse-mylyn-ide
 * 5) eclipse-mylyn-tasks
 * 6) eclipse-mylyn-docs
 * 7) eclipse-mylyn-versions
 * 8) eclipse-mylyn-builds

Implications for Eclipse Mylyn (version < 3.5.0) Dependent Packages
First note that users should be able to update their mylyn packages as usual. However, due to the restructuring of Eclipse Mylyn packages in Fedora, it may be required to update dependencies for Mylyn dependent Eclipse plug-ins. It may also be required to update build requirements for Mylyn dependent RPMs in Fedora. Here is a table showing which Mylyn 3.5 packages replace old (< 3.5) Mylyn packages (above tables and the following table may be helpful determining the correct packages for updating your R/BR's in relevant spec files):

Also, have a look in  for plug-in dependency names to be used by the   option of. All mylyn related plug-ins contain the string "mylyn" in the directory name.