On Mon, Mar 1, 2010 at 1:10 PM, sebb <seb...@gmail.com> wrote: > On 01/03/2010, sebb <seb...@gmail.com> wrote: >> On 01/03/2010, Niall Pemberton <niall.pember...@gmail.com> wrote: >> > Hi, >> > >> > I'd like to release version 13 of the commons-parent pom - the changes >> > since the last release are: >> > >> > - Upgrade to use commons-build-plugin 1.2 (for improved download pages) >> > - Change OSGi config to not import exported packages >> > - only generate javadocs, rather than full site in the "rc" profile >> > (fixes problem with multi-module components) >> > - Upgrade from version 4 to 7 of the apache parent pom >> > - Upgrade maven plugins to latest release versions >> > >> > A full diff of the pom.xml can be found at this address: >> > >> http://svn.apache.org/viewvc/commons/proper/commons-parent/trunk/pom.xml?r1=917324&r2=827809&diff_format=h >> > >> > The version number in the pom will be updated automatically during the >> > release process. >> > >> > [ ] +1 >> > [ ] =0 >> > [ ] -1 >> > >> > Vote is open for 72 hours >> >> >> I've discovered a problem with the parent pom: >> >> javadoc:jar reports: >> >> [INFO] task-segment: [javadoc:jar] >> [INFO] >> ------------------------------------------------------------------------ >> [WARNING] DEPRECATED [aggregate]: since 2.5. Use the goals >> <code>javadoc:aggregate</code> and <code>javadoc:test-aggregate</code> >> instead. >> [INFO] [javadoc:jar {execution: default-cli}] >> [INFO] >> > > Deleting line 330 > <aggregate>false</aggregate> > seems to do the trick when experimenting with EXEC, but I've no idea > if dropping the line will cause errors in other projects.
I have removed this. > Also just noticed that > > mvn javadoc:test-jar > > does not include the N&L files in the jar, I looked at fixing this - but we currently have the "antrun" plugin configured to do this - but it doesn''t get executed when that single goal is done (neither does mvn javadoc:jar include the N&L - its tied to a standard phase, so you have to do something like mvn package. So unless someone else has an idea, I don't know how to fix this. > and the MANIFEST does not > have the same details as the main code javadoc jar. Not essential, but > if it can be fixed easily then let's add it? I've fixed this - also same problem occurred whe running mvn javadoc:jar which is now fixed: Niall >> >> > Niall >> > >> > --------------------------------------------------------------------- >> > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >> > For additional commands, e-mail: dev-h...@commons.apache.org >> > >> > >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
