[jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-1864) Release source and javadoc artifacts to Maven repositories

[Andrew Lee Rubinger (JIRA)]

    [ https://jira.jboss.org/jira/browse/EJBTHREE-1864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12475008#action_12475008 ] 

Andrew Lee Rubinger commented on EJBTHREE-1864:
-----------------------------------------------

We've got JavaDoc and Source attachments for the EJB3 releases; everything is under the org.jboss.ejb3 groupId namespace. For example: 

http://repository.jboss.org/maven2/org/jboss/ejb3/jboss-ejb3-ext-api/1.0.0/

> Release source and javadoc artifacts to Maven repositories
> ----------------------------------------------------------
>
>                 Key: EJBTHREE-1864
>                 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1864
>             Project: EJB 3.0
>          Issue Type: Release
>          Components: build
>    Affects Versions: trunk
>            Reporter: Aleksander Adamowski
>            Assignee: Andrew Lee Rubinger
>
> Currently, most Maven 2 artifacts are released without accompanying source and javadoc artifacts, e.g.:
> http://repository.jboss.com/maven2/jboss/jboss-annotations-ejb3/4.2.3.GA/
> It would make development work much simpler if the release deployment procedure included source and javadoc.
> With Maven 2, this is trivial:
> http://maven.apache.org/plugin-developers/cookbook/attach-source-javadoc-artifacts.html

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