[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [dali-dev] Changes to Dali plugin and package names for next major release
|
I will be checking in the first phase of these changes soon, then Tran
will update the build for the new plug-ins.
1. A new 'common' component will be created in CVS with the following
new plug-ins:
org.eclipse.jpt.common.core
org.eclipse.jpt.common.core.tests
org.eclipse.jpt.common.ui
org.eclipse.jpt.common.ui.tests
2. The libraryValidators and resourceLocators extension points will be
moved to org.eclipse.jpt.common.core (these are new in this release)
Committers need to remember that now we have JptCommonCoreTests to run
on top of JptCoreTests and JptEclipseLinkCoreTests.
Phase 2 will involve renaming org.eclipse.jpt.utility(and tests)
plug-in and packages to org.eclipse.jpt.common.utility (and tests) and
moving to common component. I will do this once we get the build working
for the phase 1 changes.
Phase 3 will involve renaming the org.eclipse.jpt.core.* plug-ins and
packages. Another email will be sent detailing those changes prior to
check-in.
Karen
On 1/28/2011 3:36 PM, Neil Hauge wrote:
The Dali team is planning a number of plugin and package name changes
as part of a restructuring to properly accommodate the introduction of
the JAXB component into the Dali code base for Indigo.
Background: There are some good opportunities for code reuse between
the existing JPA and new JAXB component, and as a result we are
creating a Common component to contain the common code between these 2
components. As a result, the existing JPA core plugin (o.e.jpt.core)
will have a new dependency on the Common core plugin
(o.e.jpt.common.core).
Problem: As you might have noticed, this leaves the JPA core code
with a misleading name of (org.eclipse.jpt.core), including misleading
names for all of the JPA core packages (org.eclipse.jpt.core.*).
This could lead to code and dependency degradation in the future, not
to mention confusion down the road for committers and clients
Solution: We plan to refactor these names to represent the actual
functional area of the plugin, which is JPA. As a result, the new
plugin name for o.e.jpt.core would become o.e.jpt.jpa.core, and the
contained packages would become o.e.jpt.jpa.core.*. The o.e.jpt.ui
code would similarly move to o.e.jpt.jpa.ui.
Changing the plugin and root package name of o.e.jpt.core and
o.e.jpt.ui will be a breaking change that will impact Dali clients,
and as a result the major plugin version for jpt.core and jpt.ui will
be moving from 2.3 to 3.0 in the renamed plugins. Project metadata
will not be changing, so project compatibility shouldn't be an issue.
Let us know if you have any questions or concerns about this upcoming
change. A forthcoming email will describe the exact changes to assist
with migration when you are ready to move to the 3.0 code base.
Thanks,
Neil Hauge
Dali Project Lead
_______________________________________________
dali-dev mailing list
dali-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dali-dev