http://jira.codehaus.org/browse/MAVEN-256
I'm not opposed to adding the other functionality, but don't see it as
critical.
- Brett
Felipe Leme wrote:
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)
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
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
On Sat, 2004-07-31 at 11:11, Brett Porter wrote:
> I was actually thinking it would be better to add an attribute to the attainGoal
> that
> defaulted to false for backwards compat, but when set to true made sure it didn't
> run again.
> We can do that in 1.1 if wanted.
+1
I was going to pro
On Sat, 2004-07-31 at 11:32, Carlos Sanchez wrote:
> So if I add "prereqs" to a goal they won't be run again? Is this in any doc?
I don't know if that's documented, but I guess yes, that's the
behaviour.
> Then there's no new functionality needed, only use prereqs and attainGoal
> properly ?
Not
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 ru
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 Developers List
&
n Developers List
> Subject: RE: Avoid running multiple goals (was: RE: issue w/ test:test
> goal being run multiple times when dist goal is executed)
>
>
> There is an issue in JIRA for this. it is really easy for me to
> enable this feature, but it breaks
> existing builds.
31, 2004 4:12 PM
> To: Maven Developers List
> Subject: RE: Avoid running multiple goals (was: RE: issue w/
> test:test goal being run multiple times when dist goal is executed)
>
> There is an issue in JIRA for this. it is really easy for me
> to enable this feature, but it breaks ex
:[EMAIL PROTECTED]
> > Sent: Friday, July 30, 2004 12:03 PM
> > To: 'Maven Users List'; [EMAIL PROTECTED]; 'Maven Developers List'
> > Subject: Avoid running multiple goals (was: RE: issue w/ test:test goal
> > being run multiple times when dist goal
, July 30, 2004 12:03 PM
> To: 'Maven Users List'; [EMAIL PROTECTED]; 'Maven Developers List'
> Subject: Avoid running multiple goals (was: RE: issue w/ test:test goal
> being run multiple times when dist goal is executed)
>
> I personally run site with junit,
I personally run site with junit, clover and jcoverage reports and would be
difficult to skip test:test.
I see it more a general question for all plugins. Maven should keep track of
goals run and don't run again them. Plugins should be able to override that,
e.g. clover could set test:test as "not
12 matches
Mail list logo
