Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [m2e-users] Maven LifeCycleManagement

Hello Igor,

thank you for your fast reply. Yes our configurators changes JavaCode an starts PMD, checkstyle, findbugs.

We have the following problem:

We have Maven-Projects wich includes Configurators for Java-Formatting (settings of FormatRules in Eclipse),
PMD, Findbugs, Checkstyle, etc.

Before m2eclipse 1.0 these Configurators were running automatically by m2eclipse when a developer changes a code. In version 1.0 we now have to atache these configurators to a maven-plugin and the lifecycle.

Now the question is:

1) Is it possible to start these configutors automatically without ataching to a maven-plugin and the lifecycle ? 2) If we have to atache our configurators to a maven-plugin (e.g. maven-enforcer-plugin) is there a posibility to atache more than one configurator to this plugin in the "lifecycleMappingMetadata" (see example below) ?

Thank you for your help an have a nice weekend.

Best regards
     Sascha Vujevic

-----Urspr√ľngliche Nachricht----- From: Igor Fedorenko
Sent: Saturday, October 01, 2011 4:37 PM
To: m2e-users@xxxxxxxxxxx
Subject: Re: [m2e-users] Maven LifeCycleManagement

I am not sure I understand the problem. Does your command line build
reformats java code (or validates java code format), or these actions
are strictly m2e specific and have no command line build counterparts?

--
Regards,
Igor

On 11-09-30 11:06 AM, Sascha Vujevic wrote:
Hello users,
i have a question about the m2e 1.0 lifecyclemanagement:
we need to execute configurators on maven-projects which e.g. formats
java-code or make save-actions on these projects. These executions are
normally not attached to maven-plugins. How can i attache these
configurators (own plugins) to m2e.
Is there a possibility to atache more then one configurator to one
maven-plugin:
<lifecycleMappingMetadata>
<pluginExecutions>
<pluginExecution>
<pluginExecutionFilter>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-enforcer-plugin</artifactId>
<versionRange>[1.0.1,)</versionRange>
<goals>
<goal>enforce</goal>
</goals>
</pluginExecutionFilter>
<action>
<id>own.maven.ide.eclipse.configurators.scm.cleanup</id>
</configurator>
<configurator>
<id>own.maven.ide.eclipse.configurators.scm.saveactions</id>
</configurator>
</action>
</pluginExecution>
</pluginExecutions>
</lifecycleMappingMetadata>
Thank you for your help an have a nice week.
Best regards
Sascha Vujevic


_______________________________________________
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


Back to the top