Richard Gould a écrit :
hmm - that worked. I get the correct output.
Cool!
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?
This is very easy to adjust. We just need to agree on
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!)
Tryi
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 insta
Yeah, I get the same exception on trunk. Am I missing something?
Martin Desruisseaux wrote:
Martin Desruisseaux a écrit :
Do you get the same exception when running "mvn install" and "mvn
org.geotools:gt2-javadoc:javadoc" both on trunk?
(I mean on a fresh trunk checkout - I fixed a bug simi
Added a wiki page about generating javadoc:
http://docs.codehaus.org/display/GEOT/2.6+Generating+Javadoc
I noticed that a new maven-javadoc-plugin were released recently. I tried it, but some Maven plugins
still have a number of bugs. For example:
* upgrating maven-resources-plugin from 2.1
Martin Desruisseaux a écrit :
Do you get the same exception when running "mvn install" and "mvn
org.geotools:gt2-javadoc:javadoc" both on trunk?
(I mean on a fresh trunk checkout - I fixed a bug similar to this one a few
days ago).
Martin.
---
Richard Gould a écrit :
I tried a mvn install on trunk and then went to my 2.2-RC3 checkout.
Executing mvn org.geotools:gt2-javadoc:javadoc yields this exception:
[...snip...]
[DEBUG] Trace java.lang.NullPointerException
Cory Horner a écrit :
At a glance it looked like:
r19455 | rgould | 2006-05-11 13:57:44 -0700 (Thu, 11 May 2006) | 1 line
[maven-release-plugin] prepare release 2.2-RC3
was responsible... but upon review, perhaps it was:
r19418 | rgould | 2006-05-09 17:18:21 -0700 (Tue, 09 May 2006) | 1 line
[
Martin Desruisseaux wrote:
Richard Gould a écrit :
The poms are changed whenever maven release:prepare is executed, but
they do not change the formatting. I had a look at the diff for the
commit and it just changes version numbers.
Just checked. It is true that the poms are almost the same
Martin Desruisseaux wrote:
Richard Gould a écrit :
The poms are changed whenever maven release:prepare is executed, but
they do not change the formatting. I had a look at the diff for the
commit and it just changes version numbers.
Just checked. It is true that the poms are almost the same be
Richard Gould a écrit :
The poms are changed whenever maven release:prepare is executed, but
they do not change the formatting. I had a look at the diff for the
commit and it just changes version numbers.
Just checked. It is true that the poms are almost the same between 2.2.x and 2.2-RC3. But
Martin Desruisseaux wrote:
>> Does this create the javadoc zip archive that was normally generated
>> during maven 1 createRelease?
>
>
> Not yet, but it would be trivial to add (the plugin just execute an Ant
> build file, so it is just a matter of adding a few lines to this Ant
> build file - I
Jody Garnett a écrit :
If possible I would like to get a smaller javadoc of "module/*" - aka
just the geotools library.
Commited on trunk as of revision 19516. Our custom javadoc plugin now have 2
goals:
mvn org.geotools:gt2-javadoc:javadoc - Generates javadoc for the whole
Geotools
Just realized that
mvn org.geotools:gt2-javadoc:javadoc
is implemented on trunk only. I tried to port it on 2.2 branch one or two week ago, but failed
because the pom.xml files in the 2.2 branch are very different from the pom.xml files in the trunk.
Was the pom.xml files overwritten by Ma
Martin Desruisseaux wrote:
I have documented the progress I have made so far:
http://docs.codehaus.org/display/GEOT/How+to+cut+a+release
It's right at the top in the big blue box.
Can we delete the Maven 1 specific instructions in the above page, and
reformat the blue box as top-level text? I
Richard Gould wrote:
I have successfully built all of the release jars for 2.2-RC3 and they
have been uploaded to maven.geotools.fr.
Wow congrats! Thanks Richard this is very good news.
The only part that remains is to have the release process construct
the standard binary/src/javadoc archives
Richard Gould a écrit :
For now, cross-module javadoc is generated using the following custom
plugin:
mvn org.geotools:gt2-javadoc:javadoc
Does this create the javadoc zip archive that was normally generated
during maven 1 createRelease?
Not yet, but it would be trivial to add (the plug
Martin Desruisseaux wrote:
Richard Gould a écrit :
I have successfully built all of the release jars for 2.2-RC3 and they
have been uploaded to maven.geotools.fr. The only part that remains is
to have the release process construct the standard binary/src/javadoc
archives that we use for norma
Hmm actually I think I just succesfully built a source release. I was
just confused and trying something silly before. I have go to now, so I
will check it out tomorrow, and try your javadoc plug-in. Then
everything should be done.
Cheers
Richard
Richard Gould wrote:
Martin Desruisseaux wr
I have successfully built all of the release jars for 2.2-RC3 and they
have been uploaded to maven.geotools.fr. The only part that remains is
to have the release process construct the standard binary/src/javadoc
archives that we use for normal distribution.
I have documented the progress I hav
Richard Gould a écrit :
I have successfully built all of the release jars for 2.2-RC3 and they
have been uploaded to maven.geotools.fr. The only part that remains is
to have the release process construct the standard binary/src/javadoc
archives that we use for normal distribution.
Thanks a lo
Jody Garnett wrote:
Richard Gould wrote:
The only part that remains is to have the release process construct
the standard binary/src/javadoc archives that we use for normal
distribution.
Um what does it build right now? Is it something we can distribute?
It builds a bunch of jars and upload
22 matches
Mail list logo
