[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [m2e-users] On handling of generated code
|
Right, as explained in [1], mapping metadata embedded in maven plugins
is considered after pom.xml and installed m2e extensions, so both m2e
users and m2e extension developers will be able to workaround
misbehaving maven plugins.
My concern is that in most cases the source of the problem, i.e.
misbehaving maven plugin, will be far from obvious, the problem itself
will be intermittent (remember the infamous MNGECLIPSE-823?) and in the
end the ability to embed mapping metadata in maven plugins will result
in worse experience for m2e users and more support/troubleshooting work
for m2e developers.
As a side note, lets move any further discussion of this subject to m2e-dev.
[1] http://wiki.eclipse.org/M2E_plugin_execution_not_covered
--
Regards,
Igor
On 11-10-24 3:23 AM, Max Rydahl Andersen wrote:
On Oct 21, 2011, at 17:11, Igor Fedorenko wrote:
There will be no error messages about the
plugins any more, but they will either not work as expected by Eclipse
users (like in your case, code generation simply does not happen) or
cause end-less builds, resource leaks and so on. All these problems will
result in bugreports agains m2e and will require significant amount of
time to analyze.
We'll see how it goes…
if there is an "native" m2e eclipse configurator plugin for a mvn plugin does that precedence
or is the result "merged" ?
if taking precedence that is at least one way to improve on misbehaving mvn plugins.
/max
http://about.me/maxandersen
_______________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-users
