jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCRSITE-11) Prevent accidental release deployments
Date Mon, 23 Feb 2009 21:08:02 GMT

    [ https://issues.apache.org/jira/browse/JCRSITE-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12676064#action_12676064
] 

Jukka Zitting commented on JCRSITE-11:
--------------------------------------

The jackrabbit-parent (in jackrabbit/trunk/jackrabbit-parent) POM now contains the following
settings based on the new repository.apache.org server:

{code:xml}
  <distributionManagement>
    <repository>
      <id>apache.staging</id>
      <name>Apache Release Staging Repository</name>
      <url>https://repository.apache.org/service/local/staging/deploy/maven2</url>
    </repository>
    <snapshotRepository>
      <id>apache.snapshots</id>
      <name>Apache Development Snapshot Repository</name>
      <url>https://repository.apache.org/content/repositories/snapshots</url>
    </snapshotRepository>
  </distributionManagement>
{code}

The snapshot repository settings seem to be working fine, so I'll be moving this to the top
level parent POM (in jackrabbit/parent/trunk) where it'll affect all Jackrabbit subprojects.

I haven't yet tried the staging repository (planning to do that with one of the upcoming JCR
Commons releases), but even just having this setting here (regardless of whether we use yet)
will override the potentially troublesome deployment target in the org.apache:apache parent
POM.

The username and password needed for deploying snapshots and staging releases was sent to
private@jackrabbit.apache.org. I'll also archive that information in the private svn area
of the Jackrabbit PMC.

A potential issue was raised due to the "apache.snapshots" id being the same as used for the
other snapshot repository in the org.apache:apache parent POM. This might be a bit troublesome
for people (and CI builds) that deploy snapshots of multiple Apache projects. To avoid such
problems I'll change the ids to "apache.snapshot.repository" and "apache.staging.repository".

> 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
>            Priority: Minor
>
> 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.


Mime
View raw message