[
https://issues.apache.org/jira/browse/JCRSITE-11?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting resolved JCRSITE-11.
----------------------------------
Resolution: Fixed
Fix Version/s: parent 3
Assignee: Jukka Zitting
Updated the org.apache.jackrabbit:parent POM in revision 747151.
> Prevent accidental release deployments
> --------------------------------------
>
> Key: JCRSITE-11
> URL: https://issues.apache.org/jira/browse/JCRSITE-11
> Project: Jackrabbit Site
> Issue Type: Improvement
> Components: parent
> Reporter: Jukka Zitting
> Assignee: Jukka Zitting
> Priority: Minor
> Fix For: parent 3
>
>
> The org.apache:apache:4 parent POM we use configures the m2-ibiblio-rsync
> repository on people.apache.org as the default deployment target. This is
> troublesome as an accidental "mvn deploy" on a non-snapshot source tree (a
> source release, a checked out tag, etc.) can end up deploying the build all
> the way to the central Maven repository with no review.
> The Maven people are currently setting up a new repository.apache.org
> repository manager that nicely supports staged deployment. We should override
> the default deployment target with that repository or just disable the
> default deployment repository settings. Alternatively we should switch to a
> potential newer version of the Apache parent POM that has this issue fixed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
