This discussion belongs on a JMeter mailing list.
Probably the dev list.
On 15 October 2013 21:28, Gary Gregory wrote:
> On Tue, Oct 15, 2013 at 4:27 PM, Gary Gregory wrote:
>> On Tue, Oct 15, 2013 at 1:15 PM, sebb wrote:
>>> On 15 October 2013 18:11, Gary Gregory wrote:
On Tue, Oct 15, 2
On Tue, Oct 15, 2013 at 1:15 PM, sebb wrote:
> On 15 October 2013 18:11, Gary Gregory wrote:
>> On Tue, Oct 15, 2013 at 12:27 PM, sebb wrote:
>>> On 14 October 2013 01:51, Gary Gregory wrote:
On Sun, Oct 13, 2013 at 7:51 PM, sebb wrote:
> On 12 October 2013 09:08, Olivier Lamy wrote:
On Tue, Oct 15, 2013 at 4:27 PM, Gary Gregory wrote:
> On Tue, Oct 15, 2013 at 1:15 PM, sebb wrote:
>> On 15 October 2013 18:11, Gary Gregory wrote:
>>> On Tue, Oct 15, 2013 at 12:27 PM, sebb wrote:
On 14 October 2013 01:51, Gary Gregory wrote:
> On Sun, Oct 13, 2013 at 7:51 PM, sebb
Violent agreement. :)
Matt
On Tue, Oct 15, 2013 at 12:19 PM, sebb wrote:
> On 15 October 2013 17:53, Matt Benson 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 ha
On 15 October 2013 17:53, Matt Benson 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
> artifacts, and then
On 15 October 2013 18:11, Gary Gregory wrote:
> On Tue, Oct 15, 2013 at 12:27 PM, sebb wrote:
>> On 14 October 2013 01:51, Gary Gregory wrote:
>>> On Sun, Oct 13, 2013 at 7:51 PM, sebb wrote:
On 12 October 2013 09:08, Olivier Lamy wrote:
> why not having those files deployed?
>>>
On Tue, Oct 15, 2013 at 12:27 PM, sebb wrote:
> On 14 October 2013 01:51, Gary Gregory wrote:
>> On Sun, Oct 13, 2013 at 7:51 PM, sebb wrote:
>>> On 12 October 2013 09:08, Olivier Lamy wrote:
why not having those files deployed?
>>>
>>> See my reply in another thread.
>>> The Maven project
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
dist
On 14 October 2013 01:51, Gary Gregory wrote:
> On Sun, Oct 13, 2013 at 7:51 PM, sebb wrote:
>> On 12 October 2013 09:08, Olivier Lamy wrote:
>>> why not having those files deployed?
>>
>> See my reply in another thread.
>> The Maven project deploys these to Maven Central.
>>
>> The primary rele
On Sun, Oct 13, 2013 at 7:51 PM, sebb wrote:
> On 12 October 2013 09:08, Olivier Lamy 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
> A
On 12 October 2013 09:08, Olivier Lamy 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 th
why not having those files deployed?
On 11 October 2013 23:21, 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?
>
> Emmanuel Bourg
>
>
> --
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 sign
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: dev-unsubscr...@commo
14 matches
Mail list logo
