David Balazic wrote:
What is the JIRA number ?
Like I said, all you should do is disable source and javadoc
downloading in Maven settings, if that doesn't help, then there is
something else.
It is also a problem when cleaning a project.
Instead of cleaning and rebuilding just that project, eclipse goes and does
something
(I am not sure if it cleans, builds or whatever, but it sure does take time;
the progress view
shows that something with each projects pom.xml file is being done) with all
other
projects.
That is not related to the source downloading, but you should be able
to verify it by monitoring Maven console on Console view. We have fixed
some issues related to that and fix will be included into the 0.0.12
build (once we re-release it).
And when it finishes, the original project still is marked red (having error),
when
a simple command line "mvn clean install" finishes successfully in a few
seconds.
Can you please be little more specific? Exactly what errors you are
getting?
With this new version (I still not sure if it is eclipse or m2clipse) work
becomes 10 times
slower. Plus there are more misterious build failures. Several of my coworkers
tried
eclipse/m2 3.3.1/0.0.11 and then reverted to 3.1.2/0.0.9
This must have high priority. It is unusable in any multi project environment
David, to make it any priority we really need something more specific
then mysterious failures and some errors. Right now I don't even sure if
you are referring to version 0.0.11 or 0.0.12...
To fix that stuff we have to reproduce it in our own environment and
it is practically impossible without your help. For some hints see the
following wiki page.
http://docs.codehaus.org/display/M2ECLIPSE/How+To+Report+Issues
regards,
Eugene
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
