Re: maven prerequisite clause giving complaint of improper use

[Marshall Schor <ms...@schor.com>]

The uima-wide parent-pom is already using the enforcer plugin for both maven
version and java version.

The prerequisites clause is still useful for some of our projects which **are**
maven plugin.  The Maven Model docs say:

In Maven 2, this was also specifying the minimum version of Maven required to
build a project,
but this usage is deprecated in Maven 3 and not checked any more...

By the way, I did see this use-is-deprecated message once, but now do not see
it...  not sure why not...

-Marshall

On 10/2/2018 7:20 AM, Richard Eckart de Castilho wrote:
> ...
> While we are at it: Maven keeps telling me that we shouldn't use the stanza
>
>   <prerequisites>
>     <!-- 2.2.0 is broken when deploying - checksums invalid -->
>     <!-- 2.2.1 doesn't work -->
>     <maven>3.3.9</maven>
>   </prerequisites>
>
> in the parent pom, because that stanza is only relevant for Maven plugin modules.
> If we want to generally enforce the use of a specific Maven version, we should be
> using the enforcer plugin instead.
>
> Is there any reason we have that stanza in the UIMA parent pom?
>
> Cheers,
>
> -- Richard

Re: maven prerequisite clause giving complaint of improper use

[Marshall Schor <ms...@schor.com>]

+1, I'll remove this from the uima-wide parent, and leave it to individual maven
plugin projects.

-Marshall

On 10/3/2018 4:10 AM, Richard Eckart de Castilho wrote:
> On 2. Oct 2018, at 16:16, Marshall Schor <ms...@schor.com> wrote:
>> The prerequisites clause is still useful for some of our projects which **are**
>> maven plugin.  The Maven Model docs say:
>>
>> In Maven 2, this was also specifying the minimum version of Maven required to
>> build a project,
>> but this usage is deprecated in Maven 3 and not checked any more...
> It should be sufficient to declare the prerequisites in the actual maven plugin
> modules instead of declaring it in the overall parent pom.
>
> In order to still centrally configure the minimum maven version from the parent
> pom, it may be possible to declare a property which would then be used in the
> prerequisites section of the maven plugin module's poms.
>
> -- Richard

Re: maven prerequisite clause giving complaint of improper use

[Richard Eckart de Castilho <re...@apache.org>]

On 2. Oct 2018, at 16:16, Marshall Schor <ms...@schor.com> wrote:
> 
> The prerequisites clause is still useful for some of our projects which **are**
> maven plugin.  The Maven Model docs say:
> 
> In Maven 2, this was also specifying the minimum version of Maven required to
> build a project,
> but this usage is deprecated in Maven 3 and not checked any more...

It should be sufficient to declare the prerequisites in the actual maven plugin
modules instead of declaring it in the overall parent pom.

In order to still centrally configure the minimum maven version from the parent
pom, it may be possible to declare a property which would then be used in the
prerequisites section of the maven plugin module's poms.

-- Richard