Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=27187&projectId=72
Build statistics:
State: Failed
Previous State: Failed
Started at: Sat 13 Jul 2013 20:20:11 +
Finished at: Sat 13 Jul 2013 20:21:31 +
Total time: 1m 20s
Build Trigger: Schedule
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=27186&projectId=72
Build statistics:
State: Failed
Previous State: Ok
Started at: Sat 13 Jul 2013 19:20:08 +
Finished at: Sat 13 Jul 2013 19:21:36 +
Total time: 1m 28s
Build Trigger: Schedule
Buil
On 13 July 2013 15:26, Gary Gregory wrote:
> On Sat, Jul 13, 2013 at 8:30 AM, sebb wrote:
>
>>
>>
>> I've done some more investigations.
>>
>> It seems it's not possible to use mvn deploy directly to a dist URL such as
>> https://dist.apache.org/repos/dist/dev/commons/plugins
>> Probably becau
On Sat, Jul 13, 2013 at 8:30 AM, sebb wrote:
>
>
> I've done some more investigations.
>
> It seems it's not possible to use mvn deploy directly to a dist URL such as
> https://dist.apache.org/repos/dist/dev/commons/plugins
> Probably because the server does not support WEBDAV or something.
>
I've done some more investigations.
It seems it's not possible to use mvn deploy directly to a dist URL such as
https://dist.apache.org/repos/dist/dev/commons/plugins
Probably because the server does not support WEBDAV or something.
However, there is a workround:
- checkout the URL locally, s