Sean
I recently moved to 3.0.3 and believe I ran into the same (or similar)
problem.
I modified the main project pom (../pom.xml), adding
<module>magnolia</module> between the <modules></modules> elements at
the very end of the file. Next, double check the magnolia project pom
(i.e. ../magnolia/pom.xml)has a tag between all the <version> elements
that matches what you have in your maven repository. If they don't
match, update your POM to match what you have available. I seem to
remember the crux of the problem being the pom erroneously referencing
resources with "-SNAPSHOT" appended.
For example, if you have
<dependency>
<groupId>info.magnolia</groupId>
<artifactId>magnolia-module-templating</artifactId>
<version>3.0.3</version>
</dependency>
in your POM, your maven repository needs a
\info\magnolia\magnolia-module-templating\3.0.3
directory.
Finally, I had trouble building with mvn clean install running against
the main project pom, but running it instead against the magnolia
project pom seemed to work OK. Seems counter-intuitive to me, though.
*shrug*
Hope this helps.
-Michael Beaty
Senior Software Engineer
LeapFrog
-----Original Message-----
From: [email protected] [mailto:[EMAIL PROTECTED]
Sent: April 27, 2007 1:48 PM
To: [email protected]
Subject: [magnolia-user] mvn package and 3.0.2
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
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/developer.html
----------------------------------------------------------------
