[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [m2e-users] feedback M2E Ingio - m2e connector concept
|
Just to be clear. The projects are *not* corrupted (nothing bad is done to your classpath, class files, etc.). You just get red X's (I know they are annoying) but you should still be able to run the code. Could you please describe in which respect is your project "corrupted"?
Also, as mentioned before, the errors can mostly be removed in one shot in the parent pom.
"Backward compatibility" is not the right terminology here. m2e had to change because of the erratic behaviour (infinite builds, test not recognized, etc.) it was presenting when executing various mojos. Our solution to this was to flag mojos that could not be recognized and allow the user to install connectors. This change has been introduced early in 2011 to let enough time for ppl to try it.
Now, knowing that going back to the old behaviour is not a solution, what are your proposals to improve the situation?
On 2011-06-24, at 10:26 AM, Honnix Liang wrote:
> Totally agreed.
>
> This update almost corrupts all of my existing projects. I have to
> rollback to earlier version.
>
> Please consider backward compatibility when doing such a huge change.
>
> BTW, I also didn't see any benefit except mass. Why should I put
> Eclipse stuff in pom.xml and other guys in team are using Intellij for
> example?
>
> On Fri, Jun 24, 2011 at 6:45 PM, Moser, Christian <cmo@xxxxxxxxxxx> wrote:
>> Just tried out our build environment with Indigo and m2e
>> 1.0.0.20110607-2117.
>>
>>
>>
>> User-experience :
>>
>>
>>
>> After a full import of all maven projects, I’ve received following error in
>> almost every pom:
>>
>>
>>
>> Plugin execution not covered by lifecycle configuration: …
>>
>>
>>
>> After clicking around for some time, I found under pom.xml / Overview the
>> possibility to ignore those «not covered plugin-lifecycles »
>>
>>
>>
>> Unfortunately, this modified my pom and added :
>>
>>
>>
>> <pluginManagement>
>>
>> <plugins>
>>
>> <!--This plugin's configuration is used to store Eclipse
>> m2e settings only. It has no influence on the Maven build itself.-->
>>
>> <plugin>
>>
>> <groupId>org.eclipse.m2e</groupId>
>>
>> <artifactId>lifecycle-mapping</artifactId>
>>
>> <version>1.0.0</version>
>>
>> <configuration>
>>
>> …
>>
>> </configuration>
>>
>> </plugin>
>>
>> </plugins>
>>
>> </pluginManagement>
>>
>>
>>
>> In the import wizard, after m2e didn‘t found lifecycle connectors, there
>> should be a combobox in the Action column displayed BEFORE the user clicks
>> an cell. Otherwise it’s not easy to unterstand that this cell is editable.
>>
>>
>>
>> Opinion :
>>
>>
>>
>> In my view, is the attempt to store M2e settings within a platform and !IDE!
>> independent element, such as pom.xml utterly the wrong place!
>>
>>
>>
>> I’m using maven because it is an independent build tool, which does not care
>> what is used for developing or building maven projects! Even if maven or
>> other IDE’s don’t care for those excludes (eventually..), I don’t wanna be
>> forced to edit all my pom’s or at least the parents (If you got any..) for
>> developing with Eclipse.
>>
>>
>>
>> Is there a possibility to disable this new m2e connector feature by
>> default ?
>>
>>
>>
>> My suggestions:
>>
>> - Store m2e connector excludes anywhere but in the pom.xml
>>
>> - Disable m2e connector feature by default
>>
>> - Documentation for m2e connectors (what are the advantages ?)
>>
>>
>>
>> Just my two coins,
>>
>> Regards Christian
>>
>>
>>
>> _______________________________________________
>> 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
