The dms has its own lifecycle which means that we don't update its
pom on every release of the main project. In the moment where you
build all together (main project, dms, ...) maven is smart enough to
take only the latest version of core. Check the webapp after the
build and WEB-INF/lib should be fine.
After releasing the webapp pom will not update to the latest dms
snapshot immediately as it depends upon the latest stable release of
dms.
As we have more and more modules (workflow, dms, data, scheduler,
forum, poll) you might see why this things are that much independent.
To be on the save side you do:
- mvn install main project
- mvn install of the modules
- mvn install of the webapp
In case you have to build all in one reactor you must update the poms
yourself.
Philipp Bracher
On 11.12.2007, at 17:17, Amir Mistric wrote:
Well
I just tried again and this time I deleted all magnolia artifacts
from local repo (except parent pom and build tools) and used:
mvn -o -Dall=true -Pwith-optional-modules clean install
The DMS fails to build because it "wants" specifically:
1) info.magnolia:magnolia-core:jar:3.5-rc2
2) info.magnolia:magnolia-gui:jar:3.5-rc2
3) info.magnolia:magnolia-module-admininterface:jar:3.5-rc2
4) info.magnolia:magnolia-taglib-cms:jar:3.5-rc2
I did "offline" on purpose to see if the DMS would use artifacts
from the current build (RC4) that are bing installed as I build
them...
But then I checked the DMS POM and sure enough, it is not depending
on rc4 artifacts...
Regards
Amir
-----Original Message-----
From: [email protected] [mailto:[EMAIL PROTECTED]
Sent: Monday, December 10, 2007 3:38 PM
To: [email protected]
Subject: Re: [magnolia-dev] latest deploy error - DMS version
Am 10.12.2007 um 14:49 schrieb Amir Mistric:
Just did a SVN update and tried to deploy the WAR with workflow,
samples and DMS....
ERROR org.apache.catalina.core.ContainerBase.[jboss.web].
[localhost].[/magnoliaAuthor] StandardContext.java(listenerStart:
3767) 10.12.2007 08:44:34 Exception sending context
initialized event
t o listener instance of class
info.magnolia.cms.servlets.MgnlServletContextListener
java.lang.RuntimeException:
info.magnolia.module.model.reader.ModuleDependencyException: Module
dms (version 1.2.0-SNAPSHOT) is dependent on adminInterface version
3.1, but Magnolia Admin Interfa ce Module (version
3.5.0-rc4-SNAPSHOT)
is currently installed.
at
info.magnolia.cms.servlets.MgnlServletContextListener.contextInitiali
z
ed(MgnlServletContextListener.java:200)
are you sure that the latest DMS is also build in your maven
reactor and not picked up from you local or Magnolia's
snapshot mvn repository? It seems that the dms.xml module
descriptor file still has the dependency to admin interface
3.1 which is not the case since
r12536 (November, 14th) anymore. Maybe dms 1.2 snapshot was
not deployed since, thus Magnolia's snapshot repo is not up-to-date.
HTH.
Cheers,
- vivian
I know that DMS is on a "separate" development cycle, but
it would be
nice to be able to test with these 3 modules :)
Regards
Amir
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------
