[jboss-jira] [JBoss JIRA] Commented: (JBMETA-60) Do not create javadoc artifacts with the jboss-metadata release

[Paul Gier (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBMETA-60?page=comments#action_12417767 ] 
            
Paul Gier commented on JBMETA-60:
---------------------------------

I agree, since the source is already available, the javadocs should be easy to generate when needed.
The maven release plugin calls a profile in the super parent (http://maven.apache.org/guides/introduction/introduction-to-the-pom.html#Super_POM) called "release-profile".  This profile is what causes the javadocs to be generated during a release.

There is a parameter in the release plugin to not use this profile called useReleaseProfile, and that parameter is set in the jboss-parent pom.  So as long as the project uses the jboss-parent as it's parent I don't think it will generate the javadocs during a release.

> Do not create javadoc artifacts with the jboss-metadata release
> ---------------------------------------------------------------
>
>                 Key: JBMETA-60
>                 URL: http://jira.jboss.com/jira/browse/JBMETA-60
>             Project: JBoss Metadata
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Dimitris Andreadis
>         Assigned To: Paul Gier
>             Fix For: 1.0.0.CR1
>
>
> I don't think we need javadoc artifacts with jboss-metadata releases (or with other jboss project, as a matter of fact).
> We have the -sources.jar and the javadoc artifacts are just bloat for the repositories, check-in/check-out times.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira