uima-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Richard Eckart de Castilho <richard.eck...@gmail.com>
Subject Re: need for special m2e setting in jcasgen-maven-plugin?
Date Wed, 03 Jul 2013 19:49:53 GMT
This message pops up in particular on projects that use the Sonatype OSS parent POM.
Probably this one is using a different mechanism to enforce minimum version, e.g.
using the enforcer plugin instead of using the "prerequisites" element in the POM.
With the Apache/UIMA parent POM, this m2e setting may not be necessary anymore.

-- Richard

Am 03.07.2013 um 21:13 schrieb Richard Eckart de Castilho <richard.eckart@gmail.com>:

> I have various projects displaying this warning in Eclipse:
> "maven-enforcer-plugin (goal "enforce") is ignored by m2e."
> The m2e settings are probably there to remove this warning. I
> don't remember if I added them of if they have been there
> before.
> -- Richard
> Am 03.07.2013 um 21:05 schrieb Marshall Schor <msa@schor.com>:
>> I'm cleaning up loose ends, in preparation for doing a uima-sdk release.
>> The current UIMA-wide parent-pom (v5) has an execution of the enforcer plugin to
>> check for a good level of Maven (3 or better) and Java (5 or better), so every
>> project is getting this by default as part of their build.  The UIMA-wide
>> parent-pom (v5) has no m2e lifecycleMappingMetadata specs for the enforcer
>> plugin, and it doesn't seem to be needed (no errors are reported in Eclipse).
>> The jcasgen-maven-plugin POM has a special m2e lifecycleMappingMetadata spec for
>> the enforcer plugin, which says to "ignore", but no local call on the enforcer
>> plugin.
>> I'd like to take out the m2e part of the jcasgen-maven-plugin POM, but wanted to
>> check to see if I'm missing something here; does anyone know why this m2e
>> lifecycleMappingMetadata spec was put into this POM in the first place?
>> -Marshall

View raw message