To edit this page: http://maven.apache.org/plugins/maven-antrun-plugin/run-mojo.html
you edit the javadoc descriptions here: https://svn.apache.org/repos/asf/maven/plugins/trunk/maven-antrun-plugin/src/main/java/org/apache/maven/plugin/antrun/AntRunMojo.java To edit this page: http://maven.apache.org/plugins/maven-antrun-plugin/usage.html You would edit: https://svn.apache.org/repos/asf/maven/plugins/trunk/maven-antrun-plugin/src/site/apt/usage.apt As you can see, it is very straightforward. To generate the documentation, run "mvn site" and look at target/site/index.html. Here is info on how to submit it and more: http://maven.apache.org/guides/development/guide-m2-development.html#Creating%20and%20submitting%20a%20patch HTH, Brett On 11/18/05, Lee Meador <[EMAIL PROTECTED]> wrote: > Thanks for the help. It seems to be working for me. > > http://maven.apache.org/plugins/maven-antrun-plugin/run-mojo.html > > Thats where it tells about the config stuff for the antrun plugin. > > The testSourceRoot attribute is missing and there is no description on the > others. > > I'm willing to think about fixing such a thing in the documentation but have > no clue how to do so. I could spend an hour or two on it including ramp up > time. So ... since I'm counting the cost ... what is the cost in time to do > this. I guess I need to know before volunteering. > > Thanks. > > -- Lee Meador > > On 11/17/05, Brett Porter <[EMAIL PROTECTED]> wrote: > > > > On 11/18/05, Lee Meador <[EMAIL PROTECTED]> wrote: > > > 1) It took me a while to find and load the plugin sources. I found no > > > reference in the docs. The page that tells how to build the source does > > not > > > load the plugin source from subversion. Its at: > > > > > > http://maven.apache.org/guides/development/guide-building-m2.html > > > > My bad - I moved it and haven't gotten to update that page yet. > > > > > Then I just use the <sourceRoot> tag (or <testSourceRoot> for test code) > > to > > > tell maven2 to compile the stuff in the folder that I put in there. I > > don't > > > know if you can put more than one relative path in there. I doubt it but > > > don't understand the implications of what's in the java source very > > well. > > > > Neat. This also needs to be documented, as does the > > .dependency.classpath feature and the inclusion of optional task > > dependencies inside the plugin tag. Anyone? > > > > > Question: Is there a way to parameterize the folder in that tag so that > > I > > > don't put "target" but put something that will use whatever the build > > > directory should be? > > > > ${project.build.directory} > > > > Cheers, > > Brett > > > > > > > -- > -- Lee Meador > Sent from gmail. My real email address is [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
