On 5 July 2013 13:06, Thomas Neidhart <thomas.neidh...@gmail.com> wrote: > We could also publish it to the Apache public repository but prevent the > sync with maven central.
Is that possible? Anyhow, I'm not sure it makes any difference - it's still published as a Maven jar. So long as it's very clear that the API may change, I don't see a problem with publishing it to Maven Central. > In the announcement and on the site, add instructions on how to us it via > maven (add repository settings for apache public). > > btw. looking at the public repository, it contains also the latest > snapshots for commons components. Is this intended? > > https://repository.apache.org/content/groups/public/ That's apparently normal. See https://issues.apache.org/jira/browse/INFRA-6436 > Thomas > > > On Fri, Jul 5, 2013 at 10:24 AM, Thomas Neidhart > <thomas.neidh...@gmail.com>wrote: > >> Hi, >> >> just to make sure we have agreement on this topic. >> Reading again the thread about release alpha/beta releases I think we did >> not reach consensus whether to publish alpha releases to maven central. >> >> It would be easier for people to try out things, but the release will stay >> there forever and some people had objections against it. >> >> We also know for sure that the API will change, as we will at least rename >> one new class introduced for 4.0 (CompliantBag -> CollectionBag). >> >> So the questions is: >> >> Shall we publish to maven central? >> >> Thomas >> --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
