On 11:05:38 AM Tuesday, May 31, 2011 Stanislav Ochotnicky wrote:
> Excerpts from Alexander Kurtakov's message of Mon May 30 18:38:49 +0200
2011:
> > On 07:36:38 PM Monday, May 30, 2011 Stanislav Ochotnicky wrote:
> > > Excerpts from Guido Grazioli's message of Mon May 30 11:54:57 +0200
2011:
> > > > 2011/5/30 Ankur Sinha <sanjay.ankur@gmail.com>:
> > > > > The solution was to add:
> > > > >> <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
> > > > >>
> > > > >> <project.reporting.outputEncoding>UTF-8</project.reporting.outputE
> > > > >> ncod ing>
> > > > >
> > > > > to the properties section of the pom.xml file.
> > > >
> > > > could that be a candidate for inclusion in settings.xml or
> > > > MAVEN_OPTS?
> > >
> > > Good idea I believe, gonna look into it.
> >
> > I don't think this is good idea at all because AFAIK this will override
> > whatever is set in the pom even thus breaking projects that have set
> > everything correctly. Feel free to prove me wrong on this.
>
> While I admit that we should probably not touch sourceEncoding,
> outputEncoding should always be UTF-8 in Fedora.

Yup, I agree here. I would even say that we need to ask upstream to make it
default.

Alex
--
java-devel mailing list
java-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/java-devel

2011/5/31 Alexander Kurtakov:
> On 11:05:38 AM Tuesday, May 31, 2011 Stanislav Ochotnicky wrote:
>> Excerpts from Alexander Kurtakov's message of Mon May 30 18:38:49 +0200
>> > I don't think this is good idea at all because AFAIK this will override
>> > whatever is set in the pom even thus breaking projects that have set
>> > everything correctly. Feel free to prove me wrong on this.
>>
>> While I admit that we should probably not touch sourceEncoding,
>> outputEncoding should always be UTF-8 in Fedora.
> Yup, I agree here. I would even say that we need to ask upstream to make it

Actually overriding the settings in the pom file is a bit brute: if i understood
corretly this setting applies to filtered text resources, and having an xml
config file with <?xml version="1.0" encoding="iso8859-1"?> would be
allowed: changing the output encoding to UTF-8 could break things; what i had
in mind was adding an inactive profile in settings.xml, to be activated
in the mvn command line when needed.

Cheers

--
Guido Grazioli <guido.grazioli@gmail.com>
Via Parri 11 48011 - Alfonsine (RA)
Mobile: +39 347 1017202 (10-18)
Key FP = 7040 F398 0DED A737 7337* DAE1 12DC A698 5E81 2278
Linked in: http://www.linkedin.com/in/guidograzioli
--
java-devel mailing list
java-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/java-devel