this should be fixed in SVN. As soon as I've verified that MNG-2124 is
fixed as well (should be *very* shortly now), I'll put together a new RC
and call a new vote...unless anyone else has any objections? BTW, I've
moved MNG-1797 off of the 2.0.3 radar, since the general sentiment seems
to be that it needs more thought.
-john
Fabrizio Giustina wrote:
Still playing with this rc with multiproject builds with a flat
layout: after the DefaultModelInheritanceAssembler fix everything work
as expected but I got my website broken due to a different behaviour
during publishing.
In my root module the website root directory is /x/htdocs. With the
previous m2 releases the root module got published to /x/htdocs and
child modules to /x/htdocs/modulename.
Now what happens is that the root module is still published to
/x/htdocs but child modules are (unsuccessfully) published at
/x/modulename (argh, out of the webserver root).
Is this an intentional change in MNG-2006 ? I would expect that pom
relative urls should not influence the website location (while they do
influence the svn url, since the parent path need to be used to get
the parent pom location... but this has nothing to do with published
website)
WDYT?
fabrizio
On 3/3/06, John Casey <[EMAIL PROTECTED]> wrote:
This is the newest RC binary, including Kenney's fixes for MNG-1317 and
MNG-1318, along with the fix for the NPE noted earlier in
DefaultModelInheritanceAssembler.
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20060303.193236.tar.gz
Enjoy,
John
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
