Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MPPMD-13
Here is an overview of the issue:
-
Key: M
Ok, then I agree with Eric, it will be helpful.
And rememeber that you're on holiday! Have a good time!
> -Original Message-
> From: Brett Porter [mailto:[EMAIL PROTECTED]
> Sent: Saturday, July 31, 2004 5:17 PM
> To: Maven Developers List
> Subject: RE: Avoid running multiple goals (was
Message:
The following issue has been reopened.
-
View the issue:
http://jira.codehaus.org/browse/MPXDOC-47
Here is an overview of the issue:
-
Key
If you -only- use prereqs, goals will only be attained once. As soon as attainGoal is
run, a
new WerkzSession is started, so all the goals are fair game.
- Brett
Quoting Carlos Sanchez <[EMAIL PROTECTED]>:
> So if I add "prereqs" to a goal they won't be run again? Is this in any doc?
> Then th
Wow... If it's easy, I say go for it.. There are a lot of situations
where plugins call test:compile, java:compile, and other well known goals
just to ensure that the step happened.. I can see this attribute being very
useful..
Can you share what types of backwards compatibility affects this w
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MPDASHBOARD-8
Here is an overview of the issue:
-
K
So if I add "prereqs" to a goal they won't be run again? Is this in any doc?
Then there's no new functionality needed, only use prereqs and attainGoal
properly ?
> -Original Message-
> From: Brett Porter [mailto:[EMAIL PROTECTED]
> Sent: Saturday, July 31, 2004 4:12 PM
> To: Maven Develop
There is an issue in JIRA for this. it is really easy for me to enable this feature,
but it breaks
existing builds. If we can sacrifice backwards compat., then I'm happy to do it.
It already works for prereqs.
I was actually thinking it would be better to add an attribute to the attainGoal that
dion2004/07/31 04:54:09
Modified:.project.properties
Log:
exclude example plugin as it fails install
Revision ChangesPath
1.16 +1 -1 maven-plugins/project.properties
Index: project.properties
===
dion2004/07/31 04:53:15
Modified:plugin project.properties
Log:
Tests fail under jdk1.3
Revision ChangesPath
1.6 +1 -0 maven-plugins/plugin/project.properties
Index: project.properties
===
dion2004/07/31 04:52:23
Modified:hibernate project.properties
Log:
Tests fail under jdk1.3
Revision ChangesPath
1.8 +1 -0 maven-plugins/hibernate/project.properties
Index: project.properties
===
The following issue has been updated:
Updater: Joachim Bader (mailto:[EMAIL PROTECTED])
Date: Sat, 31 Jul 2004 7:05 AM
Comment:
- Add support for native dependencies (libset/syslibset)
Attention, it was neccessary to change the direcotory for native components in the
repository. It
The following comment has been added to this issue:
Author: dion gillard
Created: Sat, 31 Jul 2004 6:14 AM
Body:
If we want to have a jar of the test classes, the code should be in the test plugin.
-
View this comm
Message:
The following issue has been reopened.
Reopener: Arnaud HERITIER
Date: Sat, 31 Jul 2004 5:23 AM
We must replace the value of the maven properties by the maven properties themself.
-
View the issue:
http:/
The following comment has been added to this issue:
Author: Arnaud HERITIER
Created: Sat, 31 Jul 2004 5:22 AM
Body:
Ok. I'll modify it.
-
View this comment:
http://jira.codehaus.org/browse/MPANT-9?page=comments#a
15 matches
Mail list logo
