Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Archived » IAM (Eclipse Integration for Apache Maven) » is the project dead?
is the project dead? [message #505946] Tue, 05 January 2010 15:41 Go to next message
Lars Sonchocky-Helldorf is currently offline Lars Sonchocky-HelldorfFriend
Messages: 13
Registered: July 2009
Junior Member
I didn't see any changes here for month, is the project still alive? It was much more vital while it was still hosted at google code.

What about the proposed collaboration with m2e?
Re: is the project dead? [message #506071 is a reply to message #505946] Wed, 06 January 2010 00:40 Go to previous messageGo to next message
Carlos Sanchez is currently offline Carlos SanchezFriend
Messages: 114
Registered: July 2009
Senior Member
There has been new features in the last month, improving WAR overlays
and EAR support. The project is quite stable right now.

m2e hasn't moved to Eclipse yet, that was something we were hoping for
to go through the IP process together and join forces.

is there any particular feature or bug that you need?


On 1/5/10 7:41 AM, Lars Sonchocky-Helldorf wrote:
> I didn't see any changes here for month, is the project still alive? It
> was much more vital while it was still hosted at google code.
>
> What about the proposed collaboration with m2e?
Re: is the project dead? [message #507276 is a reply to message #506071] Tue, 12 January 2010 17:40 Go to previous messageGo to next message
Lars Sonchocky-Helldorf is currently offline Lars Sonchocky-HelldorfFriend
Messages: 13
Registered: July 2009
Junior Member
the most annoying things are:

- "Enabling/Disabling 1 maven 2 project" takes forever (more than 10 minutes!) and has no progress bar
- first IAM build of a newly checked out project always fails when dependencies are missing (have to build at command line at first to fetch the dependencies)
- "Updating classpath container" of a project takes forever (more than 10 minutes!) and has no progress bar
Re: is the project dead? [message #507279 is a reply to message #506071] Tue, 12 January 2010 17:57 Go to previous messageGo to next message
Lars Sonchocky-Helldorf is currently offline Lars Sonchocky-HelldorfFriend
Messages: 13
Registered: July 2009
Junior Member
One more very important thing I forgot to mention:

- IAM and M2E should use the same classpathentry, now for IAM it is <classpathentry kind="con" path="org.eclipse.iam.jdt.core.mavenClasspathContainer"> while M2E uses <classpathentry kind="con" path="org.maven.ide.eclipse.MAVEN2_CLASSPATH_
CONTAINER"/>

This is very annoying since in our company some developers use IAM others use M2E. So now the .classpath files of the projects here bear eater the IAM or the M2E classpathentry, depending on who started the project. Having installed both plug ins is also not an solution since some projects even have both classpathentries in their .classpath. In this case both plugins start to fight each other (I always remove the M2E classpathentry then but others who don't know Eclipse that well have their hard time).

So please get your act together (IAM and M2E) and to come to an agreement on a common classpathentry for both of your plug ins!
Re: is the project dead? [message #507300 is a reply to message #507279] Tue, 12 January 2010 20:09 Go to previous messageGo to next message
Carlos Sanchez is currently offline Carlos SanchezFriend
Messages: 114
Registered: July 2009
Senior Member
that's actually done on purpose, because you may have both plugins
installed and Eclipse would go nuts if they use the same classpath entry.
A good practice is not to check in the .classpath and .project as they
are automatically generated by the both plugins at import time.


On 1/12/10 9:57 AM, Lars Sonchocky-Helldorf wrote:
> One more very important thing I forgot to mention:
>
> - IAM and M2E should use the same classpathentry, now for IAM it is
> <classpathentry kind="con"
> path="org.eclipse.iam.jdt.core.mavenClasspathContainer"> while M2E uses
> <classpathentry kind="con" path="org.maven.ide.eclipse.MAVEN2_CLASSPATH_
> CONTAINER"/>
>
> This is very annoying since in our company some developers use IAM
> others use M2E. So now the .classpath files of the projects here bear
> eater the IAM or the M2E classpathentry, depending on who started the
> project. Having installed both plug ins is also not an solution since
> some projects even have both classpathentries in their .classpath. In
> this case both plugins start to fight each other (I always remove the
> M2E classpathentry then but others who don't know Eclipse that well have
> their hard time).
>
> So please get your act together (IAM and M2E) and to come to an
> agreement on a common classpathentry for both of your plug ins!
Re: is the project dead? [message #507301 is a reply to message #507276] Tue, 12 January 2010 20:11 Go to previous messageGo to next message
Carlos Sanchez is currently offline Carlos SanchezFriend
Messages: 114
Registered: July 2009
Senior Member
you can open the Maven Events view and will display all the events, and
you should see what is taking the time, but the progress bar should be
working too, I don't know if there's a special case where we have a bug.

The download of dependencies definitely works, maybe you have checked
"work offline" in the Maven Preferences?


On 1/12/10 9:40 AM, Lars Sonchocky-Helldorf wrote:
> the most annoying things are:
>
> - "Enabling/Disabling 1 maven 2 project" takes forever (more than 10
> minutes!) and has no progress bar
> - first IAM build of a newly checked out project always fails when
> dependencies are missing (have to build at command line at first to
> fetch the dependencies)
> - "Updating classpath container" of a project takes forever (more than
> 10 minutes!) and has no progress bar
Re: is the project dead? [message #514702 is a reply to message #506071] Tue, 16 February 2010 11:57 Go to previous messageGo to next message
Lars Sonchocky-Helldorf is currently offline Lars Sonchocky-HelldorfFriend
Messages: 13
Registered: July 2009
Junior Member
Carlos Sanchez wrote on Tue, 05 January 2010 19:40
There has been new features in the last month, improving WAR overlays
and EAR support. The project is quite stable right now.


There are quite some bugs waiting to be fixed, but only two of them are assigned:
https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advan ced;bug_status=UNCONFIRMED;bug_status=NEW;bug_status=ASSIGNE D;bug_status=REOPENED;product=IAM

Why don't you work on those?
Re: is the project dead? [message #515501 is a reply to message #514702] Fri, 19 February 2010 02:50 Go to previous message
Carlos Sanchez is currently offline Carlos SanchezFriend
Messages: 114
Registered: July 2009
Senior Member
it's a matter of priorities and available time. Many minor/enhancement
requests and nothing really critical, workarounds available.
There are other things that committers believe are more important and
are harder for users to try to fix and that can take precedence too
(such as implementing WAR overlay support)

If users submit patches they get applied pretty fast.


On 2/16/10 3:57 AM, Lars Sonchocky-Helldorf wrote:
> Carlos Sanchez wrote on Tue, 05 January 2010 19:40
>> There has been new features in the last month, improving WAR overlays
>> and EAR support. The project is quite stable right now.
>
>
> There are quite some bugs waiting to be fixed, but only two of them are
> assigned:
> https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advan ced ;bug_status=UNCONFIRMED;bug_status=NEW;bug_status=ASSIGNED;b ug_status=REOPENED;product=IAM
>
>
> Why don't you work on those?
>
Re: is the project dead? [message #571821 is a reply to message #506071] Tue, 12 January 2010 17:40 Go to previous message
Lars Sonchocky-Helldorf is currently offline Lars Sonchocky-HelldorfFriend
Messages: 13
Registered: July 2009
Junior Member
the most annoying things are:

- "Enabling/Disabling 1 maven 2 project" takes forever (more than 10 minutes!) and has no progress bar
- first IAM build of a newly checked out project always fails when dependencies are missing (have to build at command line at first to fetch the dependencies)
- "Updating classpath container" of a project takes forever (more than 10 minutes!) and has no progress bar
Re: is the project dead? [message #571847 is a reply to message #506071] Tue, 12 January 2010 17:57 Go to previous message
Lars Sonchocky-Helldorf is currently offline Lars Sonchocky-HelldorfFriend
Messages: 13
Registered: July 2009
Junior Member
One more very important thing I forgot to mention:

- IAM and M2E should use the same classpathentry, now for IAM it is <classpathentry kind="con" path="org.eclipse.iam.jdt.core.mavenClasspathContainer"> while M2E uses <classpathentry kind="con" path="org.maven.ide.eclipse.MAVEN2_CLASSPATH_
CONTAINER"/>

This is very annoying since in our company some developers use IAM others use M2E. So now the .classpath files of the projects here bear eater the IAM or the M2E classpathentry, depending on who started the project. Having installed both plug ins is also not an solution since some projects even have both classpathentries in their .classpath. In this case both plugins start to fight each other (I always remove the M2E classpathentry then but others who don't know Eclipse that well have their hard time).

So please get your act together (IAM and M2E) and to come to an agreement on a common classpathentry for both of your plug ins!
Re: is the project dead? [message #571875 is a reply to message #507279] Tue, 12 January 2010 20:09 Go to previous message
Carlos Sanchez is currently offline Carlos SanchezFriend
Messages: 114
Registered: July 2009
Senior Member
that's actually done on purpose, because you may have both plugins
installed and Eclipse would go nuts if they use the same classpath entry.
A good practice is not to check in the .classpath and .project as they
are automatically generated by the both plugins at import time.


On 1/12/10 9:57 AM, Lars Sonchocky-Helldorf wrote:
> One more very important thing I forgot to mention:
>
> - IAM and M2E should use the same classpathentry, now for IAM it is
> <classpathentry kind="con"
> path="org.eclipse.iam.jdt.core.mavenClasspathContainer"> while M2E uses
> <classpathentry kind="con" path="org.maven.ide.eclipse.MAVEN2_CLASSPATH_
> CONTAINER"/>
>
> This is very annoying since in our company some developers use IAM
> others use M2E. So now the .classpath files of the projects here bear
> eater the IAM or the M2E classpathentry, depending on who started the
> project. Having installed both plug ins is also not an solution since
> some projects even have both classpathentries in their .classpath. In
> this case both plugins start to fight each other (I always remove the
> M2E classpathentry then but others who don't know Eclipse that well have
> their hard time).
>
> So please get your act together (IAM and M2E) and to come to an
> agreement on a common classpathentry for both of your plug ins!
Re: is the project dead? [message #571918 is a reply to message #571821] Tue, 12 January 2010 20:11 Go to previous message
Carlos Sanchez is currently offline Carlos SanchezFriend
Messages: 114
Registered: July 2009
Senior Member
you can open the Maven Events view and will display all the events, and
you should see what is taking the time, but the progress bar should be
working too, I don't know if there's a special case where we have a bug.

The download of dependencies definitely works, maybe you have checked
"work offline" in the Maven Preferences?


On 1/12/10 9:40 AM, Lars Sonchocky-Helldorf wrote:
> the most annoying things are:
>
> - "Enabling/Disabling 1 maven 2 project" takes forever (more than 10
> minutes!) and has no progress bar
> - first IAM build of a newly checked out project always fails when
> dependencies are missing (have to build at command line at first to
> fetch the dependencies)
> - "Updating classpath container" of a project takes forever (more than
> 10 minutes!) and has no progress bar
Re: is the project dead? [message #572322 is a reply to message #506071] Tue, 16 February 2010 11:57 Go to previous message
Lars Sonchocky-Helldorf is currently offline Lars Sonchocky-HelldorfFriend
Messages: 13
Registered: July 2009
Junior Member
Carlos Sanchez wrote on Tue, 05 January 2010 19:40
> There has been new features in the last month, improving WAR overlays
> and EAR support. The project is quite stable right now.


There are quite some bugs waiting to be fixed, but only two of them are assigned:
https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advan ced ;bug_status=UNCONFIRMED;bug_status=NEW;bug_status=ASSIGNED;b ug_status=REOPENED;product=IAM

Why don't you work on those?
Re: is the project dead? [message #572339 is a reply to message #514702] Fri, 19 February 2010 02:50 Go to previous message
Carlos Sanchez is currently offline Carlos SanchezFriend
Messages: 114
Registered: July 2009
Senior Member
it's a matter of priorities and available time. Many minor/enhancement
requests and nothing really critical, workarounds available.
There are other things that committers believe are more important and
are harder for users to try to fix and that can take precedence too
(such as implementing WAR overlay support)

If users submit patches they get applied pretty fast.


On 2/16/10 3:57 AM, Lars Sonchocky-Helldorf wrote:
> Carlos Sanchez wrote on Tue, 05 January 2010 19:40
>> There has been new features in the last month, improving WAR overlays
>> and EAR support. The project is quite stable right now.
>
>
> There are quite some bugs waiting to be fixed, but only two of them are
> assigned:
> https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advan ced ;bug_status=UNCONFIRMED;bug_status=NEW;bug_status=ASSIGNED;b ug_status=REOPENED;product=IAM
>
>
> Why don't you work on those?
>
Previous Topic:Extremely slow "Updating classpath" on Eclipse startup
Next Topic:Disable Dependecy Path Update
Goto Forum:
  


Current Time: Wed Nov 26 05:59:22 GMT 2014

Powered by FUDForum. Page generated in 0.03474 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software