Hi Roland,
On 01.11.2010 18:03, Asmann, Roland wrote:
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!
I suppose the difference comes from the different default
Hi,
As I've written in another reply in this thread, I have set
'project.build.sourceEncoding', but it isn't working!
Roland
On 02-11-10 18:52, Jörg Hohwiller wrote:
Hi Roland,
On 01.11.2010 18:03, Asmann, Roland wrote:
configure Maven to already fail the build on
Windows or have it
...@adesso.at
To: users@maven.apache.org
Date: Tue, 2 Nov 2010 19:03:28 +0100
Subject: Re: maven-resources-plugin file-encoding
Hi,
As I've written in another reply in this thread, I have set
'project.build.sourceEncoding', but it isn't working!
Roland
On 02-11-10 18:52, Jörg
uebernehmen.
From: roland.asm...@adesso.at
To: users@maven.apache.org
Date: Tue, 2 Nov 2010 19:03:28 +0100
Subject: Re: maven-resources-plugin file-encoding
Hi,
As I've written in another reply in this thread, I have set
'project.build.sourceEncoding', but it isn't
Hi Roland,
sorry. My mail client was out of sync. When I wrote the mail, no response to
your post was visible to me.
In this case it sounds like something very special.
You can check...
... if you have any specific profiles in your POM that are OS dependent but I
doubt that it is related
Hmmm... Those last two are worth a shot... I'll try that tomorrow when I
have access to the build-server again.
There's no profiles in this project, so that can't be it.
Roland
On 02-11-10 19:16, Jörg Hohwiller wrote:
Hi Roland,
sorry. My mail client was out of sync. When I wrote the mail,
Jörg Hohwiller wrote:
Hi Roland,
sorry. My mail client was out of sync. When I wrote the mail, no response
to your post was visible to me.
In this case it sounds like something very special.
You can check...
... if you have any specific profiles in your POM that are OS dependent
but
Ha! Indeed, the output file on Windows contains garbled characters!
Great, so I know that the output is sh*t, but how to let Maven cry out
so those darn stubborn developers finally get the point?
Roland
On 02-11-10 19:22, Jörg Schaible wrote:
Jörg Hohwiller wrote:
Hi Roland,
sorry.
Hi Roland,
Asmann, Roland wrote:
Ha! Indeed, the output file on Windows contains garbled characters!
Great, so I know that the output is sh*t, but how to let Maven cry out
so those darn stubborn developers finally get the point?
use the verifier plugin to ensure that the generated file
Hi Jörg,
That plugin is tuned for single files, right? That would mean I'd have
to have all developers include the plugin with its configuration in
their POMs... I'd rather have a solution in a parent-POM (we use a
company-wide master)...
Also, if there is at least one correct Umlaut in
Hi Roland,
Asmann, Roland wrote:
Hi Jörg,
That plugin is tuned for single files, right? That would mean I'd have
to have all developers include the plugin with its configuration in
their POMs... I'd rather have a solution in a parent-POM (we use a
company-wide master)...
Also, if there
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
Martin,
Danke, aber nicht genau was ich brauch... Wie ich konvertieren kann weiß
ich schon, ich will nur das Maven schreit wenn was nicht passt, und zwar
auf beide Systeme!
Sorry, for the other readers:
Thanks, but that's not what I was looking for... I know how to convert
the encodings, I just
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]
14 matches
Mail list logo
