On 14 October 2013 01:51, Gary Gregory garydgreg...@gmail.com wrote:
On Sun, Oct 13, 2013 at 7:51 PM, sebb seb...@gmail.com wrote:
On 12 October 2013 09:08, Olivier Lamy ol...@apache.org wrote:
why not having those files deployed?
See my reply in another thread.
The Maven project deploys
Just because dist.a.o is the canonical place for the source release to live
does not necessarily mean that the artifact cannot be deployed to Nexus.
We do have the option to let Maven upload everything to Nexus, vote on the
artifacts, and then copy the successfully-voted-on source artifact to
On Tue, Oct 15, 2013 at 12:27 PM, sebb seb...@gmail.com wrote:
On 14 October 2013 01:51, Gary Gregory garydgreg...@gmail.com wrote:
On Sun, Oct 13, 2013 at 7:51 PM, sebb seb...@gmail.com wrote:
On 12 October 2013 09:08, Olivier Lamy ol...@apache.org wrote:
why not having those files deployed?
On 15 October 2013 18:11, Gary Gregory garydgreg...@gmail.com wrote:
On Tue, Oct 15, 2013 at 12:27 PM, sebb seb...@gmail.com wrote:
On 14 October 2013 01:51, Gary Gregory garydgreg...@gmail.com wrote:
On Sun, Oct 13, 2013 at 7:51 PM, sebb seb...@gmail.com wrote:
On 12 October 2013 09:08,
On 15 October 2013 17:53, Matt Benson gudnabr...@gmail.com wrote:
Just because dist.a.o is the canonical place for the source release to live
does not necessarily mean that the artifact cannot be deployed to Nexus.
We do have the option to let Maven upload everything to Nexus, vote on the
Violent agreement. :)
Matt
On Tue, Oct 15, 2013 at 12:19 PM, sebb seb...@gmail.com wrote:
On 15 October 2013 17:53, Matt Benson gudnabr...@gmail.com wrote:
Just because dist.a.o is the canonical place for the source release to
live
does not necessarily mean that the artifact cannot be
On Tue, Oct 15, 2013 at 4:27 PM, Gary Gregory garydgreg...@gmail.com wrote:
On Tue, Oct 15, 2013 at 1:15 PM, sebb seb...@gmail.com wrote:
On 15 October 2013 18:11, Gary Gregory garydgreg...@gmail.com wrote:
On Tue, Oct 15, 2013 at 12:27 PM, sebb seb...@gmail.com wrote:
On 14 October 2013
On Tue, Oct 15, 2013 at 1:15 PM, sebb seb...@gmail.com wrote:
On 15 October 2013 18:11, Gary Gregory garydgreg...@gmail.com wrote:
On Tue, Oct 15, 2013 at 12:27 PM, sebb seb...@gmail.com wrote:
On 14 October 2013 01:51, Gary Gregory garydgreg...@gmail.com wrote:
On Sun, Oct 13, 2013 at 7:51
On 12 October 2013 09:08, Olivier Lamy ol...@apache.org 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).
On Sun, Oct 13, 2013 at 7:51 PM, sebb seb...@gmail.com wrote:
On 12 October 2013 09:08, Olivier Lamy ol...@apache.org 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
why not having those files deployed?
On 11 October 2013 23:21, Emmanuel Bourg ebo...@apache.org 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
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:
On 2013-10-11, Emmanuel Bourg 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?
Sebb did some investigation back in May, I think. IIRC this implies
they won't get signed
13 matches
Mail list logo
