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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Brett Porter
[EMAIL PROTECTED]
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Brett Porter
[EMAIL PROTECTED]
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
