This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | I18N - encoding choice in wizard of freeform from ant not seen in project encoding property | ||
---|---|---|---|
Product: | java | Reporter: | Ken Frank <kfrank> |
Component: | Freeform | Assignee: | Tomas Zezula <tzezula> |
Status: | RESOLVED WORKSFORME | ||
Severity: | blocker | CC: | dkonecny |
Priority: | P3 | Keywords: | I18N |
Version: | 6.x | ||
Hardware: | Sun | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
Ken Frank
2007-11-19 20:23:34 UTC
added relnote keyword; please provide some text for release note/workaround here soon. ken.frank@sun.com "wizards for create freeform project with existing source (not the existing ant script)" is an oxymoron; this would be a regular project, not a freeform project. I don't know if that should have an encoding choice in the wizard, but that would be a separate RFE if so. Actually I was not aware that the freeform creation wizard was supposed to let you set encoding - this may be a mistake. thanks for clarifying about that its only the ones with existing ant script that are considered as freeform. should a separate issue be filed on web also due to behavior of the web project as mentioned below ? "for a web project with existing ant if change the encoding in the wizard, the new encoding is shown in project properties but if not change it, it shows as <No Encoding> in project properties." as to the choice in the wizard for encoding, I had thought that was provided as a service to the user at that point, rather than need to go to project properties and change it there after project creation (which is why I thought perhaps the project with existing sources wizard might want to have it also) ken.frank@sun.com Please provide *exact* steps to reproduce, because I'm not able to reproduce this behavior except one situation and that is when you don't select any source folder when creating a project by wizard. Which is kind of very special situation when user create a project and don't assign any sources for it (such a project doesn't make any sense). After that when user finally selects a source folder in project properties he also needs to select encoding, but that's IMO minor UI problem. If this is the original problem of this issue it's not P2 priority IMO. What is the problem with setting up encoding of the project in creation wizard? Especially for freeform project. steps, using web -> web application with existing ant script 1. new wizard appears 2. name and location panel - fill in location of the existing project 3. other sections of that wizard page is filled in 4. build and run panel - accept defaults 5. web sources panel - accept defaults 6. source package folders panel a. source package folder is prechosen already b. encoding value is that of the current global project encoding; I dont change it 7. next 2 panels - accept defaults and finish 8. project is created - encoding value of project properties states <No Encoding> as originally reported. 9. HOWEVER, if in source panel, one adds another src folder, which for this project there is another src folder at top level of the project, and then complete the wizard, then the encoding shown in project properties is valid. 9. the case for java project is not valid, since at least for the java project I am using, the sources panel is not seeded with anything, so it means I do need to choose a src folder, which avoids the problem mentioned above for web project. ken.frank@sun.com In such case it should be probably fixed in web/freeform. I don't think that this issue needs to be mentioned in Release notes, since web/freeform project is used by minority of users and there is really easy workaround. Removing RELNOTE kw and lowering priority. based on last comments - should this be changed to web/freeform ? or file new issue there and leave this one ? (we want to see if this can be fixed for 6.1) ken.frank@sun.com moving opened issues from TM <= 6.1 to TM=Dev moving to web category as suggested is issue comments. ken.frank@sun.com Please evaluate. Thanks. Why was this passed to web? Encoding is managed by java part of freeform. reproducible for java freeform project, select encoding in wizard and got "no encoding" in properties. 6.7m3 Changing the default component owner to tzezula. Works for me. When encoding is not changed in the Wizard (the wizard offers native OS encoding) no encoding element is stored in the project.xml and the project properties correctly displays OS native encoding (MacRoman in my case). When encoding is changed in the Wizard the encoding element is stored in the project.xml and the project properties correctly displays the chosen encoding. Tested both with j2se and web. |