[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [m2e-users] The reasons I feel disappointed with m2e 1.0
|
Hi Igor,
Thanks for sharing the rationale with me. I had a quick look and I can see why the decision has been made. As long as there is convenient alternative for the missing features I'm fine.
Cheers,
Tomasz
On Fri, Jul 8, 2011 at 4:24 PM, Igor Fedorenko
<igor@xxxxxxxxxxxxxx> wrote:
As it was mentioned already, it should be possible to reintroduce
dropped pom editor tabs via thirdparty extensions. If such extensions
prove to be popular and of good quality we will certainly consider
accepting them back to m2e core, provided extension's developers will be
willing to support them.
Running Maven build phases as part of project import/configuration/build
is not coming back (see [1] for reasons why). At the same time, we
believe that the new build lifecycle mapping framework we introduce in
1.0 provides much better alternative and we expect Maven plugin coverage
improve as more m2e extensions are contributed to m2e marketplace
catalog. Community participation is the key here, so if you are
interested to help with JAXB POJOs or any other code generation plugin
support, [2] provides initial pointers and we'll be happy to answer
further questions on m2e-dev mailing list.
[1] http://wiki.eclipse.org/M2E_plugin_execution_not_covered
[2] http://wiki.eclipse.org/M2E_Extension_Development
--
Regards,
Igor
On 11-07-08 6:56 PM, Tomasz Blachowicz wrote:
Hi there,
I've been using M2Eclipse feature with my Eclipse IDE for last year or
so on daily basis and I always were very happy with the tool. Today I
decided to upgrade to Indigo bundle and new m2e feature and I must say
I'm disappointed, because many of the useful features of M2Eclipse 0.12
(last of releases managed by Sonatype) has been dropped in m2e 1.0
release. Igor Fedorenko in his e-mail today has kindly mentioned that
some tabs and features has been removed and the team has decided to
concentrate on other useful features. I don't really agree this was good
idea and there is certainly a good few features that I'll be missing:
* The plug-in tab with search for plugins (How many of you actually
remember the full name of jaxb plugin and it's latest version?) and
really great support for custom plugin configuration. That was great
simplification for me and I believe other users working with complex pom
files.
* New dependency tab is not great. In the M2Eclipse 0.12 one could got
to editing of the artifact details in the right pane just by clicking on
the artifact on the list. Now the new pop-up window appears to do the same.
* The graphical representation of dependencies was nice feature. Maybe
not for large projects, but still quite useful. I'll be missing this
feature.
* In M2Eclipse 0.12 there was possibility to run specific goals on
project import and project configuration update. I found this very, very
useful when working with projects that generate code. By calling goals
automatically I stayed assure that all my generated classes (e.g. JAXB
POJOs) are up-to-date and the project compiles fine just after import.
I'd like to highlight that I really appreciate the hard work you guys
doing there and I'm really happy that Maven integration has become
top-level project in Eclipse finally. However dropping features/plugins
that advanced users like myself have been using extensively is not the
best idea in my view. Is there any chance to bring the dropped features
back to m2e?
Regards,
Tomasz Blachowicz
