From easyant-commits-return-361-apmail-incubator-easyant-commits-archive=incubator.apache.org@incubator.apache.org Sun Jul 8 19:41:36 2012 Return-Path: X-Original-To: apmail-incubator-easyant-commits-archive@minotaur.apache.org Delivered-To: apmail-incubator-easyant-commits-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id F396BD95E for ; Sun, 8 Jul 2012 19:41:35 +0000 (UTC) Received: (qmail 38169 invoked by uid 500); 8 Jul 2012 19:41:35 -0000 Delivered-To: apmail-incubator-easyant-commits-archive@incubator.apache.org Received: (qmail 38145 invoked by uid 500); 8 Jul 2012 19:41:35 -0000 Mailing-List: contact easyant-commits-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: easyant-dev@incubator.apache.org Delivered-To: mailing list easyant-commits@incubator.apache.org Received: (qmail 38131 invoked by uid 99); 8 Jul 2012 19:41:35 -0000 Received: from issues-vm.apache.org (HELO issues-vm) (140.211.11.160) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 08 Jul 2012 19:41:35 +0000 Received: from isssues-vm.apache.org (localhost [127.0.0.1]) by issues-vm (Postfix) with ESMTP id 79B50141887 for ; Sun, 8 Jul 2012 19:41:35 +0000 (UTC) Date: Sun, 8 Jul 2012 19:41:34 +0000 (UTC) From: "Jean-Louis Boudart (JIRA)" To: easyant-commits@incubator.apache.org Message-ID: <1367960959.20685.1341776495502.JavaMail.jiratomcat@issues-vm> In-Reply-To: <226285265.15521.1311859269787.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Commented] (EASYANT-37) Use an online repository to publish and fetch non core plugins and their dependencies MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/EASYANT-37?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13409047#comment-13409047 ] Jean-Louis Boudart commented on EASYANT-37: ------------------------------------------- As explained in the past we're going to use an online repository [1] for easyant. This repository will : * contain easyant plugins * contain easyant buildtypes * contain easyant skeletons * will not act as a maven proxy All repositories declared bellow will use ivy standard layout. About internal organisation, we will clearly separate apache-easyant-plugins, and the community ones. Community plugins is supposed to host plugin incompatible with Apache requirements like checkstyle, or even your plugins if you want. I suggest to have three level of stagging : * stable : were stuff will be promoted by easyant PMC when they get released, of enough tested * testing : for RC etc... * unstable : for non released plugin (integration version), while the team is developping This applies to both apache and community repository By default, easyant distribution should be preconfigured to know : * apache-easyant-stable * community-easyant-stable Then people are free to modify the configuration if they want to use testing or unstable stuff. Our online repository, offer a virtual repository feature (ability to "hide" complexity of multiple repository on server side). We could for example create two virtual repositories [2] : * apache-easyant : relying on server side on apache-easyant-stable > apache-easyant-testing > apache-easyant-unstable * community-easyant relying on server side on community-easyant-stable > community-easyant-testing > community-easyant-unstable This could be really useful for easyant developpers to fetch stuff from the different staging area while respecting the order (stable first, then testing, then unstable). About authorization now : * EasyAnt PMC's will have admin to manage online repository (make promotion, create repository, etc...) * An account will be created to publish stuff to apache-easyant-* repository. This account will be used by apache ci server * An account will be created to publish community stuff. This account will be used by the community ci server. Third party library will be downloaded from public repository. EasyAnt online repository does not intend to be a public proxy. As an exception, our online repository could host kind of snapshot of library used by the project (ant or ivy for example). > Use an online repository to publish and fetch non core plugins and their dependencies > ------------------------------------------------------------------------------------- > > Key: EASYANT-37 > URL: https://issues.apache.org/jira/browse/EASYANT-37 > Project: EasyAnt > Issue Type: Task > Reporter: Jean-Louis Boudart > Fix For: 0.9 > > > This should replace the third-party-lib repository which is currently filesystem based -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira