[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [m2e-users] Eclipse 3.7 with m2 Feedback
|
Contradict in what way? I say the same thing now as I did before --
there is no sensible default behaviour, m2e needs to know what to do
with all maven plugins bound to project build lifecycle, blindly running
maven plugins inside workspace is a bad idea.
--
Regards,
Igor
On 11-06-27 11:39 AM, Jochen Wiedmann wrote:
We previously had a discussion where I opined that you should have
provided a default value for the lifycycle mapping, rather than
forcing everybody to provide new plugins, or update their POM files.
At the time you asserted, that there is no sensible default value,
hence the error messages. Which your statement below seems to
contradict.
Jochen
On Sat, Jun 25, 2011 at 11:24 PM, Igor Fedorenko<igor@xxxxxxxxxxxxxx> wrote:
Not sure what you mean. I always said blindly running maven plugins
inside workspace was the cause of many problems we had in m2eclipse 0.12.
--
Regards,
Igor
On 11-06-25 3:38 PM, Jochen Wiedmann wrote:
On Sat, Jun 25, 2011 at 11:06 AM, Igor Fedorenko<igor@xxxxxxxxxxxxxx>
wrote:
To be clear, adding<execute/> mapping to pom.xml is almost certainly
not a good idea, especially for maven plugins that generate code in
eclipse workspace. Wiki [1] provides some background information about
bad side-effects of executing maven plugins inside eclipse workspace.
Igor, are you aware that that is almost a contradiction to your
previous assertion that there is no sensible default behaviour in
absence of a lifecycle mapping?
Jochen
