On 15 October 2013 18:11, Gary Gregory <[email protected]> wrote: > On Tue, Oct 15, 2013 at 12:27 PM, sebb <[email protected]> wrote: >> On 14 October 2013 01:51, Gary Gregory <[email protected]> wrote: >>> On Sun, Oct 13, 2013 at 7:51 PM, sebb <[email protected]> wrote: >>>> On 12 October 2013 09:08, Olivier Lamy <[email protected]> wrote: >>>>> why not having those files deployed? >>>> >>>> See my reply in another thread. >>>> The Maven project deploys these to Maven Central. >>>> >>>> The primary release channel for the bin and src tarballs must be the >>>> ASF mirror system, not Maven Central (MC). >>>> Does this mean that we cannot publish to MC as well? I don't know. >>> >>> It would make my life easier if every thing was published to one >>> place. MC is good because Maven and Ivy know how to resolve to those. >> >> ASF releases must be via the ASF mirrors; Maven jars must be to a Maven repo. >> It's not possible to publish to a single place. >> >>> No one tools know how to resolve to Apache "dist" or whatnot. >> >> Not sure I follow what you mean here. > > What I mean here is that tools like Maven and Ivy know how to fetch > jars from Maven repos, not from dist.a.o. > > While it is essential to have an official home for our jars, it would > be simpler if that home where a Maven repo. > > I have, at work, cases where we need the actual -bin from projects > like JMeter and ActiveMQ to run tests. Right now we need to manually > add these to our own repos, which is a manual process, and a pain. If > the -bin files where in Apache's Maven repo, no more headaches.
JMeter jars are released to Maven Central - there should be no need for additional input. If there is a problem with the contents, please raise this as a bug. > Gary > >> >>> I understand that we have to publish to an Apache location, but maybe >>> there is a way to make it easier. >> >> AFAIK the only choice is: >> + to use Nexus for both Maven and ASF artifacts >> + or use Nexus for Maven and the SVN dist/dev tree for ASF artifacts >> >>> Gary >>>> >>>>> On 11 October 2013 23:21, Emmanuel Bourg <[email protected]> wrote: >>>>>> The parent pom currently attaches the -bin and -src archives to the >>>>>> deploy phase, which means we have to delete them manually in Nexus. >>>>>> >>>>>> Can we agree to change that? >>>>>> >>>>>> Emmanuel Bourg >>>>>> >>>>>> >>>>>> --------------------------------------------------------------------- >>>>>> To unsubscribe, e-mail: [email protected] >>>>>> For additional commands, e-mail: [email protected] >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Olivier Lamy >>>>> Ecetera: http://ecetera.com.au >>>>> http://twitter.com/olamy | http://linkedin.com/in/olamy >>>>> >>>>> --------------------------------------------------------------------- >>>>> To unsubscribe, e-mail: [email protected] >>>>> For additional commands, e-mail: [email protected] >>>>> >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: [email protected] >>>> For additional commands, e-mail: [email protected] >>>> >>> >>> >>> >>> -- >>> E-Mail: [email protected] | [email protected] >>> Java Persistence with Hibernate, Second Edition >>> JUnit in Action, Second Edition >>> Spring Batch in Action >>> Blog: http://garygregory.wordpress.com >>> Home: http://garygregory.com/ >>> Tweet! http://twitter.com/GaryGregory >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > > > > -- > E-Mail: [email protected] | [email protected] > Java Persistence with Hibernate, Second Edition > JUnit in Action, Second Edition > Spring Batch in Action > Blog: http://garygregory.wordpress.com > Home: http://garygregory.com/ > Tweet! http://twitter.com/GaryGregory > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
