Brian Fox-3 wrote:
>
> In theory this would be possible, but the paths probably need to be
> rooted in the same location.
>
I think it can not be a path problem.
When I change the url of the distributionManagement to
file:///home/thomas/test-repo
It all works. The maven-metadata is created.
As soon as I switch to sftp://... the deploy stops with the exception, that
the maven-metadata.xml can not be received (which is right, as it does not
exists, yet). The url is the only path I change, so I rule out a pathing
issue. But, why maven skips the missing of the metadata when the deploy url
is local but stops when the url is remote?
Is there a bug in tssh wagon?
I found http://maven.apache.org/wagon/wagon-providers/wagon-ssh/
"Getting files from SSH servers is not fully tested."
Brian Fox-3 wrote:
>
> When Maven goes to deploy, it uses the
> same channel to retrieve the metadata files that need to be updated.
> It seems like your system is interfering with this process.
>
It seems that it can skip the missing of the metadata when deploying local
but stops, when deploying remote.
Thankls for any help.
Cheers,
Thomas
--
View this message in context:
http://n2.nabble.com/Error-during-deploy-in-private-repository-tp3687411p3714504.html
Sent from the maven users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
