RE: Disable certain goal dependencies?
Set maven.test.skip=true somewhere or if it is temprary provide it as -D option > -Original Message- > From: Guy Davis [mailto:[EMAIL PROTECTED] > Sent: Tuesday, February 22, 2005 4:58 PM > To: Maven Users List > Subject: Disable certain goal dependencies? > > > Hi there, > > We recently started using the Jar goal to create our jar. > However, the > Test goal seems to be dependency for this goal. Is it possible to > disable the need to run the unit tests before the jar goal is > run? If > so, how? > > Thanks, > Guy > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Disable certain goal dependencies?
Hi there, We recently started using the Jar goal to create our jar. However, the Test goal seems to be dependency for this goal. Is it possible to disable the need to run the unit tests before the jar goal is run? If so, how? Thanks, Guy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: goal dependencies
Simon Matic Langford wrote: > is it possible to make a goal depend on another goal, similar to ant > targets? > > I can put an tag in my goal, but that causes the goal to > be run, regardless > of whether or not it has been run before, and some goals do their thing > everytime, regardless > of whether they've been run, which I'm sure is sometimes necessary (eg > clover needs test:test to > run again because it instruments the code). Unless goals (and plugins) > should check better > to see if they need to run? ... R. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
goal dependencies
is it possible to make a goal depend on another goal, similar to ant targets? I can put an tag in my goal, but that causes the goal to be run, regardless of whether or not it has been run before, and some goals do their thing everytime, regardless of whether they've been run, which I'm sure is sometimes necessary (eg clover needs test:test to run again because it instruments the code). Unless goals (and plugins) should check better to see if they need to run? thanks simon The information contained in this e-mail is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. If You are not the intended recipient of this e-mail, the use of this information or any disclosure, copying or distribution is Prohibited and may be unlawful. If you received this in error, please contact the sender and delete the material from any computer. The views expressed in this e-mail may not necessarily be the views of The PCMS Group plc and should not be taken as authority to carry out any instruction contained.