Based on a bunch of updates in the last week - the build procedures for the following packages are now all linked to a common version repository:
avalon-framework avalon-logkit avalon-logging avalon-repository avalon-meta avalon-util merlin
Button line - this is *fantastic* because it eliminates the single biggest administrative overhead related to the merlin codebase management - namely the synchronization of version information.
However - before current the binary drop - there are two problems that the new version handling approach has introduced:
* tutorial content packaging
the tutorial sources are packaged with maven project files
however the project files have relative ent references to the
avalon/versioning directory which will not exist relative to a
packaged source distribution - solution is to move the tutorials
up to the same level as the versioning directory and including the
versioning data with the source distribution* plugins
the merlin distribution leverages three plugins (util, repo and
merlin - however, maven packages the project.xml file into the
jar file that is the plugin - and when including ent references in
the project.xml - we end up with a plugin that is looking for an
relative file (which will break deployment) - i.e. need to figure
out how to resolve this before cutting a 3.3 binary (hopefully
something will be posted this weekend)Cheers, 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]
