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 <[EMAIL PROTECTED]> 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to