[
https://issues.apache.org/jira/browse/BCEL-215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John McKowen Taylor reopened BCEL-215:
--------------------------------------
(I just updated the title to be more accurate)
Can you please confirm, then, that the reason pre-release packages are not
published is due to Apache policy?
I just scanned Apache's release process and it seems that is the case, that
there is a fairly high bar to be cleared for publishing a release.
I am coming from a more Continuous Integration workflow, in which consumers
configure their build process to either consume latest, possibly broken,
snapshot version - or they lock the version at a specific, qualified version -
so the upstream artifact publisher is therefore free to publish often, with
less concern about the stability of individual releases. Seems Apache has more
of a "Cathedral" model of releases.
Thanks again for your responses.
best,
John
> 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)
