I submitted a patch for wagon-scm to auto-generate the missing directories
while SCM-487 is not yet in maven-scm trunk.
The patch is in http://jira.codehaus.org/browse/WAGON-297
Thanks,
Deng
On Thu, Jan 7, 2010 at 6:19 PM, Deng Ching wrote:
> Ok, thanks for all your inputs :) I'll look into the
Ok, thanks for all your inputs :) I'll look into these suggestions..
-Deng
On Thu, Jan 7, 2010 at 6:11 PM, Olivier Lamy wrote:
> Hi,
> I would prefer using the --parents option too.
> The issue already exists [1].
> I have reverted due to the svn 1.5 requirements.
>
> BTW, this change can be ad
Hi,
I would prefer using the --parents option too.
The issue already exists [1].
I have reverted due to the svn 1.5 requirements.
BTW, this change can be added in this project [2]. And you can use
this provider (svnjava) instead of the svnexe one.
--
Olivier
[1] http://jira.codehaus.org/browse/S
On 07/01/2010, at 2:37 PM, Deng Ching wrote:
> After looking through the code, I came up with two possible fixes for this:
>
> 1. Fix it in wagon-scm by automatically creating the missing directories
> when an error is encountered during checkout when a deployment is performed.
> Instead of chan
Hi All,
I'm trying to fix http://jira.codehaus.org/browse/SCM-511, which occurs when
you try to publish a site to an SVN repository where the base directory does
not exist yet. An example scenario is when you have the following
configuration in your POM:
site.svn
scm:svn:
https://m