Kareem Al Jabr wrote: > I would like to have a clear picture on how the build process should be. I > checked out the source code from SVN and I also added dependencies on STK > module and all is working fine. Now I use the generated WAR file in the > target folder of magnolia-empty-webapp as my author instance WAR file. And I > added the public instance located in the Apache bundle webapp folder. Now I > work on my site through the admin central by applying styles and modifying > templates definitions if needed.
There is not 'one right way' for your build process. We don't check out the source from Subversion, but have set up our own Maven project based on the Magnolia empty web app jar and added the modules we want to have in our setup. And then we add our own custom code and configuration in our own additional modules. > Note: I use MySQL as my repository. If I need to make changes on the source > code I have to build the author instance again, will this override my > modifications to the styles and template definitions I modified in the > previous war file? Any configuration stored in MySQL will be persisted, unless an update overwrites this data. We use local instances of Magnolia during development and export our repository modifications to XML and commit these XML files in our build, so they get bootstrapped when the code is deployed. > And What about the public instance!? is it enough to keep working on the > folder I've extracted from the Apache bundle? or I can create a copy of the > generated WAR file from source code and rename it as public instance? You can use a WAR file with multiple configurations: http://documentation.magnolia-cms.com/cookbook/using-a-single-war-file-with-multiple-configurations.html Nils. ------------------------------------------------------------------------ VPRO www.vpro.nl ------------------------------------------------------------------------ ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
