Hello Simo,
That second settings is what I am actually using! The output in Maven
looks like this:
[INFO]
------------------------------------------------------------------------
[INFO] Building deva - EJB
[INFO] task-segment: [package]
[INFO]
------------------------------------------------------------------------
[INFO] [resources:copy-resources {execution: copy-resources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 15 resources
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] null
On Windows, the build error does not occur and the build continues on.
But on both systems Maven tells me it is using UTF-8 and only on Linux
does it actually stop the build.
And as you can see, the error I get is pretty obvious! :-)
Only after turning on debugging I found out that there were Umlauts in
the property-files and that they were encoded as Cp1252!
Roland
On 01-11-10 18:58, Simone Tripodi wrote:
> Hi Roland,
> you've 2 options:
>
> * specify the 'encoding'[1] parameter of the maven-resources-plugin to
> 'UTF-8'
> * define in the 'properties' section the property
> 'project.build.sourceEncoding' to 'UTF-8'.
>
> I usually prefer the second option, so the char encoding is globally
> set also for the compiler and site plugin.
> Hope this helps, alles gute,
> Simo
>
> [1]
> http://maven.apache.org/plugins/maven-resources-plugin/resources-mojo.html#encoding
>
> http://people.apache.org/~simonetripodi/
> http://www.99soft.org/
>
>
>
> On Mon, Nov 1, 2010 at 6:03 PM, Asmann, Roland <[email protected]>
> wrote:
> > Hi all,
> >
> > I'm having some problems with the maven-resources-plugin. I am
> > responsible for our CI-builds and have a Hudson set up on a Linux
> > environment.
> >
> > Now, our developers are using Eclipse on Windows and therefore have
> > inadvertently configured the resources to be encoded in 'Cp1252',
> > instead of 'UTF-8'. Now some have accidentally included German Umlauts
> > in the resources, which I agree shouldn't be done in the first place.
> >
> > The strange thing is that Maven builds without any problems on Windows
> > (even telling us that it is using UTF-8 encoding on the resources!), but
> > it fails with an exception on Linux!
> >
> > Is there any way I can configure Maven to already fail the build on
> > Windows or have it configured so that it works on Linux? I want the
> > behavior of the two builds to be the same -- as it should be!
> >
> > Any help is greatly appreciated!
> >
> > --
> > Roland Asmann
> > Senior Software Engineer
> >
> > adesso Austria GmbH
> > Floridotower 26. Stock T +43 1 2198790-27
> > Floridsdorfer Hauptstr. 1 F +43 1 2198790-927
> > A-1210 Wien M +43 664 88657566
> > E [email protected]
> > W www.adesso.at
> >
> > -------------------------------------------------------------
> > >>> business. people. technology. <<<
> > -------------------------------------------------------------
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [email protected]
> > For additional commands, e-mail: [email protected]
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
--
Roland Asmann
Senior Software Engineer
adesso Austria GmbH
Floridotower 26. Stock T +43 1 2198790-27
Floridsdorfer Hauptstr. 1 F +43 1 2198790-927
A-1210 Wien M +43 664 88657566
E [email protected]
W www.adesso.at
-------------------------------------------------------------
>>> business. people. technology. <<<
-------------------------------------------------------------
