Installing only javadocs

[Christian Domsch <ma...@landrus.de>]

Hi,

I have a continuous integration setup where the build is setup in two 
steps. First all modules are built and deployed. After that a second 
build is triggered that takes those artifacts and builds installers from 
that.

Because of performance reasons and they are only needed for the 
installers, any javadoc jars are only being built in the second step. 
Now I want to install these jars into the local repo as well. A call to 
javadoc:jar only creates those jars, not copy them over to the local repo.

I do not want to run mvn install, as that would run the complete build 
again. Now, I looked at the documentation of maven-javadoc-plugin and 
the maven-install-plugin but I couldnt find a way to only install the 
javadocs. (something like mvn javadoc:jar javadoc:install, if such a 
goal would exist).

Is there a way to achieve that or am I on the wrong track?

Greetings,

Christian

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

Re: Installing only javadocs

[Christian Domsch <ma...@landrus.de>]

Hi Stephen,

that is actually the way it is setup. With one minor problem, the 
installers need the javadocs from the other modules as well. And we do 
not build them during the normal built because of performance reasons 
(it takes ~15mins to create them).

You are right, the installer modules could be even completly decoupled, 
what we have are submodules that are activated via a profile.

But to built the javadocs I have to go into the original modules again 
and create the javadocs. This so far is working. But in this setup, the 
installer modules have no access to the javadocs, since they onlide 
reside inside the target folders and not the local repository.

Maybe to illustrate:

Main module:
   root/module/A
              /B
              /C
              /D/D1
                /D2

Installer:
   root/installers/instA
                  /instB


What I currently run is mvn deployin the main build, with disabled 
javadoc generation.
For the installers, I runmvn javadoc:jarin the main module directory, 
and then mvn installin the installer directory. But again, javadoc:jar 
does not copy to local repo, so when the installers are run the 
(possibly) reference old javadocs that are still in the local repo, 
instead of using the just generated javadocs.

Hope this clarifies the problem

Thanks,
Christian

On 15.12.2014 15:47, Stephen Connolly wrote:
> Wrong track.
>
> On 15 December 2014 at 13:13, Christian Domsch <ma...@landrus.de> wrote:
>> Hi,
>>
>> I have a continuous integration setup where the build is setup in two
>> steps. First all modules are built and deployed. After that a second build
>> is triggered that takes those artifacts and builds installers from that.
>>
> You should have separate modules that transform the artifacts into
> installers for those artifacts.
>
> Those separate moduled can even be in a separate SCM root as you may
> release the first modules multiple times but only build installers from the
> last time.
>
>
>
>> Because of performance reasons and they are only needed for the
>> installers, any javadoc jars are only being built in the second step. Now I
>> want to install these jars into the local repo as well. A call to
>> javadoc:jar only creates those jars, not copy them over to the local repo.
>>
>> I do not want to run mvn install, as that would run the complete build
>> again. Now, I looked at the documentation of maven-javadoc-plugin and the
>> maven-install-plugin but I couldnt find a way to only install the javadocs.
>> (something like mvn javadoc:jar javadoc:install, if such a goal would
>> exist).
>>
>> Is there a way to achieve that or am I on the wrong track?
>>
>> Greetings,
>>
>> Christian
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>

Re: Installing only javadocs

[Stephen Connolly <st...@gmail.com>]

Wrong track.

On 15 December 2014 at 13:13, Christian Domsch <ma...@landrus.de> wrote:
>
> Hi,
>
> I have a continuous integration setup where the build is setup in two
> steps. First all modules are built and deployed. After that a second build
> is triggered that takes those artifacts and builds installers from that.
>

You should have separate modules that transform the artifacts into
installers for those artifacts.

Those separate moduled can even be in a separate SCM root as you may
release the first modules multiple times but only build installers from the
last time.



>
> Because of performance reasons and they are only needed for the
> installers, any javadoc jars are only being built in the second step. Now I
> want to install these jars into the local repo as well. A call to
> javadoc:jar only creates those jars, not copy them over to the local repo.
>
> I do not want to run mvn install, as that would run the complete build
> again. Now, I looked at the documentation of maven-javadoc-plugin and the
> maven-install-plugin but I couldnt find a way to only install the javadocs.
> (something like mvn javadoc:jar javadoc:install, if such a goal would
> exist).
>
> Is there a way to achieve that or am I on the wrong track?
>
> Greetings,
>
> Christian
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>