[ http://jira.codehaus.org/browse/MPECLIPSE-70?page=comments#action_43267 ]
Felipe Leme commented on MPECLIPSE-70:
--
Eric/Brett,
I found another use case wher this customization is useful: when doing expanded
deploy on JBoss (or other application server
The following comment has been added to this issue:
Author: David Eric Pugh
Created: Thu, 3 Feb 2005 11:55 AM
Body:
The fundamental solution for quite a few of these types of "customizations" is
to reuse any existing .project or .classpath files. This way the Maven Eclipse
plugi
The following comment has been added to this issue:
Author: Felipe Leme
Created: Wed, 2 Feb 2005 9:44 PM
Body:
> If you can change the plugin to update an existing one rather than
> overwrite, you get that benefit too.
Do you mean adding a merge capability to the plugin? Yes, tha
The following comment has been added to this issue:
Author: Brett Porter
Created: Wed, 2 Feb 2005 8:26 PM
Body:
> so, with Maven, we just need to run 'maven eclipse' and the
> dependencies are automatically updated.
If you can change the plugin to update an existing one rather th
The following comment has been added to this issue:
Author: Felipe Leme
Created: Wed, 2 Feb 2005 8:09 PM
Body:
Hi Brett,
I don't want to start a flame war here, but by changing the linked resources on
the IDE would require a manual tuning on the .project and I like the way that
The following comment has been added to this issue:
Author: Brett Porter
Created: Wed, 2 Feb 2005 7:48 PM
Body:
the better solution here is to make the eclipse plugin not overwrite existing
linkedResources, and use the GUI to set them up in the first place.
I'm -1 to adding a kit
The following comment has been added to this issue:
Author: Felipe Leme
Created: Wed, 2 Feb 2005 7:14 PM
Body:
Hi Trygve,
Yes, I agree with you. But believe me, that cannot be done in my case. This is
my main rant about Maven: it forces the projects to adapt to Maven, not the
op
The following comment has been added to this issue:
Author: Trygve Laugstol
Created: Wed, 2 Feb 2005 6:57 PM
Body:
I really don't think that this is a good idea to implement. You should really
share the source as either a Maven artifact or make a Eclipse project out of
the common
