[
https://issues.apache.org/jira/browse/COMMONSSITE-60?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12887073#action_12887073
]
Sebb commented on COMMONSSITE-60:
---------------------------------
The same reasoning applies to the distributionManagement entries in the "ci"
profile.
So that profile should be restored too...
> Profile "rc" lost ability to release to /www/people.apache.org/builds/commons
> -----------------------------------------------------------------------------
>
> 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.
-
You can reply to this email to add a comment to the issue online.
