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 attribute, we could have one with many options for many expected behaviors. For instance: <attainGoal name="test:test" multipleRuns="allowed"/> Default value (for backwards compatibility), allows a goal to be attained multiple times. <attainGoal name="test:test" multipleRuns="ignores"/> Ignores the second and later runs of a goal, i.e., runs it only once <attainGoal name="test:test" multipleRuns="forbidden"/> Throws an exception if the goal is run more than once. Regarding the backward compatibility, I'd like to go one step further and define a property with the default value (for tags that don't carry the attribute). This default property in turn would be set as 'allowed', but could be changed by the user (otherwise, it would requires a lot of changes in large projects). What do you guys think? -- Felipe On Sun, 2004-08-01 at 18:38, Felipe Leme wrote: > 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 propose something like because I'm facing such an issue > while porting the Jakarta Taglibs to maven (I created a goal called > tld:generate and it is being called a lot of times, as it's a preGoal > for many pristine Maven goals). > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
