Hi there,
I've seen this topic debated many times, and still haven't figured
everything out. I was recently confused by the handling and
inheritance of urls in Maven. I think I got most of it, when it comes
to project.url.
Now, when it comes to deploying a site, I'm baffled. Up to
Grégory Joseph wrote:
Hi there,
I've seen this topic debated many times, and still haven't figured
everything out. I was recently confused by the handling and
inheritance of urls in Maven. I think I got most of it, when it comes
to project.url.
Now, when it comes to deploying a site,
Hi Lukas,
On 2 July 2012 13:18, Lukas Theussl ltheu...@apache.org wrote:
Grégory Joseph wrote:
It kind of sounds like MSITE-600 to me, so I'm unsure if/how the issue
was fixed. Example:
* Corporate parent pom defines this site deployment url:
prot://foo/${artifactId}/${version} -- it works
Just tried staging, and indeed, the paths in that case are correct* -
but again, I'm assuming that's because the normalization is done and
supported by my local FS ?
-g
* with the strange bug that https://nexus.domain.org/xyz; was
converted to targetstaging/http/s.domain.org/xyz ...
On 2 July
Grégory Joseph wrote:
Just tried staging, and indeed, the paths in that case are correct* -
but again, I'm assuming that's because the normalization is done and
supported by my local FS ?
IIRC normalization is done by the wagon you are using for the deploy, so
it's outside the realm of the
On 2 July 2012 14:38, Lukas Theussl ltheu...@apache.org wrote:
Grégory Joseph wrote:
Just tried staging, and indeed, the paths in that case are correct* -
I take it back. Staging was fine… with 2.1.1.
With 3.1 I get this, for example for last module of the multi-module build
[INFO] Pushing
