Mailing-List: contact dev-help@hc.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "HttpComponents Project" <dev@hc.apache.org>
Received-SPF: error (athena.apache.org: local policy)
Message-ID: <1371558950.7964.0.camel@ubuntu>
Subject: Re: Wrong compiler property names used in parent POM.
From: Oleg Kalnichevski <olegk@apache.org>
To: HttpComponents Project <dev@hc.apache.org>
Date: Tue, 18 Jun 2013 14:35:50 +0200
In-Reply-To: 
 <CAOGo0VbyR8R1F8dQ0R+qU3djQ7hKWm2mYOxmaxuEnW+tEHwMFg@mail.gmail.com>
References: 
	<CAOGo0VbyR8R1F8dQ0R+qU3djQ7hKWm2mYOxmaxuEnW+tEHwMFg@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit

On Tue, 2013-06-18 at 11:59 +0100, sebb wrote:
> The Maven compiler plugin uses properties which have the prefix
> "maven.compiler.", however the pom uses "maven.compile.".
> 
> That's why the poms need to include the compiler config - it would be
> picked up automatically otherwise.
> 
> Also the plugin uses uses maven.compiler.showDeprecation not
> maven.compile.deprecation
> 
> Fixing these should allow simplification of many of the poms.
> 
> If the parent pom is fixed, some child poms will also need to be changed.
> However they will only need to be changed when they switch to the new
> parent pom - it won't affect existing builds - so I don't see any
> downside to fixing the parent pom for the next version.
> 
> OK?
> 

+1

Oleg


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org