Le samedi 29 mars 2008, Benjamin Bentmann a écrit :
> > core plugins to be modified:
>
> I moved this list over to the wiki article [0] in Confluence, think it's
> easier to maintain there instead of being splattered through this mailing
> thread.
great
I added a link in http://docs.codehaus.org/display/MAVEN/Home and
http://docs.codehaus.org/display/MAVEN/All+Proposals
When the proposal will be ready, we'll call for a vote.
> > should we provide ${encoding} or ${sourceEncoding}?
>
> Don't know, it's the question of ease of typing vs. expressiveness. The
> tools javac and javadoc have their corresponding cli parameters named
> "encoding", too. On the other hand, how often do we expect users to really
> specify this parameter via the cli instead of permanently configuring the
> POM?
true: let's stay with encoding
> platform-dependent encoding. I would rather prefer that the behavior of a
> plugin depends only on its own version and not also on the executing Maven
> version to ease reproducibility.
right
> So I believe there are two choices:
> If your initial concerns about backwards compatibility meet general
> consensus, the super POM should simply not define a specific property for
> ${project.build.sourceEncoding} such that users get platform-dependent
> behavior as now by default (not my favorite).
> Otherwise, plugins should by convention agree to handle a null value for
> the encoding parameter to denote some fixed encoding. This way, upgrading
> Maven will not affect the default encoding behavior.
The convention has to be shared between every plugin and the super POM. I
dislike the pure formal convention, that every plugin would copy/paste.
Coded as an API like "String checkSourceEncoding(String encoding)" method to
AbstractMojo, that every plugin would call: "encoding =
checkSourceCodeEncoding(encoding)" is ok for me
>
>
> Benjamin
>
>
> [0]
> http://docs.codehaus.org/display/MAVENUSER/POM+Element+for+Source+File+Enco
>ding
>
>
> ---------------------------------------------------------------------
> 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]
