[jboss-jira] [JBoss JIRA] Resolved: (JBMETA-280) Add jboss release repo to distributionManagement in jboss-metadata-ejb pom

[jaikiran pai (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBMETA-280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

jaikiran pai resolved JBMETA-280.
---------------------------------

    Resolution: Done


> Add jboss release repo to distributionManagement in jboss-metadata-ejb pom
> --------------------------------------------------------------------------
>
>                 Key: JBMETA-280
>                 URL: https://jira.jboss.org/jira/browse/JBMETA-280
>             Project: JBoss Metadata
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: ejb
>    Affects Versions:  jboss-metadata-ejb-2.0.0-alpha-11
>            Reporter: jaikiran pai
>            Assignee: jaikiran pai
>             Fix For: jboss-metadata-ejb-2.0.0-alpha-12
>
>
> As per the new release guidelines http://community.jboss.org/wiki/MavenDeployingaRelease
> <quote>
> In order to deploy to the Maven releases repository, your project POM (or parent POM) will need to be configured with the appropriate distributionManagement information.  The best practice is to inherit this information from the JBoss parent pom (version 5 or later).
>   <parent>
>     <groupId>org.jboss</groupId>
>     <artifactId>jboss-parent</artifactId>
>     <version>5</version>
>   </parent>
> If you are not able to inherit from the jboss parent pom, you will need the following configuration in your POM.
>   <distributionManagement>
>     <repository>
>       <id>jboss-releases-repository</id>
>       <name>JBoss Releases Repository</name>
>       <url>https://repository.jboss.org/nexus/service/local/staging/deploy/maven2/</url>
>     </repository>
>     ...
>   </distributionManagement>
> </quote>
> We have had some issues using jboss-parent 5, so instead of using that version, add the distribution management section to the pom.

-- 
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