Bug 378500 - Using platform encoding (Cp1252 actually) to copy filtered resources, i.e. build is platform dependent!
Summary: Using platform encoding (Cp1252 actually) to copy filtered resources, i.e. bu...
Status: VERIFIED WORKSFORME
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.8   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: 4.3 M5   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2012-05-04 10:36 EDT by Martin Spamer CLA
Modified: 2013-02-04 11:05 EST (History)
3 users (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 Martin Spamer CLA 2012-05-04 10:36:17 EDT 
Build Identifier: 


The error message "Using platform encoding (Cp1252 actually) to copy filtered resources, i.e. build is platform dependent!" is displayed in problems despite the Workspace and project being defined as UTF-8 text file encoding.




Reproducible: Always
Comment 1 Ayushman Jain CLA 2012-05-07 10:51:37 EDT 
Can you please copy the complete error log here? Which plugin is causing this error message?
Also, which build id are you using?
Are you using Maven? If yes, try this in your project's pom.xml

<project>
  ...
  <properties>
    <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
  </properties>
  ...
</project>
Comment 2 Martin Spamer CLA 2012-05-08 07:40:19 EDT 
Yes, but changing the properties to UTF-8 for the project or globally doesn't fix this issue.  This fix you suggest is actually a work around.  The bug is that changes to this property setting does't fix the project.
Comment 3 Ayushman Jain CLA 2012-05-08 09:50:56 EDT 
(In reply to comment #2)
> Yes, but changing the properties to UTF-8 for the project or globally doesn't
> fix this issue.  This fix you suggest is actually a work around.  The bug is
> that changes to this property setting does't fix the project.

Yeah, it seems like bug 378783 also happens on the same lines
Comment 4 Satyam Kandula CLA 2012-05-10 06:57:53 EDT 
(In reply to comment #2)
I think this message is actually coming from M2E. JDT/Core doesn't report this warning. Look at http://maven.apache.org/general.html. 
> Yes, but changing the properties to UTF-8 for the project or globally doesn't
> fix this issue.  This fix you suggest is actually a work around.  The bug is
> that changes to this property setting does't fix the project.
What do you mean by that this doesn't fix the project? What is the problem you are facing apart from the message?
Comment 5 Martin Spamer CLA 2013-01-22 11:13:06 EST 
This problem seems to be fixed in Indigo.
Comment 6 Jay Arthanareeswaran CLA 2013-01-22 20:59:53 EST 
Thanks for the update. Closing the bug.
Comment 7 Jay Arthanareeswaran CLA 2013-02-04 11:05:07 EST 
Verified for 4.3 M5 with build I20130130-2000