[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[mylyn-integrators] upcoming changes to Mylyn Commons
- From: Steffen Pingel <steffen.pingel@xxxxxxxxxxx>
- Date: Thu, 1 Dec 2011 12:32:43 +0100
- Delivered-to: firstname.lastname@example.org
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.
Senior Software Developer, Eclipse Mylyn
Mylyn Tasks Lead