Mailing-List: contact issues-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: issues@commons.apache.org
Date: Fri, 20 Mar 2015 15:55:38 +0000 (UTC)
From: "John McKowen Taylor (JIRA)" <jira@apache.org>
To: issues@commons.apache.org
Message-ID: <JIRA.12783634.1426863153000.158076.1426866938790@Atlassian.JIRA>
In-Reply-To: <JIRA.12783634.1426863153000@Atlassian.JIRA>
References: <JIRA.12783634.1426863153000@Atlassian.JIRA>
 <JIRA.12783634.1426863153466@arcas>
Subject: [jira] [Updated] (BCEL-215) Wish BCEL would publish pre-release
 versions to maven central
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

John McKowen Taylor updated BCEL-215:
-------------------------------------
    Summary: Wish BCEL would publish pre-release versions to maven central  (was: Wish BCEL would automagically publish packages to maven central)

> Wish BCEL would publish pre-release versions to maven central
> -------------------------------------------------------------
>
>                 Key: BCEL-215
>                 URL: https://issues.apache.org/jira/browse/BCEL-215
>             Project: Commons BCEL
>          Issue Type: Wish
>          Components: Build
>    Affects Versions: 6.x
>            Reporter: John McKowen Taylor
>            Priority: Minor
>              Labels: build, maven
>             Fix For: unspecified
>
>   Original Estimate: 168h
>  Remaining Estimate: 168h
>
> As a consumer of BCEL, I want BCEL builds to automagically publish finished packages to Maven Central, so I can simply require BCEL jars in my build scripts and let Maven or Gradle retrieve them as needed.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)