Dion:


I know this is really wimpy, but I have a beta-10 release
running on my machine which is the release that is documeted
under the respective Avalon products.  I would prefer to
maintain my environment relative to beta-10 for the moment as
I'm dealing with other user issues relative to that context.

I have just uploaded the plugin jar files to ibiblio.  If
anyone could confirm that the install procedure is functional
it would save me a lot of deinstall/test/reinstall hasles.  The
plgins in question include:

avalon-meta/avalon-meta-plugin-1.1.jar
merlin/merlin-plugin-1.0.jar

Cheers, Steve.


[EMAIL PROTECTED] wrote:


Stephen McConnell <[EMAIL PROTECTED]> wrote on 26/09/2003 02:17:34 PM:



Jason:

Just a point of confirmation - Avalon have two Maven plugins, one
dealing with automated generation of component meta-info and the second
supporting simulated component deployment.  Currently these plugins are
located in the Avalon CVS and binary downloads are maintained on the
Apache mirror, the DPML, and the Maven repository on Ibiblio.

My understanding is that Maven RC1/beta-11 will include a plugin
installer. Can you confirm if there is anything we (Avalon) need to
do in order to ensure that Avalon plugins are easily integrated into
the Maven environment under the pending release.



Test against RC1-SNAPSHOT.


In particular, remove the current plugins from your $MAVEN_HOME/plugins directory, and the $MAVEN_HOME_LOCAL/plugins directory, and use

maven -D..... plugin:download

to test it out.

It expects the plugins to be deployed to ${maven.repo.remote}/<groupId>/plugins/<artifactId>-<version>.jar

let us know if we can help.
--
dIon Gillard, Multitask Consulting
Blog:      http://blogs.codehaus.org/people/dion/




--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]





--


Stephen J. McConnell
mailto:[EMAIL PROTECTED]




--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to