Bug 238598 - New Non-roman characters in JET project names causes underscores in ID and Java packages names
Summary: New Non-roman characters in JET project names causes underscores in ID and Ja...
Status: NEW
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Jet (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Paul Elder CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-06-26 10:02 EDT by Paul Elder CLA
Modified: 2020-05-01 16:11 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Paul Elder CLA 2008-06-26 10:02:33 EDT 
Currently, the NEW JET project wizard generates the Java package name for compiled output as follows:

1) Project name is used to derive the plug-in id. Since plug-in id's are limited to [A-Za-z0-9], _ and ., any invalid characters are mapped to _. The ID limitation is imposed by the OSGi specification. 

2) The following wizard defaults are then generated from the plug-in:
  * Default Java Package
  * Transformation Name
  * Template Loader (uses Default Java Package)

In the case where the JET project name is in some non-roman language (e.g. Arabic, Japanese), this results in transformation/plug-in IDs and Java package names that contain nothing but _ and .

The current wizard behavior is identical to the PDE new plug-in wizard, but must lead to considerable confusion to some users.

Possible solutions:
* Drive the Java package names directly from the project name, not the plug-in ID. Disadvantage: this is counter to best practices where Java code in a plug-in matches the namespace established by the plug-in ID.

* Derive the project name from the plug-in ID. That is, let the user enter the plug-in first. Disadvantage: this is different from many Eclipse new project wizards.