[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [mylyn-integrators] upcoming changes to Mylyn Commons

I am experiencing a problem which seems to be coming from this re-factoring.
  After installing latest Mylyn Reiews my Eclipse installation is not starting and is complaining of a class not found exception, so the TasksUIPlugin can not be started.

Caused by: java.lang.NoClassDefFoundError: org/eclipse/mylyn/internal/tasks/core/notifications/Environment
at java.lang.Class.getDeclaredConstructors0(Native Method)
at java.lang.Class.privateGetDeclaredConstructors(Class.java:2389)
at java.lang.Class.getConstructor0(Class.java:2699)
at java.lang.Class.newInstance0(Class.java:326)
at java.lang.Class.newInstance(Class.java:308)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.loadBundleActivator(AbstractBundle.java:166)
... 69 more     

Looking at the latest changes we can see that the class above was removed from o.e.m.tasks.core 
  However my upgraded installation picked up the new tasks.core plug-in but not the latest o.e.m.tasks.ui plug-in.

Looking at the o.e.mylyn.taks.ui manifest, it specifies dependencies to o.e.m.tasks.core [3.0.0, 4.0.0).  

I think the minimum dependency should now be moved to 3.7 ??
so the latest tasks.ui gets loaded as well.

I am not sure if there are other similar cases caused by the re-structuring.

Lets discuss further in the Mylyn weekly meeting.


On Thu, Dec 1, 2011 at 6:32 AM, Steffen Pingel <steffen.pingel@xxxxxxxxxxx> wrote:

over the course of the Mylyn restructuring we made a number of improvements to the modularity of the code base and distribtion packaging. At the same time we made sure to maintain a high degree of backwards compatibility which in some cases meant keeping internals stable. 

I would like to take the next step and tackle pending refactoring tasks for Mylyn 3.7 in the next few weeks that are likely to have an impact on integrations.

To encourage consumption of Mylyn Commons I would like to remove the provisional identifier from all packages and mark them as API. Where feasible we'll leave existing classes in place and deprecate them.

Please be aware that all internal deprecated classes are likely to be REMOVED prior to the release.

 360301: [api] make provisional packages API

Additionally, I would like to make the bundle naming in Mylyn Commons consistent with the standard project guidelines by moving each component into it's own namespace.

 350385: [releng] rename bundles to reflect component structure

Each component will be distributed in a separate feature to ensure that the commons are always updated along with other Mylyn components.

 305782: restructure Mylyn Commons features

If you have any concerns or input please comment on the tasks above. I'll sent out a note once all refactorings are complete with documentation how to consume the changes.


Steffen Pingel
Senior Software Developer, Eclipse Mylyn
Mylyn Tasks Lead

mylyn-integrators mailing list