commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sebb (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (COMMONSSITE-60) Profile "rc" lost ability to release to /www/people.apache.org/builds/commons; "ci" dropped unnecessarily
Date Sat, 05 Feb 2011 18:23:30 GMT

     [ https://issues.apache.org/jira/browse/COMMONSSITE-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Sebb resolved COMMONSSITE-60.
-----------------------------

    Resolution: Fixed

> Profile "rc" lost ability to release to /www/people.apache.org/builds/commons; "ci" dropped
unnecessarily
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: COMMONSSITE-60
>                 URL: https://issues.apache.org/jira/browse/COMMONSSITE-60
>             Project: Commons All
>          Issue Type: Bug
>          Components: Commons Parent Pom
>    Affects Versions: 16
>            Reporter: Sebb
>             Fix For: 17
>
>
> As part of the changes to use Nexus for release management in version 16, all the repository
entries were removed.
> This was too drastic.
> The "rc" profile should have retained the following distributionManagement entry:
> {code}
> <repository>
>   <id>apache.snapshots</id>
>   <name>Apache Development Snapshot Repository</name>
>   <url>${commons.deployment.protocol}://people.apache.org/www/people.apache.org/builds/commons/${commons.componentid}/${commons.release.version}/${commons.rc.version}/staged</url>
> </repository>
> {code}
> Unlike the other distributionManagement entries that were removed, this is a local snapshot
repository which is not synchronised with the Maven repos.
> So it is quite safe to leave the entry in the parent pom.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message