You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Brett Porter <br...@apache.org> on 2008/10/03 06:53:25 UTC
Re: Mercury wagon provider
Ping
On 26/09/2008, at 11:22 PM, Brett Porter wrote:
> Oleg,
>
> Sorry for the delay. I'm still planning to dig into this once I get
> my head above water, but a couple of questions occurred to me in the
> mean time:
>
> * Does it make sense to release the mercury transport stuff (I
> believe otherwise known as awesome-jetty-bits) separately to have it
> available sooner?
>
> * I'd previously wondered how, once integrated into Maven, alternate
> deployment mechanisms would be handled (scp, etc). Would mercury, as
> the new API, delegate to other wagons, or would they sit side by
> side as alternatives?
>
> * Given the above, if the answer is delegate, does it make more
> sense to move forward with that than to force mercury into wagon?
>
> Thanks,
> Brett
>
> On 18/09/2008, at 2:19 AM, Oleg Gusakov wrote:
>
>> In order to show/test Mercury transport layer, I implemented
>> Mercury wagon provider. The first one could be deployed into any
>> (I hope) Maven >= 2.0.9 and implements two protocols: mttp and
>> mttps, so that it could be used in parallel with http and https
>> providers. It can be configured generate/verify PGP signatures.
>>
>> Upload protocol - is webDAV, encoded the same - mttp or mttps. I
>> only tested uploads with Nexus.
>>
>> Details and provider binaries - http://jira.codehaus.org/browse/MERCURY-8
>> - grab the zip and unpack it into $M2_HOME/lib, then define your
>> mttp serevrs in pom.xml and/or settings.xml, examples in Jira
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>
> --
> Brett Porter
> brett@apache.org
> http://blogs.exist.com/bporter/
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
--
Brett Porter
brett@apache.org
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Mercury wagon provider
Posted by Brett Porter <br...@apache.org>.
On 03/10/2008, at 3:16 PM, Oleg Gusakov wrote:
>>> * Does it make sense to release the mercury transport stuff (I
>>> believe otherwise known as awesome-jetty-bits) separately to have
>>> it available sooner?
> I am working on that, will try to stage tomorrow.
Ah, so you mean release the whole thing, but just use certain bits of
it for now?
I'd like to see it out of the sandbox before doing the release... and
I'm pretty sure everyone needs a bit of lead time to review it since
this is no small thing :)
It was on my list for next week as I was keen to see how you
implemented PGP to compare notes with the solution I have in place.
Thanks!
Cheers,
Brett
--
Brett Porter
brett@apache.org
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Mercury wagon provider
Posted by Oleg Gusakov <ol...@gmail.com>.
Brett Porter wrote:
> Ping
Sorry - did not catch this posting.
>
> On 26/09/2008, at 11:22 PM, Brett Porter wrote:
>
>> Oleg,
>>
>> Sorry for the delay. I'm still planning to dig into this once I get
>> my head above water, but a couple of questions occurred to me in the
>> mean time:
>>
>> * Does it make sense to release the mercury transport stuff (I
>> believe otherwise known as awesome-jetty-bits) separately to have it
>> available sooner?
I am working on that, will try to stage tomorrow.
>>
>> * I'd previously wondered how, once integrated into Maven, alternate
>> deployment mechanisms would be handled (scp, etc). Would mercury, as
>> the new API, delegate to other wagons, or would they sit side by side
>> as alternatives?
TBD. For now - Mercury has Transport abstraction layer and the only
implementation for http/https/dav, so all other provider can co-exist.
>>
>> * Given the above, if the answer is delegate, does it make more sense
>> to move forward with that than to force mercury into wagon?
It makes sense to release Mercury as soon as possible, so that we can
try it in real world and fix the bugs, that any program is said to have
:) Please also see my answer to the first question.
Thanks,
Oleg
>>
>> Thanks,
>> Brett
>>
>> On 18/09/2008, at 2:19 AM, Oleg Gusakov wrote:
>>
>>> In order to show/test Mercury transport layer, I implemented Mercury
>>> wagon provider. The first one could be deployed into any (I hope)
>>> Maven >= 2.0.9 and implements two protocols: mttp and mttps, so that
>>> it could be used in parallel with http and https providers. It can
>>> be configured generate/verify PGP signatures.
>>>
>>> Upload protocol - is webDAV, encoded the same - mttp or mttps. I
>>> only tested uploads with Nexus.
>>>
>>> Details and provider binaries -
>>> http://jira.codehaus.org/browse/MERCURY-8 - grab the zip and unpack
>>> it into $M2_HOME/lib, then define your mttp serevrs in pom.xml
>>> and/or settings.xml, examples in Jira
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>
>> --
>> Brett Porter
>> brett@apache.org
>> http://blogs.exist.com/bporter/
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>
> --
> Brett Porter
> brett@apache.org
> http://blogs.exist.com/bporter/
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org