[ http://jira.magnolia.info/browse/MAGNOLIA-411?page=comments#action_11029 ] Philipp Bracher commented on MAGNOLIA-411: ------------------------------------------
>> - what is about the different bootstrap (security entries, subscriibers, ..) > in the properties file you can set the magnolia.bootstrap.dir to a different > directory and package multiple set of configurations in the same war. I thought about something like a modification of the bootstrap (xml files), so that we don't have to make an extra export after each change in the configuration (having two directories). How ever we can extend the property file and behavior later on. >From the usability point of view i would prefer a context parameter (web.xml) >which defines the configuration directory. This would avoid this magic >directory naming. > public instance in deployed war file > ------------------------------------ > > Key: MAGNOLIA-411 > URL: http://jira.magnolia.info/browse/MAGNOLIA-411 > Project: magnolia wcm > Type: Improvement > Components: build system (maven) > Versions: 2.1 Developer Preview > Reporter: Pascal Mangold > Assignee: Boris Kraft > Priority: Blocker > Fix For: 2.1 Final > > We need to have not only an author instance in our dropable .war file, but a > public instance too. This solves many issues on our mailinglist > Or in another case we need a clean description what to do to create a public > instance -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia.info/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira ---------------------------------------------------------------- for list details see http://www.magnolia.info/en/magnolia/developer.html ----------------------------------------------------------------
