so taking the example of the java plugin
groupId (from parent project.xml) is maven id is maven-java-plugin currentVersion 1.3
so I should expect to see at ibiblio
http://www.ibiblio.org/maven/maven/plugins/maven-java-plugin-1.3.jar and many others, but I only see a few. Have only some of the plugins been moved over to this new structure?
Jason van Zyl wrote:
On Tue, 2003-09-30 at 09:50, Nathan Coast wrote:
what's the stucture for plugins in a remote repository?
<groupId>/plugins/<artifactId>-version.jar
Yes, the plugins are now another artifact type. So you might have:
<dependency> <groupId>foo</groupId> <artifactId>bar-plugin</artifactId> <type>plugin</type> <version>1.0</version> </dependency>
You get <repo>/foo/plugins/bar-plugin-1.0.jar
can you define which remote repository you wish to download a specific plugin from, or can the remote repositories only be set by setting the
maven.repo.remote property?
Yes, should work just like any other artifact.
cheers Nathan
Jason van Zyl wrote:
On Mon, 2003-09-29 at 20:12, Brett Porter wrote:
Brett,
Could you give me a quick rundown of how to download a plugin and how the mechanism works. I will look at the code for certain but I just want to push in a little bit of doco now with all the plugins separated.
maven plugin:download -DartifactId=maven-dbunit-plugin -DgroupId=maven -Dversion=1.1-SNAPSHOT
Downloads, installs to $MAVEN_HOME/plugins, deletes old versions in $MAVEN_HOME_LOCAL/plugins
If you declare a plugin as a dependency will an install be attempted?
Yes, same as above but doesn't delete other versions. For this one, just a standard dependency element is needed with <type>plugin</type> given.
Awesome, thanks!
Cheers, Brett
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
