I've just updated our lightly-customized version of magnolia from 3.0.1 to 3.0.2 using a merge in subversion, but am now having difficulty getting a WAR out of the system.
I used to be able to do "mvn clean install" at the trunk directory and have maven spit a war out the other end. When I do so now, it appears to build all the module jars and puts them in the maven repository, but doesn't do anything from the magnolia module. I read through the list archives, and they seemed to indicate that a "cd magnolia; mvn package" should now do the trick. Unfortunately, I get errors when I try this: GroupId: info.magnolia ArtifactId: magnolia-project Version: 3.0.2-SNAPSHOT Reason: Unable to download the artifact from any repository info.magnolia:magnolia-project:pom:3.0.2-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2) So it looks like the snapshot is supposed to be generated and installed to the repository somewhere along the way, but it isn't happening. I would guess trunk/pom.xml is the place where this is supposed to happen, but I'm afraid I'm not yet maven-savvy enough to sort out why it's not occurring in my case. Does anybody have any insight into what I need to be doing to get maven to start spitting out WAR files again? Thanks for any help, Sean ---------------------------------------------------------------- for list details see http://www.magnolia.info/en/developer.html ----------------------------------------------------------------
