Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MAVEN-1560
Here is an overview of the issue:
-
Key:
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MPECLIPSE-71
Here is an overview of the issue:
-
Ke
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
Hi Brett,
Have we decided about adding this feature to 1.1 yet? If not, I can open
a jira issue for that (I think this is a very important feature).
In fact, I've been thinking better about the problem and would like to
suggest a slightly different approach: instead of having a true/false
attribu
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 7:00 PM
Body:
What use case is this? Are you mixing example code with production code?
-
View this comment:
htt
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
The following comment has been added to this issue:
Author: Leo Fang
Created: Wed, 2 Feb 2005 2:41 PM
Body:
How about the use case of sample source files in addition to source files and
test source files?
-
View t
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MAVEN-1559
Here is an overview of the issue:
-
Key:
The following comment has been added to this issue:
Author: Dan Tran
Created: Wed, 2 Feb 2005 11:21 AM
Body:
This is the block of code that should be replace in plugin.jelly.
Note I added one more statement to copy _.lib to
desired full name. I will try to learn SVN patching syst
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MPECLIPSE-70
Here is an overview of the issue:
-
Ke
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MAVENUPLOAD-297
Here is an overview of the issue:
-
Hi Brett,
Have we decided about adding this feature to 1.1 yet? If not, I can open
a jira issue for that (I think this is a very important feature).
In fact, I've been thinking better about the problem and would like to
suggest a slightly different approach: instead of having a true/false
attribu
Author: brett
Date: Wed Feb 2 01:01:28 2005
New Revision: 149500
URL: http://svn.apache.org/viewcvs?view=rev&rev=149500
Log:
workaround change in x:set
Modified:
maven/maven-1/plugins/trunk/xdoc/plugin.jelly
Modified: maven/maven-1/plugins/trunk/xdoc/plugin.jelly
URL:
http://svn.apache.org
17 matches
Mail list logo