Hi all, OK, given the deafening silence, I posted it on SO: http://stackoverflow.com/q/26787825/1207769
Regards, Curtis On Wed, Nov 5, 2014 at 12:42 PM, Curtis Rueden <[email protected]> wrote: > Hi everyone, > > I am trying to generate an aggregated set of javadocs from a collection of > related projects, like so: > > > https://github.com/imagej/imagej-javadoc/blob/83d2fe7f2d546cdc0971f323dfaf56d0089e715d/pom.xml > > Basically, this POM project declares a bunch of dependencies and then uses > the maven-javadoc-plugin's > <includeDependencySources>true</includeDependencySources> option. > > Some of the dependencies have a "script-templates" folder in their > resources, which gets lumped into the "-sources" JAR by the > maven-source-plugin. > > Unfortunately, the javadoc tool hates seeing folders with violate java > package naming conventions. So my build ultimately fails with: > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-javadoc-plugin:2.9.1:jar (attach-javadocs) > on project imagej-javadoc: MavenReportException: Error while creating > archive: > [ERROR] Exit code: 1 - javadoc: error - Illegal package name: > "script-templates.Java" > > I tried adding <excludePackageNames>script-templates</excludePackageNames> > to the maven-javadoc-plugin configuration, but it seemed to have no effect. > > Does anyone have ideas how to work around this problem? > > Thanks, > Curtis > > P.S. I could rename the "script-templates" folders in all of the > dependencies, and then update the code to handle both the old and new > resource locations, and then release new versions of them all, but that > would be a substantial amount of work. And the problem could still crop up > again later if any other incompatibly-named folders appear in any > "-sources" JARs. >
