Bug 177435 - [nls tooling] Allow Externalize Strings Accessor class that is not in source folder
Summary: [nls tooling] Allow Externalize Strings Accessor class that is not in source ...
Status: ASSIGNED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Text (show other bugs)
Version: 3.3   Edit
Hardware: PC Windows NT
: P5 enhancement (vote)
Target Milestone: ---   Edit
Assignee: JDT-Text-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2007-03-14 17:34 EDT by Amber Beerends CLA
Modified: 2007-09-14 05:42 EDT (History)
1 user (show)

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 Amber Beerends CLA 2007-03-14 17:34:01 EDT 
Build ID:  I20061214-1445

The Externalize Strings Wizard allows configuration of the accessor class, but the Configure dialog requires that the class must be selected from a source folder within the workspace.  We have an API that builds upon the internationalization and localization APIs provided by the Java SE SDK.  Most often, it is not in the developer's workspace, but available via the project's classpath.  It would be nice if this class could be selected and referenced by the wizard.
Comment 1 Dani Megert CLA 2007-03-15 03:41:25 EDT 
There are currently no plans to do this but it might be reconsidered if someone provides a good patch.
Comment 2 Dani Megert CLA 2007-06-22 09:59:32 EDT 
Get rid of deprecated state.
Comment 3 Luzius Meisser CLA 2007-09-14 05:42:15 EDT 
Related to this, but a little simpler to implement: allow to externalize strings into resource files that are not in a source folder. Currenlty, the externalize strings wizard requires the ".properties" files to be in a source folder. As we distribute our ".properties" files independently from our jar files, fixing this would allow us to use the externalize Strings feature for our project.