On 9 May 2015 at 21:07, Ralph Goers <ralph.go...@dslextreme.com> wrote: > You can publish an alpha or a beta and still change the API. That really > isn’t locked in until the first official GA release.
In theory, perhaps, at least with an alpha release. However how many people take note of the alpha/beta status of the code? Any project that depends on an alpha/beta release ought itself to be labelled as alpha/beta - does that happen? If not, then downstream projects may get a nasty shock. > Ralph > >> On May 7, 2015, at 3:44 AM, sebb <seb...@gmail.com> wrote: >> >> Yes, it might cause a problem to publish an RC. >> >> Any publication to Maven Central effectively freezes the current public API. >> If a problem is then found, generally the only solution that avoids >> jar hell is to release a new version with different package name and >> different Maven coords - i.e. effectively a different product. >> This will not be a drop-in replacement, and will require source code >> changes by anyone using it. >> >> On 7 May 2015 at 03:54, DiFrango, Ronald (CONT) >> <ronald.difra...@capitalone.com> wrote: >>> Yeah, I would prefer to avoid the snap-shot repo, so if nothing else I'll >>> build a version locally and upload it to our local Nexus. >>> >>> One question, if this is close, would it hurt to pulish an "RC" into Maven >>> Central? >>> >>> -----Original Message----- >>> From: sebb [mailto:seb...@gmail.com] >>> Sent: Wednesday, May 06, 2015 9:20 PM >>> To: Commons Users List >>> Subject: Re: [configuration] Apache Commons Configuration Version 2 >>> >>> You should also be able to get it from the ASF snapshot repo. >>> >>> However note that such artifacts may change or disappear at any time, so >>> should only be used for testing. >>> >>> On 6 May 2015 at 20:07, Oliver Heger <oliver.he...@oliver-heger.de> wrote: >>>> Hi Ron, >>>> >>>> Am 06.05.2015 um 03:38 schrieb DiFrango, Ronald (CONT): >>>>> Oliver, >>>>> >>>>> I guess I could build it from source and store it in our local Nexus >>>>> until a release version is built. >>>>> >>>> >>>> this is of course possible. I do not expect major or breaking changes >>>> until the final release. >>>> >>>> Thanks for your feedback, this is indeed motivating :-) >>>> >>>> Oliver >>>> >>>>> Ron DiFrango >>>>> >>>>> -----Original Message----- >>>>> From: DiFrango, Ronald (CONT) [mailto:ronald.difra...@capitalone.com] >>>>> Sent: Tuesday, May 05, 2015 4:23 PM >>>>> To: Commons Users List >>>>> Subject: RE: [configuration] Apache Commons Configuration Version 2 >>>>> >>>>> Oliver, >>>>> >>>>> I figured it would be something like that and that's understandable as is >>>>> the time-table. We definitely like the feature set of 2.x as it supports >>>>> many of the uses cases more naturally than 1.x so would like to move >>>>> forward with it. >>>>> >>>>> But I can't unless it's in maven central. >>>>> >>>>> Thanks, >>>>> >>>>> Ron >>>>> >>>>> >>>>> -----Original Message----- >>>>> From: Oliver Heger [mailto:oliver.he...@oliver-heger.de] >>>>> Sent: Tuesday, May 05, 2015 4:20 PM >>>>> To: Commons Users List >>>>> Subject: Re: [configuration] Apache Commons Configuration Version 2 >>>>> >>>>> Hi Ron, >>>>> >>>>> Am 05.05.2015 um 22:09 schrieb DiFrango, Ronald (CONT): >>>>>> All, >>>>>> >>>>>> Is Apache commons configuration in maven central or some other repo? >>>>>> I'm using Gradle and pointing to an internal Nexus repo that is a proxy >>>>>> for Maven central and I can't resolve it as follows: >>>>>> >>>>>> compile group: 'org.apache.commons', name: 'commons-configuration2', >>>>>> version: '2.0-alpha2' >>>>>> >>>>>> >>>>> >>>>> because it is only an alpha release, this version has not been deployed >>>>> to a public Maven repository. We did this by intension to avoid potential >>>>> jar hell if there are still binary incompatible changes before the final >>>>> release. >>>>> >>>>> I am working to get the final version 2.0 out, but unfortunately my time >>>>> is currently pretty limited. So I cannot predict a release schedule. >>>>> >>>>> Oliver >>>>> >>>>>> Thanks, >>>>>> >>>>>> Ron >>>>>> >>>>>> ________________________________________________________ >>>>>> >>>>>> The information contained in this e-mail is confidential and/or >>>>>> proprietary to Capital One and/or its affiliates. The information >>>>>> transmitted herewith is intended only for use by the individual or >>>>>> entity to which it is addressed. If the reader of this message is not >>>>>> the intended recipient, you are hereby notified that any review, >>>>>> retransmission, dissemination, distribution, copying or other use of, or >>>>>> taking of any action in reliance upon this information is strictly >>>>>> prohibited. If you have received this communication in error, please >>>>>> contact the sender and delete the material from your computer. >>>>>> >>>>> >>>>> --------------------------------------------------------------------- >>>>> To unsubscribe, e-mail: user-unsubscr...@commons.apache.org >>>>> For additional commands, e-mail: user-h...@commons.apache.org >>>>> >>>>> ________________________________________________________ >>>>> >>>>> The information contained in this e-mail is confidential and/or >>>>> proprietary to Capital One and/or its affiliates. The information >>>>> transmitted herewith is intended only for use by the individual or entity >>>>> to which it is addressed. If the reader of this message is not the >>>>> intended recipient, you are hereby notified that any review, >>>>> retransmission, dissemination, distribution, copying or other use of, or >>>>> taking of any action in reliance upon this information is strictly >>>>> prohibited. If you have received this communication in error, please >>>>> contact the sender and delete the material from your computer. >>>>> >>>>> >>>>> --------------------------------------------------------------------- >>>>> To unsubscribe, e-mail: user-unsubscr...@commons.apache.org >>>>> For additional commands, e-mail: user-h...@commons.apache.org >>>>> >>>>> ________________________________________________________ >>>>> >>>>> The information contained in this e-mail is confidential and/or >>>>> proprietary to Capital One and/or its affiliates. The information >>>>> transmitted herewith is intended only for use by the individual or entity >>>>> to which it is addressed. If the reader of this message is not the >>>>> intended recipient, you are hereby notified that any review, >>>>> retransmission, dissemination, distribution, copying or other use of, or >>>>> taking of any action in reliance upon this information is strictly >>>>> prohibited. If you have received this communication in error, please >>>>> contact the sender and delete the material from your computer. >>>>> >>>>> >>>>> --------------------------------------------------------------------- >>>>> To unsubscribe, e-mail: user-unsubscr...@commons.apache.org >>>>> For additional commands, e-mail: user-h...@commons.apache.org >>>>> >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: user-unsubscr...@commons.apache.org >>>> For additional commands, e-mail: user-h...@commons.apache.org >>>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: user-unsubscr...@commons.apache.org >>> For additional commands, e-mail: user-h...@commons.apache.org >>> >>> ________________________________________________________ >>> >>> The information contained in this e-mail is confidential and/or proprietary >>> to Capital One and/or its affiliates. The information transmitted herewith >>> is intended only for use by the individual or entity to which it is >>> addressed. If the reader of this message is not the intended recipient, >>> you are hereby notified that any review, retransmission, dissemination, >>> distribution, copying or other use of, or taking of any action in reliance >>> upon this information is strictly prohibited. If you have received this >>> communication in error, please contact the sender and delete the material >>> from your computer. >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: user-unsubscr...@commons.apache.org >> For additional commands, e-mail: user-h...@commons.apache.org >> > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscr...@commons.apache.org > For additional commands, e-mail: user-h...@commons.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@commons.apache.org For additional commands, e-mail: user-h...@commons.apache.org
