> However, now I only really need those goals to execute on the children. Is > there a way to bind & configure the goals in the parent but only have them > execute in the children?
The neatest way to do it would be to define a profile in the parent that switched off the goals you neded, and then override in the children to switch them back on selectively. I played with this a bit, but there are unfortunately still many issues outstanding (browse JIRA and you will see) to do with profile inheritance, and it didn't seem to work very well. I ended up with a solution that is quite particular to the problem we were discussing (installing third-party jars): I just use an antrun task to prepare the jar for installation, and use the <available> task in ant to decide whether the project has a jar to deploy. The parent projects do not, and the leafs gerenrall do. There are probably still other tricks you can play with local properties and profiles. -- View this message in context: http://www.nabble.com/Optional-Goals---Dependencies-tf2081628.html#a5810379 Sent from the Maven - Users forum at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
