Hmmm... still no luck. I tried with a 1.6 jdk on both mac and windows
and same result. I am getting odd behaviour. It seems that javadocs are
only generated for the build and demo modules:
./build/dummy/jaxb/target/site/apidocs
./build/maven/jar-collector/target/site/apidocs
./build/maven/javado
Hello Justin
Justin Deoliveira a écrit :
> I have been working my way through the release and all is going
> relatively well. I hit a snitch when trying to generate javadocs.
> Nothing seems to generate. I tried grepping for errors in the javadoc
> logs but to no avail. I thought it might be a
Hi all,
I have been working my way through the release and all is going
relatively well. I hit a snitch when trying to generate javadocs.
Nothing seems to generate. I tried grepping for errors in the javadoc
logs but to no avail. I thought it might be a mac issue but i also tried
on windows an
Justin Deoliveira ha scritto:
> H,
>
> I may have spoke too soon. I have the geoapi link working properly but i
> noticed alot of classes dont show up in the docs. From what I can tell
> none of the plugins or extensions are getting javadoc'd.
>
Can you try to modify the main pom enabling ja
H,
I may have spoke too soon. I have the geoapi link working properly but i
noticed alot of classes dont show up in the docs. From what I can tell
none of the plugins or extensions are getting javadoc'd.
-Justin
Justin Deoliveira wrote:
> Alright I think i have it,
>
> We need to use the gt
Alright I think i have it,
We need to use the gt2-javadoc from trunk which uses the latest geoapi
links. I think if i change them to the 2.0 javadoc, rebuild the plugin,
then generate javadocs again we should be ok.
Might be nice to backport the javadoc plugin to 2.2.x.
I updated the javadoc art
Hmm, I thought this was fixed, apparently not, I will have to look into
this.
-Justin
Adrian Custer wrote:
> Hey Justin,
>
> Congrats on getting this far.
>
> Good news is the jmappane works as well as can be expected.
>
> Bad news is javadocs still point to geoapi 2.1 and not geoapi 2.0.
>
Hey Justin,
Congrats on getting this far.
Good news is the jmappane works as well as can be expected.
Bad news is javadocs still point to geoapi 2.1 and not geoapi 2.0.
--adrian
On Fri, 2006-08-11 at 08:45 -0700, Justin Deoliveira wrote:
> Hi all,
>
> I have successfully built all the rele
Hi all,
I have successfully built all the release artifacts. The jars are posted
in the repository. I am uploading to sf now. I figure I will wait until
Monday morning before making the official announcement. In the meantime
I am switching geoserver over to official 2.2.0 and going to run cite
tes
