> From: Maczka Michal [mailto:[EMAIL PROTECTED] > > No! preGoals should not be used by plugins.
Ok, so these aren't behaving themselves? cache\maven-antlr-plugin-1.2\plugin.jelly(59): <preGoal name="java:compile"> cache\maven-antlr-plugin-1.2\plugin.jelly(63): </preGoal> cache\maven-html2xdoc-plugin-1.3\plugin.jelly(102): <preGoal name="xdoc:jelly-transform"> cache\maven-html2xdoc-plugin-1.3\plugin.jelly(108): </preGoal> cache\maven-latex-plugin-1.2\plugin.jelly(82): <preGoal name="xdoc"> cache\maven-latex-plugin-1.2\plugin.jelly(86): </preGoal> > > At the moment indeed the solution which involves plugin > requires very short duplicating blocks in maven.xml. > Probably we will be able to eliminate the need for most of > them and even maven.xml themselves if we will have workflow > which might be parametrized. E.g java:compile goal might > depend on java:runCodeGenerator goal which by default might be nop. > and you will be able to define alias java:runCodeGenerator - > > xdoclect:hibernatedoclet. > So in the such common cases no scripting will be ever needed. > But that's not yet official - that's just one of the possibilties. > > Michal This brings me back to my previous email. 1. Does maven.xml inheritance currently only happen when sub-projects run within the reactor? 2. Does project.properties and build.properties inheritance currently only happen when sub-projects are run within the reactor? If so, what's the reasoning behind this decision? Thanks, Matt. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
