When you start doing lots of weird things, it is sometimes better to copy the plugin in question, and create "myplugin" to do this stuff. Otherwise you are constantly testing against changes made to the javadoc plugin. Especially when they are somewhat unusual requirements.
> -----Original Message----- > From: Eirik Torske [mailto:[EMAIL PROTECTED] > Sent: Thursday, November 25, 2004 9:49 AM > To: [EMAIL PROTECTED] > Subject: Using the Javadoc Plugin with multiple source trees > > > Our project has multiple source trees. > We have our production code - but also our unit tests, > requirement tests and integration tests. > For several reasons we want _individually generated_ > Javadoc for these source trees. > > The Problem: > It seems impossible to manipulate the > ${maven.compile.src.set} property in the Javadoc > Plugin... > What does this line really mean (in the Javadoc Plugin > 'plugin.jelly')? > maven.compile.src.set = > [${context.getAntProject().getReferences().get('maven.compile.src.set')}] > > > The Dream: > What I would like to do is just override the > properties of choice and execute the plugin. > Something like this: > > <goal name="javadoc:requirementtest" > description="Generate API documentation for the > requirement tests"> > <j:set var="maven.compile.src.set" > value="${my.requirementtest.src.dir}"/> > <attaingoal name="javadoc"/> > </goal> > > ...this don't work with the Javadoc Plugin. > At present, we are using the <ant:javadoc> in a > custom-made goal, but we would rather use the plugin > directly. > > Is it possible? What is the trick? > > Thanks > Eirik > > > --------------------------------------------------------------------- > 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]
