I *do* feel your pain and I understand the problems you are having.
the m2eclipse plugin is actually participating in the build that
Eclipse initiated (which it does do after every code change), which
helps keep things in sync. What exactly it does will depend on what
needs doing (for instance if you have a lot of filtered resources,
it's going to take longer).
About your corrupt modules... I also get that from time to time, but I
usually find that happens if there is an error some place like in a
POM file. Finding it and fixing it usually resolves the problem.
You may be able to turn off that auto build... earlier versions of the
plugin didn't do it but you'd end up with partial builds on the
eclipse side and more of a mess than was worth it.
You can also make sure you have run a build in the console as it will
speed up the m4e plugin (it doesn't have to download anything).
I think that if your happy with the mvn eclipse:eclipse method of
working, then you don't really need to change.. your modules are
clearly designed for it and the m2e plugin does pretty much the same
thing anyway.
I guess it's a bit unfortunate that you had so much trouble with it,
but I can tell you that I use the m4e plugin every hour of every
working day without any trouble. I think part of why it works so well
for me is that I keep my modules small and flat (little to no nesting)
and so *don't even notice* when it's building... it may be that it
works for me because of how I work and organize my projects.
So, the other plugin I was talking about is the q4e plugin... I was
very not impresses when I tried it. You can check it out yourself at:
http://code.google.com/p/q4e/
Also, I noticed before that the q4e plugin was going into Eclipse,
however I now see that the m4eclipse plugin is becoming an official
plugin:
http://www.eclipse.org/m2e/
- Brill Pappin
On 27-Feb-09, at 2:38 AM, Emond Papegaaij wrote:
That is the plugin Martijn is talking about, and I am one of the co-
workers he
mentioned. I tried the m2eclipse plugin and used it for a day. The
plugin
(version 0.9.7.200902090947) was able to checkout the project from
svn and
create eclipse projects for all modules, so far so good, although
the browse
button in the svn window didn't work. At that moment the trouble
started.
Somehow, after even the slightest code change, eclipse started to
rebuild the
entire project over and over, taking ages. After some more changes
(some of
them might have been in the pom), some of my projects got corrupted
and I had
to clean everything, doing a complete rebuild. A few hours later,
while I was
working on a Java file, about 30,000 errors suddenly appeared.
Somehow,
m2eclipse had reversed some of my module-to-module dependencies. I
tried
cleaning, updating, refreshing the project configuration, nothing
helped. I was
unable to get the project to build again.
My experience with m2eclipse is that it is slow and very unstable.
My last
attempt was not the first attempt. I tried to use it several times,
because
running mvn eclipse:eclipse all the time is just a pain in the *,
but every
time I ran into some strange problem I could not solve.
Emond Papegaaij
On Thursday 26 February 2009 17:20:04 Brill Pappin wrote:
I don't think we're talking about the same plugin then (although you
seem to be calling it the same thing)...
I'm referring to:
http://m2eclipse.codehaus.org/
It's the *only* one I've found that *actually works* properly,
particularly for larger projects... although I run the dev version so
I'm not sure how well the released version is working at this moment.
Of course I could simply go back to the console and use the maven
plugin to generate the eclipse project files, but I find the plugin
to
be light-years ahead in maintaining a clean build env.
I guess people's experience with various tools also depends a lot on
*how* they work not just what they work with :)
- Brill Pappin
On 24-Feb-09, at 12:38 PM, Martijn Dashorst wrote:
m2eclipse is absolutely worthless for anything beyond a
quickstart. It
is constantly reparsing poms, grinding eclipse to a halt. It
failed to
generate the right project dependencies for our multimodule project
that consists of 2 multimodule child projects. It failed miserably
to
uninstall, needing me to axe my eclipse installation.
In short: my experience (and that of my co-workers) with m2eclipse
is
that it is far from ready for prime time.
Martijn
On Tue, Feb 24, 2009 at 5:55 PM, Brill Pappin <br...@pappin.ca>
wrote:
I should add something about the Eclipse maven plugins... don't go
for the
official eclipse Q4 plugin... use the "Maven Integration 4 Eclipse"
plugin
(and actually the development version if your jiggy with it, it
works and
gets updated/fixed way more often).
If your on Netbeans, I think Maven will generate Netbeans project
files for
you as well (it will do so for eclipse), so you could actually flip
back and
forth if you wanted.
- Brill Pappin
On 23-Feb-09, at 5:19 PM, Pierre Goupil wrote:
+1, I like Wicket Bench. And with M2Eclipse, you have the full
sources &
JavaDoc just by adding Wicket as a dependency, which is very
convenient.
But
don't expect Wicket Bench to do too much, it's just a small,
useful tool.
Pierre
Hi, I use Eclipse with Wicket Bench plugin and it works very
fine.
--
Sans amis était le grand maître des mondes,
Eprouvait manque, ce pour quoi il créa les esprits,
Miroirs bienveillants de sa béatitude.
Mais au vrai, il ne trouva aucun égal,
Du calice du royaume total des âmes
Ecume jusqu'à lui l'infinité.
(Schiller, "l'amitié")
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
--
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.3.5 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
