hmm - that worked. I get the correct output.
I then executed mvn org.geotools:gt2-javadoc:javadoc on trunk and it
worked!
(note that I have not done an svn update since I last tried, so it seems
mvn install in gt/maven/javadoc did the trick, which is odd, because I
tried that before!)
Trying it on 2.2-RC3: it worked!
Checking the built zip file, it looks like only the javadocs for
gt/module were built. For the release, don't we want all javadocs to be
in the javadoc zip file?
Oh well - this is great. Now all I have to do is get the source release
archive working and then the release process is finished.
Thanks Martin!
Richard
Martin Desruisseaux wrote:
Richard Gould a écrit :
Do you get the same exception when running "mvn install" and "mvn
org.geotools:gt2-javadoc:javadoc" both on trunk?
Yeah, I get the same exception on trunk. Am I missing something?
Not necessarly, it is likely to be a bug in the custom plugin.
When invoking "mvn install" from gt/maven/javadoc module on trunk, do
you see the following lines?
[INFO] Applying extractor for language: java
[INFO] Extractor for language: java found 0 mojo descriptors.
[INFO] Applying extractor for language: bsh
[INFO] Extractor for language: bsh found 0 mojo descriptors.
[INFO] Applying extractor for language: ant
[INFO] Extractor for language: ant found 2 mojo descriptors.
The important point is the last line: it should found 2 mojos for Ant
language. If Maven said that it found 0 mojors for Ant (or worst, if it
didn't looked at all for Ant mojos), we probably have a bug there.
Martin.
-------------------------------------------------------
All the advantages of Linux Managed Hosting--Without the Cost and Risk!
Fully trained technicians. The highest number of Red Hat certifications in
the hosting industry. Fanatical Support. Click to learn more
http://sel.as-us.falkag.net/sel?cmd=lnk&kid7521&bid$8729&dat1642
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
