Re: MetaClass

[email protected] wrote:
> Hiya,
> 
> Has anyone had any problems with the latest version of MetaClass? Over the
> next week or so I would like to cut a release for it and upgrade it out of
> the sandbox. I was thinking that it would be best to migrate it to a
> "top-level" project with separate www/cvs presence. My main reason for this
> is that it is not really a "component" and nor is it specific to container
> development so thus it makes sense to move it out. 
> 
> Thoughts?

Yep - I agree.
Also - while at it can we settle on a naming convention for the maven 
plugins?

The current convention is that maven-xxxx-plugin is the plugin for maven
of component/application xxxx.
Adopting this, the metaclass plugin for maven should be called
maven-metaclass-plugin.

We can leave metaclass-yyyy-plugin for any plugin that metaclass may 
support.

Make sense?

Cheers