[ http://jira.codehaus.org/browse/MANT-23?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vincent Siveton closed MANT-23. ------------------------------- Resolution: Fixed Added javadoc task > Make the ant plugin able to generate javadoc targets into build.xml files > ------------------------------------------------------------------------- > > Key: MANT-23 > URL: http://jira.codehaus.org/browse/MANT-23 > Project: Maven 2.x Ant Plugin > Issue Type: New Feature > Affects Versions: 2.0-beta-1 > Reporter: Petteri Räty > Assigned To: Vincent Siveton > Fix For: 2.0-beta-2 > > > [EMAIL PROTECTED] /mnt/checkouts/maven-ant-plugin $ grep -i javadoc -r . > ./src/it/ear-it/primary-source/.svn/text-base/pom.xml.svn-base: > <artifactId>maven-javadoc-plugin</artifactId> > ./src/it/ear-it/primary-source/pom.xml: > <artifactId>maven-javadoc-plugin</artifactId> > [EMAIL PROTECTED] /mnt/checkouts/commons-dbutils-trunk $ grep -i javadoc > maven-build.xml > [EMAIL PROTECTED] /mnt/checkouts/commons-dbutils-trunk $ > For Gentoo packaging and for me being able to include maven generated > build.xml files in source releases I need to be able to generate javadocs > using the build.xml files. The standard target layout for self written > build.xml files I have come across is: > -compile > -jar (We have this as package, would be nice to name this after the thing it > does so jar would be jar and ear would be ear but that is an another bug) > -test > -javadoc > -dist (dummy target depending on jar, test and javadoc) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira