Bug 329304 - Derive the default Java package from the project name
Summary: Derive the default Java package from the project name
Status: CLOSED DUPLICATE of bug 329433
Alias: None
Product: Dali JPA Tools
Classification: WebTools
Component: Diagram Editor (show other bugs)
Version: 0.5   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: 3.3   Edit
Assignee: Project Inbox CLA
QA Contact: Stefan Dimov CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-02 18:02 EDT by Kaloyan Raev CLA
Modified: 2012-09-11 11:03 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kaloyan Raev CLA 2010-11-02 18:02:35 EDT
Currently, the default Java package for new entities is set (by default) to "org.persistence". In a typical use case users would always want to change this property to a package that is in their project namespace. This step should be executed every time after a new JPA project is created. 

We can avoid this annoying step (at least for a majority of the use cases) if we set the default Java package (per project) to something that is related closer to the project and not fixed to a global package as "org.persistence". Perhaps, the simple idea to set the default Java package to the project name would work great for most of the use cases.
Comment 1 Neil Hauge CLA 2011-10-27 11:16:41 EDT
The 3.2 target now represents the Juno release.
Comment 2 Petya Sabeva CLA 2012-05-04 01:54:38 EDT
Retargeting this bug to the Kepler realease (3.3).
Comment 3 Petya Sabeva CLA 2012-09-11 11:03:06 EDT

*** This bug has been marked as a duplicate of bug 329433 ***