Hi Steven, Tks for the explanation. I should have seen that from the ant targets!
Diverging from the thread title and probably already discussed... but why pom are not committed and maintained in SVN?
(Even if 'mvn install' works fine, I still have issues importing the modules hierarchy in eclipse due to e.g. the src/test-framework module. Having pom in trunk would allow to fix this one for all.)
Thx. On 04/07/11 20:07, Steven A Rowe wrote:
Hi Eric, 'ant get-maven-poms' will generate the pom.xml files for you. 'ant generate-maven-artifacts' has to generate the javadoc for each module, and javadoc generation fails on warnings. When the javadoc tool fails to download the package list from Oracle, which seems to happen often, the resulting warning fails the build. Steve -----Original Message----- From: Eric Charles [mailto:[email protected]] Sent: Monday, July 04, 2011 5:07 AM To: [email protected] Subject: failonjavadocwarning to false for ant generate-maven-artifacts Hi, In current trunk, I had to set failonjavadocwarning to false to successfully generate the pom (via ant generate-maven-artifacts). (invoking ant javadoc in lucene folder also fails). I was simply looking for the pom.xml generation, but much more was done. I'm not worry about that (just willing to share it). Thx. -- Eric --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
-- Eric --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
