Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [m2e-users] M2Eclipse / Eclipse Indigo / LifecycleMapping configuration

Hi Igor,


thanks for your hints. But why so complicated? I am not familiar with
OSGi nor extension and I dont want to spend time in investigating and
developing. I simply need the plugin for dependency resolution, not
more. Because of many other unbeautiful warnings/errors (e.g "groupId
duplicates parent groupId", "project configuration inconsistent; please
update project configuration" - I dont want to update project
configuration since a want separate output folders for eclipse and maven
build.....).

Now I've installed the old version 0.12, which do what I want. I hope in
the future the plugin allows for a lightweight usage as I prefer.


Regards
/roman





> You really need to write develop a trivial m2e extension (i.e. some java
> code wrapped in an OSGi bundle). And you'd still need to enable that
> extension in your pom.xml file. And I'll be happy to provide pointers
> and answer further questions on m2e-dev list.
> 
> -- 
> Regards,
> Igor
> 
> On 11-12-19 3:04 PM, Roman Klähne wrote:
>> Hi Igor,
>>
>>
>> I also think this must be a trivial thing and I am really wondering why
>> this is not yet implemented. I read in the "distributed documentation"
>> that there is a NoopConfigurator, which do nothing. Can I use this to
>> configure m2e to run no plugin? If yes, how I do that?
>>
>>
>> Regards
>> /roman
>>
>>
>>> This is not currently possible, but should be fairly trivial to
>>> implement as an m2e extensions. I can provide some pointers on m2e-dev
>>> mailing list if you are interested.
>>>
>>> -- 
>>> Regards,
>>> Igor
>>>
>>> On 11-12-19 2:50 PM, Roman Klähne wrote:
>>>> Hi Lukasz,
>>>>
>>>>
>>>> thank you for your reply. The problem is that I do not need any
>>>> automatic maven build within Eclipse using connectors or something
>>>> else.
>>>> I want to ignore all plugin execution!
>>>> My project pom's are completely independent of Eclipse. If I need to
>>>> run
>>>> a maven phase I do that either with a
>>>> Eclipse-Maven-Run-Configuration or
>>>> on the command line using mvn.
>>>>
>>>> To achieve the ignoring of all plugins I have to add the
>>>> pluginExecution
>>>> element from your example for each single plugin, which extremely blows
>>>> up my pom (there - resp. in parent poms - are a lot of plugins
>>>> configured).
>>>>
>>>> I want m2e say, what it should do and not what it should not do.
>>>>
>>>> I think there must be a simple way to achieve this. But, unfornutately,
>>>> it seems to be impossible to provide a comprehensive documentation
>>>> explaining all the key features of m2e, such as connectors,
>>>> configurators, execution filters etc.
>>>>
>>>>
>>>> Regards
>>>> /roman
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> Hi Roman,
>>>>>
>>>>> This should help you get started. The first mapping invokes a plugin
>>>>> goal when the project is fully built (project clean from Eclipse),
>>>>> and the second simply ignores the goal.
>>>>>
>>>>> You don't need to specify a life-cycle mapping if a m2e connector
>>>>> already exists for the given plugin (check Eclipse Marketplace and
>>>>> install appropriate connectors, i.e. axistools is covered).
>>>>>
>>>>> I myself couldn't find a complete and thorough documentation,
>>>>> including what exact version should be given for the
>>>>> lifecycle-mapping artifact.
>>>>>
>>>>> Also, check this out:
>>>>>
>>>>> http://wiki.eclipse.org/M2E_plugin_execution_not_covered
>>>>>
>>>>> Hope this helps.
>>>>> Lukasz
>>>>>
>>>>>          <pluginManagement>
>>>>>              <plugins>
>>>>>                  <plugin>
>>>>>                      <groupId>org.eclipse.m2e</groupId>
>>>>>                      <artifactId>lifecycle-mapping</artifactId>
>>>>>                      <version>1.0.0</version>
>>>>>                      <configuration>
>>>>>                          <lifecycleMappingMetadata>
>>>>>                              <pluginExecutions>
>>>>>                                  <pluginExecution>
>>>>>                                      <pluginExecutionFilter>
>>>>>
>>>>> <groupId>org.codehaus.mojo</groupId>
>>>>>
>>>>> <artifactId>idlj-maven-plugin</artifactId>
>>>>>
>>>>> <versionRange>[1.0.0,)</versionRange>
>>>>>                                          <goals>
>>>>>                                              <goal>generate</goal>
>>>>>                                          </goals>
>>>>>                                      </pluginExecutionFilter>
>>>>>                                      <action>
>>>>>                                          <execute>
>>>>>
>>>>> <runOnIncremental>false</runOnIncremental>
>>>>>                                          </execute>
>>>>>                                      </action>
>>>>>                                  </pluginExecution>
>>>>>                                  <pluginExecution>
>>>>>                                      <pluginExecutionFilter>
>>>>>
>>>>> <groupId>org.apache.maven.plugins</groupId>
>>>>>
>>>>> <artifactId>maven-ear-plugin</artifactId>
>>>>>
>>>>> <versionRange>[1.0.0,)</versionRange>
>>>>>                                          <goals>
>>>>>
>>>>> <goal>generate-application-xml</goal>
>>>>>                                          </goals>
>>>>>                                      </pluginExecutionFilter>
>>>>>                                      <action>
>>>>>                                          <ignore/>
>>>>>                                      </action>
>>>>>
>>>>> </pluginExecution>
>>>>> </pluginExecutions>
>>>>>                          </lifecycleMappingMetadata>
>>>>>                      </configuration>
>>>>>                  </plugin>
>>>>>              </plugins>
>>>>>          </pluginManagement>
>>>>>
>>>>> -----Original Message-----
>>>>> From: m2e-users-bounces@xxxxxxxxxxx
>>>>> [mailto:m2e-users-bounces@xxxxxxxxxxx] On Behalf Of Roman Klähne
>>>>> Sent: Monday, December 19, 2011 1:37 PM
>>>>> To: m2e-users@xxxxxxxxxxx
>>>>> Subject: [m2e-users] M2Eclipse / Eclipse Indigo / LifecycleMapping
>>>>> configuration
>>>>>
>>>>> Hi,
>>>>>
>>>>>
>>>>> in past I used Eclipse 3.5.1 with old m2eclipse version. Now I've
>>>>> updated to Eclipse Indigo with new integrated m2eclipse.
>>>>>
>>>>> I am searching yet for a while for a documentation of the
>>>>> lifecycle-mapping plugin with all the possible tags
>>>>> (<configurator>,<pluginExecution>, etc.), reasonable example
>>>>> configurations etc. All what I can find is distributed documentation
>>>>> explaining backgrounds etc. but not providing some examples how to
>>>>> implement the configuration.
>>>>>
>>>>> I want a really simple configuration ignoring all plugin execution.
>>>>> If I want to execute a plugin I use run configurations. The only
>>>>> thing I need m2e is to manage dependencies.
>>>>> To achieve this I dont want to add<pluginExecution>   elements for all
>>>>> plugins (at least 15 plugins) in my project pom's.
>>>>>
>>>>> By the way, I think the pom is really a bad place to put eclipse
>>>>> specific configuration.
>>>>>
>>>>> Best Regards
>>>>> /roman
>>>>>
>>>>> _______________________________________________
>>>>> m2e-users mailing list
>>>>> m2e-users@xxxxxxxxxxx
>>>>> https://dev.eclipse.org/mailman/listinfo/m2e-users
>>>>>
>>>>> ----------------------------------------------------------------------
>>>>> This message w/attachments (message) is intended solely for the use
>>>>> of the intended recipient(s) and may contain information that is
>>>>> privileged, confidential or proprietary. If you are not an intended
>>>>> recipient, please notify the sender, and then please delete and
>>>>> destroy all copies and attachments, and be advised that any review or
>>>>> dissemination of, or the taking of any action in reliance on, the
>>>>> information contained in or attached to this message is prohibited.
>>>>> Unless specifically indicated, this message is not an offer to sell
>>>>> or a solicitation of any investment products or other financial
>>>>> product or service, an official confirmation of any transaction, or
>>>>> an official statement of Sender. Subject to applicable law, Sender
>>>>> may intercept, monitor, review and retain e-communications (EC)
>>>>> traveling through its networks/systems and may produce any such EC to
>>>>> regulators, law enforcement, in litigation and as required by law.
>>>>> The laws of the country of each sender/recipient may impact the
>>>>> handling of EC, and EC may be archived, supervised and produced in
>>>>> countries other than the country in which you are located. This
>>>>> message cannot be guaranteed to be secure or free of errors or
>>>>> viruses.
>>>>>
>>>>> References to "Sender" are references to any subsidiary of Bank of
>>>>> America Corporation. Securities and Insurance Products: * Are Not
>>>>> FDIC Insured * Are Not Bank Guaranteed * May Lose Value * Are Not a
>>>>> Bank Deposit * Are Not a Condition to Any Banking Service or Activity
>>>>> * Are Not Insured by Any Federal Government Agency. Attachments that
>>>>> are part of this EC may have additional important disclosures and
>>>>> disclaimers, which you should read. This message is subject to terms
>>>>> available at the following link:
>>>>> http://www.bankofamerica.com/emaildisclaimer. By messaging with
>>>>> Sender you consent to the foregoing.
>>>>> _______________________________________________
>>>>> 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
> _______________________________________________
> m2e-users mailing list
> m2e-users@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/m2e-users
> 



Back to the top