> I'm wondering about the encoding example. Would you EVER want to do this?
> I mean, you need to configure the compiler plugin with the same encoding so
> specify project.build.sourceEncoding is the way to go IMO. You could keep
> the possibility to configure this, but I don't see the value in having an
> example of (what I think would be) an anti-pattern.
>

Thinking this through I think that the example could be kept, but you
should change it to show the proper usage of the
project.build.sourceEncoding property to configure this.

/Anders



>
> /Anders
>
>
> On Thu, Mar 28, 2013 at 12:36 PM, Baptiste MATHUS <[email protected]>wrote:
>
>> Fixed, thanks.
>>
>>
>> 2013/3/28 Stephen Connolly <[email protected]>
>>
>>>
>>> http://mojo.codehaus.org/templating-maven-plugin/examples/source-filtering.htmlhas
>>>  the defaults in the example as children of <goals> and not
>>> <configuration>
>>>
>>>
>>> On 27 March 2013 22:01, Baptiste MATHUS <[email protected]> wrote:
>>>
>>>> Hi,
>>>>
>>>> I'd like to release version 0.0.1 of the templating-maven-plugin
>>>>
>>>> That project was created to offer the Maven Right Way® to filter
>>>> sources.
>>>>
>>>> This is the very* first release* of this recently graduated mojo.
>>>> That's why I chose a 0.0.1 versioning as a starting point.
>>>>
>>>> Staging Repositories:
>>>> General:  https://nexus.codehaus.org/content/groups/staging/
>>>> Exclusive:
>>>> https://nexus.codehaus.org/content/repositories/orgcodehausmojo-003/
>>>>
>>>> (Staging) Site:
>>>> http://mojo.codehaus.org/templating-maven-plugin/
>>>>
>>>> SCM Tag:
>>>> https://svn.codehaus.org/mojo/tags/templating-maven-plugin-0.0.1
>>>>
>>>> We also plan to add some day support for templating engines like
>>>> Mustache, ...
>>>>
>>>>  [ ] +1
>>>>  [ ] +0
>>>>  [ ] -1
>>>>
>>>> The vote is open for 72 hours and will succeed by lazy consensus.
>>>>
>>>> Cheers
>>>>
>>>> -- Baptiste
>>>>
>>>
>>>
>>
>>
>> --
>> Baptiste <Batmat> MATHUS - http://batmat.net
>> Sauvez un arbre,
>> Mangez un castor !
>>
>
>

Reply via email to