That's sort of what I've been doing, thanks! :-)
Andrus
On Jul 2, 2007, at 3:38 PM, Grégory Joseph wrote:
On Jul 2, 2007, at 13:09 , Andrus Adamchik wrote:
Cool, thanks!
Now I can build a single working war. When building a bundle I am
still getting a long stack trace that (in a trimmed form) looks
like this:
[INFO] INFO info.magnolia.cms.beans.config.ConfigLoader
ConfigLoader.java(load:133) 02.07.2007 13:50:31 Configuration
loaded!
[INFO] [INFO] About to execute 4 post-bootstrappers ...
[INFO] [INFO]
---------------------------------------------------------------------
---
[INFO] [ERROR] BUILD ERROR
[INFO] [INFO]
---------------------------------------------------------------------
---
[INFO] [INFO] can't call execute() method on the inner mojo
....
[INFO] Caused by: java.lang.IncompatibleClassChangeError
[INFO] at info.magnolia.maven.bootstrap.post.OrderNodes.execute
(OrderNodes.java:45)
[INFO] ... 35 more
Since I can build a minimally working deployable file, this one is
not a biggie at the moment. Still wanted to mention.
Well, I guess we'll fix that next time we need to build a bundle ;)
All it does is bootstrap 2 wars, one as Author, the other as
Public. In the meantime you can do that "manually" by deploying non-
bootstrapped war files with appropriate names (ie
magnoliaAuthor.war and magnoliaPublic.war)
hth
g
----------------------------------------------------------------
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
----------------------------------------------------------------
