You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Marshall Schor (JIRA)" <de...@uima.apache.org> on 2010/10/29 13:28:20 UTC

[jira] Created: (UIMA-1919) change apache-release build to not do individual project Javadocs for -distr projects

change apache-release build to not do individual project Javadocs for -distr projects
-------------------------------------------------------------------------------------

                 Key: UIMA-1919
                 URL: https://issues.apache.org/jira/browse/UIMA-1919
             Project: UIMA
          Issue Type: Improvement
          Components: Build, Packaging and Test
            Reporter: Marshall Schor
            Assignee: Marshall Schor
            Priority: Minor
             Fix For: build-parent-pom-1


The -distr projects already build Javadocs for the aggregate of the individual modules, but with a filtering of the classes, to show the public APIs.  

The default apache-release build (done when the apache-release profile is activated, which it is by default during during release, or if you specify -Papache-release on the mvn command line) builds additionally, Javadocs for everything.   These Javadocs are full of warnings because we haven't been very careful in writing the Javadocs.

Building individual Javadocs for every Java module makes the build much slower.  These Javadocs are not included in the distribution, but would be available (if generated) in the Maven repository.  However, the source code is also being generated for each module during release, and that is also available in the with the main artifact in the Maven repository (when finally released).  That has been sufficient for our previous releases.

For these reasons, override the apache-release profile for the -distr aggregate projects to remove the Javadoc builds for the -distr projects.



-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Closed: (UIMA-1919) change apache-release build to not do individual project Javadocs for -distr projects

Posted by "Marshall Schor (JIRA)" <de...@uima.apache.org>.
     [ https://issues.apache.org/jira/browse/UIMA-1919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marshall Schor closed UIMA-1919.
--------------------------------

    Resolution: Fixed

> change apache-release build to not do individual project Javadocs for -distr projects
> -------------------------------------------------------------------------------------
>
>                 Key: UIMA-1919
>                 URL: https://issues.apache.org/jira/browse/UIMA-1919
>             Project: UIMA
>          Issue Type: Improvement
>          Components: Build, Packaging and Test
>            Reporter: Marshall Schor
>            Assignee: Marshall Schor
>            Priority: Minor
>             Fix For: build-parent-pom-1
>
>
> The -distr projects already build Javadocs for the aggregate of the individual modules, but with a filtering of the classes, to show the public APIs.  
> The default apache-release build (done when the apache-release profile is activated, which it is by default during during release, or if you specify -Papache-release on the mvn command line) builds additionally, Javadocs for everything.   These Javadocs are full of warnings because we haven't been very careful in writing the Javadocs.
> Building individual Javadocs for every Java module makes the build much slower.  These Javadocs are not included in the distribution, but would be available (if generated) in the Maven repository.  However, the source code is also being generated for each module during release, and that is also available in the with the main artifact in the Maven repository (when finally released).  That has been sufficient for our previous releases.
> For these reasons, override the apache-release profile for the -distr aggregate projects to remove the Javadoc builds for the -distr projects.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.