Mailing-List: contact users-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Maven Users List" <users@maven.apache.org>
MIME-Version: 1.0
Message-ID: <3f598021-7427-489b-8884-e9f385429aa6@default>
Date: Wed, 13 Jan 2016 21:36:06 -0800 (PST)
From: Robert Patrick <robert.patrick@oracle.com>
Sender: Robert Patrick <robert.patrick@oracle.com>
To: Maven Users List <users@maven.apache.org>
Subject: RE: Maven javadoc plugin's aggregate-jar goal, multi-module project,
 and code generation
References: <2eb29082-92c9-4f13-a06f-a1803d33d331@default>
 <OFB20F4AB5.71953075-ON65257F3A.001BACD4-65257F3A.001BE4B4@tcs.com>
In-Reply-To: 
 <OFB20F4AB5.71953075-ON65257F3A.001BACD4-65257F3A.001BE4B4@tcs.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable

Yeah, but that won't help since the code is not all in a single module.  By=
 default, the aggregate-jar goal docs claim it is bound to the package phas=
e and all of my source in the submodules are generated in the generate-sour=
ces phase.=20

Now that I analyze the output more carefully, it appears that the aggregate=
-jar goal is running the aggregate goal during the generate-sources phase a=
nd somehow causing the builds of the modules in parallel (even though I did=
n't tell it to do so).  The 58 warnings are all from mod4, mod5, and mod6 (=
the last 3 submodules in the modules list)--even though mod1, mod2, and mod=
3 also use the exact same code generation and referencing techniques.  So t=
his makes me think that there is a bug in the parallel execution logic.

-----Original Message-----
From: Sarath Shasikumar [mailto:sarath.shasikumar@tcs.com]=20
Sent: Wednesday, January 13, 2016 11:05 PM
To: Maven Users List
Cc: Robert Patrick
Subject: Re: Maven javadoc plugin's aggregate-jar goal, multi-module projec=
t, and code generation

To execute plugin during certain phase, add <phase> to <execution>. Plugin =
should be fired:
<executions>
   <execution>
      <id>attach-javadocs</id>
      <phase>install</phase>    <------ HERE
      <goals>
         <goal>aggregate-jar</goal>
       </goals>
    </execution>
 </executions>

Regards
Sarath Shasikumar
Systems Engineer
Tata Consultancy Services
Cell:- +91 97 46 136153
Mailto: sarath.shasikumar@tcs.com
Website: http://www.tcs.com
____________________________________________
Experience certainty.   IT Services
                        Business Solutions
                        Consulting
____________________________________________


From:   Robert Patrick <robert.patrick@oracle.com>
To:     users@maven.apache.org
Date:   01/14/2016 10:24 AM
Subject:        Maven javadoc plugin's aggregate-jar goal, multi-module=20
project, and code generation


I am beating my head against the wall on this and surely I am just being st=
upid so hopefully someone will take pity on me and point me in the right di=
rection.

=20

I am trying to add Javadoc generation into my normal build process for my=
=20
multi-module project.  It all works fine if I run "mvn install" on the=20
project followed by "mvn javadoc:aggregate-jar" but I would really like to=
=20
be able to generate the javadocs jar as part of the normal build so that=20
it:

=20

-        Gets built by default (without having to remember to run the=20
extra command)

-        Sets attached to the build so that the install plugin installs it

=20

I put something like the following in the top-level POM (the module names=
=20
have been changed to protect the innocent.):

=20

<modules>
    <module>mod1</module>
    <module>mod2</module>
    <module>mod3</module>
    <module>mod4</module>
    <module>mod5</module>
    <module>mod6</module>
</modules>
<build>
    <plugins>
        <plugin>
            <groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-javadoc-plugin</artifactId>
            <executions>
                <execution>
                    <id>generate-javadoc</id>
                    <goals>
                        <goal>aggregate-jar</goal>
                    </goals>
                </execution>
            </executions>
        </plugin>
    </plugins>
</build>

=20

Unfortunately, this runs the aggregate-jar goal first, before building the=
=20
modules.  Since Java code in the modules reference classes generated by=20
the module build, the build generates tons of warnings from the Javadoc=20
plugin about not finding the generated classes (which makes sense since=20
they don't exist yet) like this:

=20

[WARNING] import com.mycompany.mod4.resources.MyResourceBundle;

[WARNING] ^

[WARNING]=20
C:\myproject\mod4\src\main\java\com\mycompany\mod4\MyApplication.java:24:=
=20
error: package com.mycompany.mod4.resources does not exist

=20

Is there really no way to do this with code generation?=20

=20

Thanks,

Robert

=20

=3D=3D=3D=3D=3D-----=3D=3D=3D=3D=3D-----=3D=3D=3D=3D=3D
Notice: The information contained in this e-mail
message and/or attachments to it may contain=20
confidential or privileged information. If you are=20
not the intended recipient, any dissemination, use,=20
review, distribution, printing or copying of the=20
information contained in this e-mail message=20
and/or attachments to it are strictly prohibited. If=20
you have received this communication in error,=20
please notify us by reply e-mail or telephone and=20
immediately and permanently delete the message=20
and any attachments. Thank you


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org