Nau, Mike wrote at Donnerstag, 15. Oktober 2009 23:31: > Was able to finally figure this out - posting here in case someone else > runs into the same issue. > > New classes were recently added to the failing module without an explicit > package defined (they were added directly under src/main/java). Doing this > triggered a bug in the javadoc compiler detailed in > http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=5101868 when the -use > flag is used when generating javadocs (stacktrace included below). > > We only saw this error when performing the maven release:perform goal. > Apparently maven sets the -use javadoc flag as part of the release:perform > goal, but not as part of a normal non-release build. So we never saw this > on developer workstations or our SNAPSHOT builds. > > The fix was to relocate the classes added from the default package to > com.foo.install which side-stepped javadoc bug. Another option we tested > was to explicitly set the use=false flag within the tcs-prod-tool's > pom.xml file which also worked.
You're aware that the settings made for the javadoc plugin in the plugins section of report have nothing to do with the settings made in the plugins section of build? - Jörg --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
