[
https://issues.apache.org/jira/browse/EXLBR-33?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leo Simons closed EXLBR-33.
---------------------------
Resolution: Fixed
Fix Version/s: 2.2
we've now (finally!) moved to maven 2, which has automagic javadoc generation
support.
> javadoc targets in the build.xml files of released source tarballs are broken
> -----------------------------------------------------------------------------
>
> Key: EXLBR-33
> URL: https://issues.apache.org/jira/browse/EXLBR-33
> Project: Excalibur Components
> Issue Type: Bug
> Components: Pool
> Affects Versions: 2.1
> Reporter: Petteri Räty
> Fix For: 2.2
>
> Attachments: 2.1-build.xml-javadoc.patch
>
>
> javadoc:
> [mkdir] Created dir:
> /var/tmp/portage/dev-java/excalibur-pool-impl-2.1/work/excalibur-pool-impl/dist/docs/api
> BUILD FAILED
> /var/tmp/portage/dev-java/excalibur-pool-impl-2.1/work/excalibur-pool-impl/build.xml:207:
> No source files and no packages have been specified.
> Total time: 1 second
> !!! ERROR: dev-java/excalibur-pool-impl-2.1 failed.
> Call stack:
> ebuild.sh, line 1593: Called dyn_compile
> ebuild.sh, line 951: Called src_compile
> ebuild.sh, line 1282: Called java-pkg-2_src_compile
> java-pkg-2.eclass, line 69: Called eant 'jar' 'javadoc' '-f' 'build.xml'
> java-utils-2.eclass, line 1395: Called die
> http://apache.mirrors.webazilla.nl/excalibur/excalibur-pool/source/
> Experienced with both excalibur-pool-api-2.1-src.tar.gz and
> excalibur-pool-impl-2.1-src.tar.gz so probably affect instrumented too.
> I think the build.xml is generated from some maven files inside your svn so
> hopefully you know where to fix it.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
