Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Dali Project/Weekly Meeting/December 04 2009"
(New page: =Dali Weekly Meeting= ===Attendees=== * Neil ==Agenda== ===New Topics=== * ===Old Topics=== * ===Next Meeting=== * ===Action Items=== *) |
|||
| Line 10: | Line 10: | ||
===New Topics=== | ===New Topics=== | ||
| − | * | + | *Should JPA 2.0 be enabled for Java 1.5 facet? |
| + | |||
| + | *What should the preselected Facet configuration be (JPA1.0 or JPA2.0 or calculated(if that is even possible))? | ||
| + | |||
| + | *Can we need to remove the Utility Facet? What are the implications? What is the desired use case for SE and EE scenarios? | ||
===Old Topics=== | ===Old Topics=== | ||
| − | * | + | * JPA 1.0 to 2.0 Migration - How can we improve the migration experience without being overbearing? |
| + | ** Some may wish to continue to use their 1.0 level artifacts, or will be stuck with them in a jar | ||
| + | Could be 2 phases: | ||
| + | |||
| + | Phase 1 - Add "Migrate XML documents" checkbox to current Facet change "Further Configuration..." dialog that will search for and upgrade persistence.xml and orm.xml and eclipselink-orm.xml (based on platform) as a part of the facet change. | ||
| + | |||
| + | Phase 2 - Add a new menu item on JPA project JPA Tools menu that will open a similar wizard, but won't require users to find the facet properties page. | ||
===Next Meeting=== | ===Next Meeting=== | ||
Revision as of 17:54, 24 November 2009
Contents
Dali Weekly Meeting
Attendees
- Neil
Agenda
New Topics
- Should JPA 2.0 be enabled for Java 1.5 facet?
- What should the preselected Facet configuration be (JPA1.0 or JPA2.0 or calculated(if that is even possible))?
- Can we need to remove the Utility Facet? What are the implications? What is the desired use case for SE and EE scenarios?
Old Topics
- JPA 1.0 to 2.0 Migration - How can we improve the migration experience without being overbearing?
- Some may wish to continue to use their 1.0 level artifacts, or will be stuck with them in a jar
Could be 2 phases:
Phase 1 - Add "Migrate XML documents" checkbox to current Facet change "Further Configuration..." dialog that will search for and upgrade persistence.xml and orm.xml and eclipselink-orm.xml (based on platform) as a part of the facet change.
Phase 2 - Add a new menu item on JPA project JPA Tools menu that will open a similar wizard, but won't require users to find the facet properties page.