avalon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stephen McConnell <mcconn...@apache.org>
Subject [merlin] meta migration strategy
Date Tue, 15 Jul 2003 23:19:47 GMT

I've completed the re-shuffling of the Merlin Meta content into a 
separate sandbox project and now the Merlin build has been restructured 
to use Avalon Meta instead of Merlin Meta (at the meta-info level).  
There is a direct and immediate impact of this change ...

* your existing @avalon.meta.* tags are broken.  *

To correct this situation, you need to:

   1. replace @avalon.meta.* with @avalon.*
   2. replace the following definitions

Old style:

   @avalon.meta.version 1.0
   @avalon.meta.name fred
   @avalon.meta.lifestyle singleton

New style:

   @avalon.type version="1.0" name="fred" lifestyle="singleton"

Installation Notes:
Finally, you will need to install the avalon meta plugin into you Maven 
plugin directory.  If you have already checked out the sandbox/meta 
package, then the plugin will be automatically installed as a result of 
invoking maven.  If not, you can download and install the latest version 
of the plugin from this link:


The file to download is:


To use the plugin inside Maven, you should declare a pre or postGoal 
inside you maven.xml file such as the following:

    <postGoal name="java:compile">
      <attainGoal name="avalon:meta"/>

This will result in the automated generation of meta-info descriptors 
for your components following a successful compilation.

Cheers, Steve.


Stephen J. McConnell

Sent via James running under Merlin as an NT service.

To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org

View raw message