Brett Porter <[EMAIL PROTECTED]> wrote on 12/09/2003 09:07:04 AM: [snip] > To obtain a plugin, you can give a dependency, or use the plugin:download > goal. Either way, it gets installed into MAVEN_HOME (this is a problem at > the moment - we're back to the beta-9 and before days of not having a read > only distribution...) We could remove the installation into MAVEN_HOME as part of the plugin processing. No big deal there.
> How do I see it long term? > > For the downloading and use of plugins - exactly how it is now is fine, > however I think that we should replace $MAVEN_HOME/plugins with > $MAVEN_REPO_LOCAL/maven/plugins as the central storage point. More > consistent, less duplication. What about plugins from other parties, e.g. the maven-plugins project. They'd come from $MAVEN_REPO_LOCAL/maven-plugins/plugins I'd much rather the list of installed plugins be in a different directory to the repo. > Decoupling core plugins is fine, but we -must- a convenient distribution of > them and their dependencies. Not everyone has broadband internet, and there > is nothing more annoying than downloading a program, getting offline, and > not being able to use it because you need to download more stuff to even > compile a single class. Big +1. > I think what is core is fairly obvious. Off the top of my head clean, jar, > war, ear, plugin, site, dist (probably more) and anything required to run > them - java, test, junitreport, xdoc, all the standard reports, artifact, -- dIon Gillard, Multitask Consulting Blog: http://blogs.codehaus.org/people/dion/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
