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.

Bug 97852 - Provide FileEncodingQueryImplementation
Summary: Provide FileEncodingQueryImplementation
Status: RESOLVED FIXED
Alias: None
Product: apisupport
Classification: Unclassified
Component: Project (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker (vote)
Assignee: Jesse Glick
URL:
Keywords:
Depends on: 101076
Blocks: 97848
  Show dependency tree
 
Reported: 2007-03-14 16:05 UTC by Tomas Zezula
Modified: 2007-12-13 16:25 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tomas Zezula 2007-03-14 16:05:12 UTC
The project should provide FEQI in its lookup and javac task should use encoding
argument.
Comment 1 Jesse Glick 2007-03-23 22:35:18 UTC
I will just fix UTF-8 as the encoding since I don't expect a need for other
encodings in NBM projects.
Comment 2 Jesse Glick 2007-03-23 23:17:12 UTC
Checking in
apisupport/project/src/org/netbeans/modules/apisupport/project/queries/FileEncodingQueryImpl.java;
/shared/data/ccvs/repository/apisupport/project/src/org/netbeans/modules/apisupport/project/queries/FileEncodingQueryImpl.java,v
 <--  FileEncodingQueryImpl.java
initial revision: 1.1
done
Checking in
apisupport/project/src/org/netbeans/modules/apisupport/project/NbModuleProject.java;
/shared/data/ccvs/repository/apisupport/project/src/org/netbeans/modules/apisupport/project/NbModuleProject.java,v
 <--  NbModuleProject.java
new revision: 1.152; previous revision: 1.151
done
Checking in
apisupport/project/src/org/netbeans/modules/apisupport/project/suite/SuiteProject.java;
/shared/data/ccvs/repository/apisupport/project/src/org/netbeans/modules/apisupport/project/suite/SuiteProject.java,v
 <--  SuiteProject.java
new revision: 1.34; previous revision: 1.33
done
Checking in nbbuild/templates/common.xml;
/shared/data/ccvs/repository/nbbuild/templates/common.xml,v  <--  common.xml
new revision: 1.58; previous revision: 1.57
done
Checking in nbbuild/templates/projectized.xml;
/shared/data/ccvs/repository/nbbuild/templates/projectized.xml,v  <-- 
projectized.xml
new revision: 1.93; previous revision: 1.92
done
Comment 3 Jesse Glick 2007-03-26 16:16:40 UTC
Was not in time for M8.
Comment 4 Ken Frank 2007-04-13 19:24:26 UTC
if this will be seen in m9 vs in latest nb builds, this can be ignored:

in project properties of module project,  I don't see place where encoding is noted
or can be changed, like is seen in j2se project - shouldn't that be there since that
seems part of the solving of 42638 that users might want to change encoding ?

ken.frank@sun.com
Comment 5 Jesse Glick 2007-04-13 22:49:05 UTC
I guess you missed my comment above - the encoding is fixed as UTF-8 for all
module projects.
Comment 6 anchoret 2007-05-11 03:31:51 UTC
Using UTF-8 as the default encoding of a project is much better of course than
what has been before. But it's not perfect, I think, since NB is such a great
IDE. Why it should be worse than other IDEs? Why it can't deal with the
encoding, the basic problem?
Comment 7 Tomas Zezula 2007-05-11 06:59:45 UTC
For the j2se project, web project and others you can simply change the encoding
in the project's customizer. For the apisupport project, project type for
creating Neteans modules, it's good decision to keep the NetBeans sources in
common encoding (UTF-8).
Comment 8 colonel 2007-12-13 13:34:36 UTC
It is good ONLY for netbeans modules.
But what about standalone applications which are using netbeans platform?
Comment 9 colonel 2007-12-13 13:35:36 UTC
It is good ONLY for netbeans modules.
But what about standalone applications which are using netbeans platform?
Comment 10 Ken Frank 2007-12-13 16:25:30 UTC
see 123798 which relates to this;
thus I think this one can be left closed
and can refer to that other issue.

could you add your comments and your name to cc
list of that other issue ?

IMO referring to other issue is more applicable
since this issue was for nb6, and nb6 has been released.

thus in that context will reclose this one.

ken.frank@sun.com