See in maven when we build a module it also looks for dependent module first. So they have to be built before. When you are building say product-enterprise-web you should always build the following first: 1. platform-core 2. platform-plugins 3. platform-skins 4. platform-web In that said order. Now if you notice that product-enterprise-web = platform-web + platform-plugin So if you just always build the platform-web and add plugins to it you get the product-enterprise (of course you have to modify xwiki.cfg to add built plugins). I suspect in your case it might be getting the platform-web war from the maven repository, may be -nsu flag prevents it. Here is a process you may want to follow: I build xwiki from source daily and the whole process is automated via ant scripts. Ant executes mvn targets and using ant-maven dependency tasks it automatically copies the additional plugin jars to lib folder of my build. Whole process takes not more that 2 - 3 minutes. Thanks Sachin ------------------------------
Message: 6 Date: Tue, 1 Apr 2008 17:34:59 -0500 From: "Kamna Jain" <[email protected]> Subject: [xwiki-devs] Question about the Build process. To: [email protected] Message-ID: <[email protected]> Content-Type: text/plain; charset=ISO-8859-1
Hello,
I am trying to make soem changes to the XWikiHibernateAttachmentStore class.
So the procees I follow while building is:
1) Build the xwiki core using mvn install 2) build the Xwiki Enterprise application using - mvn -nsu install -Pxe 3) after this I replace the existing xwiki folder with the newly updated one (from the target folder)
Is this the right way to do. I am wondering because it takes almost 8 - 10 mins to build the Enterprise every time I make any small change in the Core code.
Thanks.