You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by "Brehm, Robert P" <Ro...@xerox.com> on 2006/11/03 01:15:14 UTC
Javadoc plugin issue: 2nd try
Hi,
I am using Maven 2 and here is my dilemma:
We have internal projects some of which are compiled in Java 1.4 and
some in Java 1.5.
My JAVA_HOME is set to .. j2sdk1.4.2_04
In my POM I have included
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<configuration>
<fork>true</fork>
<source>1.5</source>
<target>1.5</target>
<compilerVersion>1.5</compilerVersion>
<executable>/apps/java/jdk1.5.0_07/bin/javac</executable>
</configuration>
</plugin>
</plugins>
</build
So the project compiles in Java 1.5. However, when I do:
<reporting>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-javadoc-plugin</artifactId>
<configuration>
<minmemory>128m</minmemory>
<maxmemory>512</maxmemory>
</configuration>
</plugin>
</plugins>
</reporting>
I get compilation errors and
Command line was:/apps/java/j2sdk1.4.2_04/jre/../bin/javadoc
-J-DproxyHost=13.62.6.90 -J-DproxyPort=8080 -J-Xmx512m -J-Xms128m
@options @packages
So it used the JAVA_HOME for the javadoc bin file.
I tried adding this to the javadoc configuration:
<sourcepath>/apps/java/jdk1.5.0_07/bin/javadoc</sourcepath> and this
time javadoc did nothing.
So it looks like the javadoc plugin is not looking at the build plugin
and the source path has no effect. Is there any way to configure the
javadoc plugin to use the specified build plugin. If no response then
perhaps I need to submit a bug.
Regards,
Bob
--------------------------------------------------------------------
Robert P. Brehm
Software Engineer, Manufacturing Technology Development
Xerox Office Group, Wilsonville, OR, USA
503-685-2329
Re: Javadoc plugin issue: 2nd try
Posted by Wayne Fay <wa...@gmail.com>.
I got interested in this issue and wrote some code to add this functionality to maven-javadoc-plugin...
Its not ideal for various reasons -- SystemUtils doesn't know how parse the Javadoc version, so you need to pass it in as a <configuration> element -- but its a good first step, and it works fine in my limited testing with JAVA_HOME=1.4 and configuration=1.5.
I made an issue in JIRA for this [1] and attached the patch, so if you want to start using this now, go grab the source from SVN and apply my patch to AbstractJavadocMojo.java.
[1] http://jira.codehaus.org/browse/MJAVADOC-98
Wayne
On 11/2/06, Wayne Fay <wa...@gmail.com> wrote:
> Sorry about that, here's the M2 Javadoc plugin link:
> http://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html
>
> Still don't see a way to specify the Javadoc binary path/version. ;-)
>
> Wayne
>
> On 11/2/06, Wayne Fay <wa...@gmail.com> wrote:
> > Any reason why you can't set JAVA_HOME to your 1.5 installation, and
> > then use the 1.4 compiler for the 1.4 "stuff" since it seems like you
> > need to use the 1.5 Javadoc?
> >
> > Otherwise I suppose filing an RFE against this plugin is a reasonable
> > strategy. I checked the properties and don't see anything that allows
> > you to specify what Javadoc path (binary) you want to use...
> >
> > http://maven.apache.org/maven-1.x/plugins/javadoc/properties.html
> >
> > Wayne
> >
> > On 11/2/06, Brehm, Robert P <Ro...@xerox.com> wrote:
> > > Hi,
> > >
> > >
> > >
> > > I am using Maven 2 and here is my dilemma:
> > >
> > >
> > >
> > > We have internal projects some of which are compiled in Java 1.4 and
> > > some in Java 1.5.
> > >
> > >
> > >
> > > My JAVA_HOME is set to .. j2sdk1.4.2_04
> > >
> > >
> > >
> > > In my POM I have included
> > >
> > >
> > >
> > > <build>
> > >
> > > <plugins>
> > >
> > > <plugin>
> > >
> > > <groupId>org.apache.maven.plugins</groupId>
> > >
> > > <artifactId>maven-compiler-plugin</artifactId>
> > >
> > > <configuration>
> > >
> > > <fork>true</fork>
> > >
> > > <source>1.5</source>
> > >
> > > <target>1.5</target>
> > >
> > > <compilerVersion>1.5</compilerVersion>
> > >
> > > <executable>/apps/java/jdk1.5.0_07/bin/javac</executable>
> > >
> > > </configuration>
> > >
> > > </plugin>
> > >
> > > </plugins>
> > >
> > > </build
> > >
> > >
> > >
> > > So the project compiles in Java 1.5. However, when I do:
> > >
> > >
> > >
> > > <reporting>
> > >
> > > <plugins>
> > >
> > > <plugin>
> > >
> > > <groupId>org.apache.maven.plugins</groupId>
> > >
> > > <artifactId>maven-javadoc-plugin</artifactId>
> > >
> > > <configuration>
> > >
> > > <minmemory>128m</minmemory>
> > >
> > > <maxmemory>512</maxmemory>
> > >
> > > </configuration>
> > >
> > > </plugin>
> > >
> > > </plugins>
> > >
> > > </reporting>
> > >
> > >
> > >
> > > I get compilation errors and
> > >
> > >
> > >
> > > Command line was:/apps/java/j2sdk1.4.2_04/jre/../bin/javadoc
> > >
> > > -J-DproxyHost=13.62.6.90 -J-DproxyPort=8080 -J-Xmx512m -J-Xms128m
> > > @options @packages
> > >
> > >
> > >
> > > So it used the JAVA_HOME for the javadoc bin file.
> > >
> > >
> > >
> > > I tried adding this to the javadoc configuration:
> > >
> > > <sourcepath>/apps/java/jdk1.5.0_07/bin/javadoc</sourcepath> and this
> > > time javadoc did nothing.
> > >
> > >
> > >
> > > So it looks like the javadoc plugin is not looking at the build plugin
> > > and the source path has no effect. Is there any way to configure the
> > > javadoc plugin to use the specified build plugin. If no response then
> > > perhaps I need to submit a bug.
> > >
> > >
> > >
> > > Regards,
> > >
> > >
> > >
> > > Bob
> > >
> > >
> > >
> > > --------------------------------------------------------------------
> > >
> > > Robert P. Brehm
> > >
> > > Software Engineer, Manufacturing Technology Development
> > >
> > > Xerox Office Group, Wilsonville, OR, USA
> > >
> > > 503-685-2329
> > >
> > >
> > >
> > >
> > >
> >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Javadoc plugin issue: 2nd try
Posted by Wayne Fay <wa...@gmail.com>.
Sorry about that, here's the M2 Javadoc plugin link:
http://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html
Still don't see a way to specify the Javadoc binary path/version. ;-)
Wayne
On 11/2/06, Wayne Fay <wa...@gmail.com> wrote:
> Any reason why you can't set JAVA_HOME to your 1.5 installation, and
> then use the 1.4 compiler for the 1.4 "stuff" since it seems like you
> need to use the 1.5 Javadoc?
>
> Otherwise I suppose filing an RFE against this plugin is a reasonable
> strategy. I checked the properties and don't see anything that allows
> you to specify what Javadoc path (binary) you want to use...
>
> http://maven.apache.org/maven-1.x/plugins/javadoc/properties.html
>
> Wayne
>
> On 11/2/06, Brehm, Robert P <Ro...@xerox.com> wrote:
> > Hi,
> >
> >
> >
> > I am using Maven 2 and here is my dilemma:
> >
> >
> >
> > We have internal projects some of which are compiled in Java 1.4 and
> > some in Java 1.5.
> >
> >
> >
> > My JAVA_HOME is set to .. j2sdk1.4.2_04
> >
> >
> >
> > In my POM I have included
> >
> >
> >
> > <build>
> >
> > <plugins>
> >
> > <plugin>
> >
> > <groupId>org.apache.maven.plugins</groupId>
> >
> > <artifactId>maven-compiler-plugin</artifactId>
> >
> > <configuration>
> >
> > <fork>true</fork>
> >
> > <source>1.5</source>
> >
> > <target>1.5</target>
> >
> > <compilerVersion>1.5</compilerVersion>
> >
> > <executable>/apps/java/jdk1.5.0_07/bin/javac</executable>
> >
> > </configuration>
> >
> > </plugin>
> >
> > </plugins>
> >
> > </build
> >
> >
> >
> > So the project compiles in Java 1.5. However, when I do:
> >
> >
> >
> > <reporting>
> >
> > <plugins>
> >
> > <plugin>
> >
> > <groupId>org.apache.maven.plugins</groupId>
> >
> > <artifactId>maven-javadoc-plugin</artifactId>
> >
> > <configuration>
> >
> > <minmemory>128m</minmemory>
> >
> > <maxmemory>512</maxmemory>
> >
> > </configuration>
> >
> > </plugin>
> >
> > </plugins>
> >
> > </reporting>
> >
> >
> >
> > I get compilation errors and
> >
> >
> >
> > Command line was:/apps/java/j2sdk1.4.2_04/jre/../bin/javadoc
> >
> > -J-DproxyHost=13.62.6.90 -J-DproxyPort=8080 -J-Xmx512m -J-Xms128m
> > @options @packages
> >
> >
> >
> > So it used the JAVA_HOME for the javadoc bin file.
> >
> >
> >
> > I tried adding this to the javadoc configuration:
> >
> > <sourcepath>/apps/java/jdk1.5.0_07/bin/javadoc</sourcepath> and this
> > time javadoc did nothing.
> >
> >
> >
> > So it looks like the javadoc plugin is not looking at the build plugin
> > and the source path has no effect. Is there any way to configure the
> > javadoc plugin to use the specified build plugin. If no response then
> > perhaps I need to submit a bug.
> >
> >
> >
> > Regards,
> >
> >
> >
> > Bob
> >
> >
> >
> > --------------------------------------------------------------------
> >
> > Robert P. Brehm
> >
> > Software Engineer, Manufacturing Technology Development
> >
> > Xerox Office Group, Wilsonville, OR, USA
> >
> > 503-685-2329
> >
> >
> >
> >
> >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Javadoc plugin issue: 2nd try
Posted by Wayne Fay <wa...@gmail.com>.
Any reason why you can't set JAVA_HOME to your 1.5 installation, and
then use the 1.4 compiler for the 1.4 "stuff" since it seems like you
need to use the 1.5 Javadoc?
Otherwise I suppose filing an RFE against this plugin is a reasonable
strategy. I checked the properties and don't see anything that allows
you to specify what Javadoc path (binary) you want to use...
http://maven.apache.org/maven-1.x/plugins/javadoc/properties.html
Wayne
On 11/2/06, Brehm, Robert P <Ro...@xerox.com> wrote:
> Hi,
>
>
>
> I am using Maven 2 and here is my dilemma:
>
>
>
> We have internal projects some of which are compiled in Java 1.4 and
> some in Java 1.5.
>
>
>
> My JAVA_HOME is set to .. j2sdk1.4.2_04
>
>
>
> In my POM I have included
>
>
>
> <build>
>
> <plugins>
>
> <plugin>
>
> <groupId>org.apache.maven.plugins</groupId>
>
> <artifactId>maven-compiler-plugin</artifactId>
>
> <configuration>
>
> <fork>true</fork>
>
> <source>1.5</source>
>
> <target>1.5</target>
>
> <compilerVersion>1.5</compilerVersion>
>
> <executable>/apps/java/jdk1.5.0_07/bin/javac</executable>
>
> </configuration>
>
> </plugin>
>
> </plugins>
>
> </build
>
>
>
> So the project compiles in Java 1.5. However, when I do:
>
>
>
> <reporting>
>
> <plugins>
>
> <plugin>
>
> <groupId>org.apache.maven.plugins</groupId>
>
> <artifactId>maven-javadoc-plugin</artifactId>
>
> <configuration>
>
> <minmemory>128m</minmemory>
>
> <maxmemory>512</maxmemory>
>
> </configuration>
>
> </plugin>
>
> </plugins>
>
> </reporting>
>
>
>
> I get compilation errors and
>
>
>
> Command line was:/apps/java/j2sdk1.4.2_04/jre/../bin/javadoc
>
> -J-DproxyHost=13.62.6.90 -J-DproxyPort=8080 -J-Xmx512m -J-Xms128m
> @options @packages
>
>
>
> So it used the JAVA_HOME for the javadoc bin file.
>
>
>
> I tried adding this to the javadoc configuration:
>
> <sourcepath>/apps/java/jdk1.5.0_07/bin/javadoc</sourcepath> and this
> time javadoc did nothing.
>
>
>
> So it looks like the javadoc plugin is not looking at the build plugin
> and the source path has no effect. Is there any way to configure the
> javadoc plugin to use the specified build plugin. If no response then
> perhaps I need to submit a bug.
>
>
>
> Regards,
>
>
>
> Bob
>
>
>
> --------------------------------------------------------------------
>
> Robert P. Brehm
>
> Software Engineer, Manufacturing Technology Development
>
> Xerox Office Group, Wilsonville, OR, USA
>
> 503-685-2329
>
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org