Hi.
I recently started getting a weird issue building Magnolia 3.0 branch
from svn. It builds all the modules, but not the war. Aparently the
magnolia subproject was missing from the top level pom.xml. When I do
add the magnolia subproject to the list in the top level pom.xml, it
creates the war, but downloads all the other sub-project's jars rather
than use what was just built. I've cleared the local maven repository,
deleted and re-checked out the magnolia branch and built clean with the
same result.
This appears to be new behavior since just over a week ago (approx.
March 19th). Looks like someone was preparing a 3.0.2 release, but only
half done. Any thoughts on what might have changed in the top-level
pom.xml and magnolia subproject pom.xml?
Environment:
Maven 2.0.5
Sun JDK 1.5.0_11
Windows XP SP2
Completely fresh checkout from the 3.0 branch of svn
Thanks.
David
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/developer.html
----------------------------------------------------------------
