implemented

I don't see the option for project file encoding on the mobiltly applications
project 
properties window, like it is for other projects that have implemented this.
Can it be there or is it in some other location ?

ken.frank@sun.com

Encoding field in Compiling category of Project Properties was introduced in 5.0.
FileEncodingQueryImplementation is now consuming this information already
provided by our project.

Created attachment 43244 [details]
screenshot of the panel

could there be the dropdown with other encoding choices as has been done for the
other feq implementations done so far by other project types ?

ken.frank@sun.com

yes, done

please, set up the correct target milestone for FIXED issue. It's not obvious
from date in what build the issue has been fixed.

thank you

It does not seem the mobility project writes the global encoding value:

1. create new j2se project (j2se project known to read/write global encoding value ok

2.  change the encoding value to something else.

3. create new java desktop project

4. look at the encoding property - it is the one created in step 2, so this works ok.

5. change the encoding value of the mobility project.

6. create new mobility and then also new  j2se project

7. the new project encoding property is not the one changed in step 5 - this is the part that does not appear to work.


PS - please  also review the code also for the following situations:

a. that the project encoding will be used for compilation  and all other activities in using form editor functionality
where sense
of encoding is needed to process files and data.

a1. that the other kinds of mobility projects, including those with existing source, read and write the project encoding
and work well with it - one can run even in en locale for that part of the testing

b. that when it does change the encoding, that new files created in the project use the new encoding
(besides html, jsp and xml - see c. below - this may not be needed if mobility projects does not use jsp or html files.

c. as per spec/infoTomas provided, and as part of other tasks, 97871 and 97873
the charset tag, if present, in jsp and html files will be used for the
encoding versus that of the project encoding -- please make sure these
2 senses of encoding work together in the project.

d. We are assuming that for java and other non html and jsp files,
that the project encoding will be used.

for text files,  97861 was done for properties, but 97867 related to
autodetect encoding of text files is not done, so expectation
is just that text files are created and processed in the encoding
of the project.

ken.frank@sun.com

The mobility project should update the default encoding when the encoding is changed in the project customizer. The fix
is simple, add:
FileEncodingQuery.setDefassultEncoding(newEncoding) into the code storing the project properties.

fixed

reopening - the global project encoding is not being used when create the project - the encoding of the
locale user is in is being used; and when changing the project encoding of this project, it does not
cause next created project like j2se project, or another mobility project, to use that encoding.

ken.frank@sun.com

exporting the last used encoding already works
using FileEncodingQuery during project creation was not effective because all default property values were cached - it
is fixed now

verified.