Re: [m2e-users] Ignoring the enforcer plugin

[Lóránt Pintér <lorant.pinter@xxxxxxxxx>]

Thanks, this works perfectly.

Lorant

On Fri, Jun 3, 2011 at 10:15, Anders Hammar <anders@xxxxxxxxxx> wrote:

Adding the following to the pluginManagement section did the trick for me:

        <plugin>
          <groupId>org.eclipse.m2e</groupId>
          <artifactId>lifecycle-mapping</artifactId>
          <version>1.0.0</version>
          <configuration>
            <lifecycleMappingMetadata>
              <pluginExecutions>
                <pluginExecution>
                  <pluginExecutionFilter>
                    <groupId>org.apache.maven.plugins</groupId>
                    <artifactId>maven-enforcer-plugin</artifactId>
                    <versionRange>[1.0,)</versionRange>
                    <goals>
                      <goal>enforce</goal>
                    </goals>
                  </pluginExecutionFilter>
                  <action>
                    <ignore></ignore>
                  </action>
                </pluginExecution>
              </pluginExecutions>
            </lifecycleMappingMetadata>
          </configuration>
        </plugin>

/Anders

2011/6/3 Lóránt Pintér <lorant.pinter@xxxxxxxxx>

Hi,

I think I wasn't clear: I did not create a configurator for Maven enforcer. What I try to fix is how can I ignore it *without* creating a custom configurator plugin just for this. Is there a way how I can specify in my POM to ignore the enforcer?

Thanks,

Lorant

On Thu, Jun 2, 2011 at 17:52, Igor Fedorenko <igor@xxxxxxxxxxxxxx> wrote:

Lifecycle mappings contributed by installed eclipse plugins are expected
to override default mappings provided by m2e. Please open a bugreport in
m2e bugzilla if this does not work for you. Make sure to provide
standalone sample project and mapping xml file, so we can understand
what's going on.


--
Regards,
Igor

On 11-06-02 11:43 AM, Lóránt Pintér wrote:

Hi,

I've managed to create lifecycle-mapping-configurator Eclipse plugins
for all our internal plugins. Not easy, but doable, and it's a great
improvement that people don't need to add stuff to their POMs to make
them work.

However, I still have things like the Maven enforcer plugin that is
reported to be ignored by m2e. I'm fine with that, so I would like to
remove the warning. Is there a way to specify that I do want it to be
ignored? Can I do it somehow in my parent POM?

BTW, I read this, but it didn't help:
http://wiki.eclipse.org/M2E_plugin_execution_not_covered :(

Thanks,
Lorant

_______________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-users

_______________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-users

_______________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-users

_______________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-users