Community
Participate
Working Groups
The JPT project currently contains only one conceptual component, JPA. For 3.0, JPT needs to house 2 different components, JPA and JAXB. This will require project level changes in the following areas: - CVS - Bugzilla This will also require some amount of restructuring of the JPT code, but I am going to keep that as a separate bug so the scope of this bug doesn't become too large.
More details: For CVS... The webtools CVS repository contains the following root folder for Dali content: org.eclipse.jpa This should be changed to: org.eclipse.jpt to accurately reflect the project name and scope - "Dali Java Persistence Tools". This will require the assistance of Eclipse IT. A "jaxb" directory should be added to the "components" directory. In addition, a "core" directory should be added to contain the common code to jpa and jaxb components For Bugzilla... I propose that a "JAXB" entry be added to the existing list of Components resulting in the following items: Doc - Still used for both JPA and JAXB content Framework - Still used for core and JPA framework related bugs General - a simple place for users to enter bugs, which can be further triaged to other bucket as necessary. Would still house most Dali bugs. JAXB - used for all JAXB specific bugs Website - Still used for website related bugs
(In reply to comment #1) Regarding Bugzilla, after further discussion we decided it might be confusing if there is a component listing for 'JAXB' and not one for 'JPA', so in addition to adding 'JAXB', we should also add 'JPA'. 'General' can be used to handle bugs that are not specific to any particular technology area.
Still waiting to get all committers to a safe "checked-in" state for these changes.
Update: JAXB component has been added to bugzilla and to the our cvs components directory. Other refactoring work is still waiting for some outstanding changes to be checked in.
Will have to wait until M4.
Will be M7 before all dependent items can be completed.
WTP 3.2.x still lives.
Marking this as fixed. Bug 336550 is a standalone issue that can be dealt with at the appropriate time.