Back under version 3.0 merlin controlled the repository. Then can 3.2 and the repository controlled merlin. The upside was a much improved embedding model and consistency across off of the current embedded merlin implementations.
However - there is downside that has been introduced - and the purpose of this email is address that issue.
Under Merlin 3.0 we had the following:
MERLIN_HOME
Under 3.2 we have:
AVALON_HOME (used by the repository package) MERLIN_HOME (used by merlin)
In addition, the 3.2 version introduced the potential for the aggregation of properties from multiple property files - and the result of this is the following property file:
avalon.properties merlin.properties
What I think we should do is to abandon MERLIN_HOME and merlin.properties and instead consolidate under AVALON_HOME and avalon.properties. This will make things a lot more consistent because we will be able to:
* consolidate property handling
* facilitate command line handler extension
(i.e. repo cli would be a strict subset of merlin cli)
* keep installation as simple as possible
* and simplify site configurationSound ok?
Stephen.
--
|------------------------------------------------| | Magic by Merlin | | Production by Avalon | | | | http://avalon.apache.org/merlin | | http://dpml.net/merlin/distributions/latest | |------------------------------------------------|
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
