Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@openjpa.apache.org
Message-ID: <257388.331371281709395968.JavaMail.jira@thor>
Date: Fri, 13 Aug 2010 10:23:15 -0400 (EDT)
From: "Donald Woods (JIRA)" <jira@apache.org>
To: dev@openjpa.apache.org
Subject: [jira] Resolved: (OPENJPA-1712) Upgrade builds to use Apache hosted
 Nexus repo
In-Reply-To: <20870886.132451277900570339.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Donald Woods resolved OPENJPA-1712.
-----------------------------------

    Resolution: Fixed

Believe everything it setup now.
Will update the release process on the wiki as I perform the 2.0.1 release and check-in any required updates against this JIRA if needed.

> Upgrade builds to use Apache hosted Nexus repo
> ----------------------------------------------
>
>                 Key: OPENJPA-1712
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-1712
>             Project: OpenJPA
>          Issue Type: Improvement
>          Components: build / infrastructure
>            Reporter: Donald Woods
>            Assignee: Donald Woods
>             Fix For: 1.3.0, 2.0.1, 2.1.0
>
>         Attachments: OPENJPA-1712-13x.diff, OPENJPA-1712-20x.diff, OPENJPA-1712-trunk-tests.diff
>
>
> Now that INFRA-2841 is complete, we can start migrating over to the new Apache hosted Nexus repo instance, instead of continuing to use the old SCP to people.a.o method.  Infra has asked projects to start migrating, with the goal to eventually force everyone over, as Nexus uses the LDAP ACLs and can check for signatures before allowing artifacts to be released.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.