cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Liguori (JIRA)" <j...@apache.org>
Subject [jira] Updated: (CXF-3078) Encoding warning with Maven 2.2.1 while building CXF sample projects.
Date Thu, 21 Oct 2010 19:28:15 GMT

     [ https://issues.apache.org/jira/browse/CXF-3078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Robert Liguori updated CXF-3078:
--------------------------------

    Description: 
I see an encoding warning when building CXF samples with Maven 2.2.1.

[INFO] ------------------------------------------------------------------------
[INFO] Building Apache CXF Code Generation Maven2 Plugins
[INFO]    task-segment: [clean, install]
[INFO] ------------------------------------------------------------------------
...
[WARNING] Using platform encoding (Cp1252 actually) to read mojo metadata, i.e. build is platform
dependent!
...

This blog entry is close to what I am seeing:
([WARNING] Using platform encoding (Cp1252 actually) to copy filtered resources, i.e. build
is platform dependent!)

http://blog.vinodsingh.com/2009/04/encoding-warning-with-maven-210.html

I think it's best to remove warnings where possible... as such, should the CXF POM files be
updated with something similar to this:

<properties>
    <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
  </properties>

Or would this affect backwards compatibility?

Thanks!


  was:
I see an encoding warning when building CXF samples with Maven 2.2.1.

This blog entry is identical to what I am seeing:
([WARNING] Using platform encoding (Cp1252 actually) to copy filtered resources, i.e. build
is platform dependent!)

http://blog.vinodsingh.com/2009/04/encoding-warning-with-maven-210.html

I think it's best to remove warnings where possible... as such, should the CXF POM files be
updated with something similar to this:

<properties>
    <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
  </properties>

Or would this affect backwards compatibility?

Thanks!



> Encoding warning with Maven 2.2.1 while building CXF sample projects.
> ---------------------------------------------------------------------
>
>                 Key: CXF-3078
>                 URL: https://issues.apache.org/jira/browse/CXF-3078
>             Project: CXF
>          Issue Type: Improvement
>          Components: Build system
>    Affects Versions: 2.3.0
>            Reporter: Robert Liguori
>            Priority: Minor
>
> I see an encoding warning when building CXF samples with Maven 2.2.1.
> [INFO] ------------------------------------------------------------------------
> [INFO] Building Apache CXF Code Generation Maven2 Plugins
> [INFO]    task-segment: [clean, install]
> [INFO] ------------------------------------------------------------------------
> ...
> [WARNING] Using platform encoding (Cp1252 actually) to read mojo metadata, i.e. build
is platform dependent!
> ...
> This blog entry is close to what I am seeing:
> ([WARNING] Using platform encoding (Cp1252 actually) to copy filtered resources, i.e.
build is platform dependent!)
> http://blog.vinodsingh.com/2009/04/encoding-warning-with-maven-210.html
> I think it's best to remove warnings where possible... as such, should the CXF POM files
be updated with something similar to this:
> <properties>
>     <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
>   </properties>
> Or would this affect backwards compatibility?
> Thanks!

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message