|Re: [m2e-users] Improved "import maven project" workflow in m2e 1.5.0|
Heh. This is the first time I hear someone uses working sets as working
All people I talked to before use working sets as a workaround for
lack of proper multimodule project support. It was certainly annoying
following the same 5+ steps process needed to create and select new
working set each time I imported a project. The updated wizard is
definite improvement for my workflow.
Unfortunately, I don't see a good way to automatically and conveniently
group modules of the same aggregator and to allow flexible
working set selection during import. Any suggestions anybody?
On 2013-10-02 6:40 PM, Andrew Holland wrote:
I tend to have a lot of single maven projects, these are normally
grouped under plugins or utils working sets, for multi-module projects
these are generally in there own working sets.
how about having radio buttons (generate working set/choose working
set), this could grey out the old select dialog that was there previously?
On 2 October 2013 23:12, Igor Fedorenko <igor@xxxxxxxxxxxxxx<mailto:igor@xxxxxxxxxxxxxx>> wrote:
How often do you import multi-module projects into existing working set?
Can you describe your workflow that leads into this?
On 2013-10-02 5:53 PM, Andrew Holland wrote:
i liked the old way to choose an existing working set, wouldn't
better to have the old drop down with a button to create a new
On 30 September 2013 15:33, Fred Bricon <fbricon@xxxxxxxxx
<mailto:fbricon@xxxxxxxxx> https://bugs.eclipse.org/bugs/__show_bug.cgi?id=409732<mailto:fbricon@xxxxxxxxx <mailto:fbricon@xxxxxxxxx>>> wrote:
we've made some drastic changes in the way the "Import Maven
projects" workflow in m2e 1.5.0 . Previously, when
directory of projects to import, m2e spent a huge amount of
analyzing potential lifecycle mapping errors and discover
fixes from remote connectors, before you could even choose
specific projects to import.
That lifecycle mapping analysis has been deferred to *after*
projects are imported and it only checks for *actual*
before trying to discover the world. The discovery
has also been greatly optimized.
It means the 1st page of the maven import wizard can now
less than a couple second (usually << 1s), instead of up to
One caveat is it won't try to discover connectors that for
whose lifecycle is already covered. ex: the mavenarchiver
won't be proposed for download if the maven-jar-plugin has
The lifecycle mapping discovery refactoring led to a few
classes to be deleted or changed in a non backward
so if you built some m2e extensions over these, you might
affected. Check  to see the extent of the changes.
So, please, give the latest dev build a try  and let's
good or bad the changes are from your perspective.
"Have you tried turning it off and on again" - The IT Crowd
m2e-users mailing list
m2e-users mailing list
Back to the top