Re: Managining Maven Plugins and dependencues

Jose Gonzalez Gomez Wed, 29 Sep 2004 00:56:05 -0700


   So summing up, is the following what I am supposed to do?

  1. Uninstall the offending plugin (maven plugin:uninstall?)
  2. Create correct dependency in project.xml (see another mail in this
     thread)
  3. Use plugin in command line or maven.xml

OR

  1. Wait for maven 1.1
  2. Install maven 1.1
  3. Create correct dependency in project.xml (see another mail in this
     thread)
  4. Use plugin in command line or maven.xml

I guess in the first case the plugin will only be available for the user building the project with the stated dependency, won't it? This may cause weird behaviour in multi-user environments, as I'm talking about the hibernate plugin, that is included in the maven distribution. I mean, other user may expect that plugin to be installed.

   Best regards
   Jose

Carlos Sanchez wrote:

Hi,
The plugin is extracted to ~/.maven/cache, not MAVEN_HOME/plugins.
Currently there's a bug when you have a dependency of a plugin already
installed. http://jira.codehaus.org/browse/MAVEN-1427
Regards
Carlos Sanchez
A Coru�a, Spain
http://www.jroller.com/page/carlossg/Weblog
Oness Project
http://oness.sourceforge.net
-----Original Message----- From: Jose Gonzalez Gomez [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 29, 2004 12:57 AM To: Maven Users List Subject: Re: Managining Maven Plugins and dependencues
   Arnaud,
I tried this, but it doesn't work... the plugin is downloaded, but it isn't used in the build process (I guess maven is supposed to use it, isn't it?). I'm running maven in a linux environment, as a normal user, without write permissions on the plugin directory of maven, should I have write permissions for this to work?
   Best regards
   Jose
Arnaud HERITIER wrote:
You can define a plugin dependency in your POM.
For example :
<dependency>
    <groupId>statcvs</groupId>
    <artifactId>maven-statcvs-plugin</artifactId>
    <version>2.5</version>
    <type>plugin</type>
    <url>http://statcvs-xml.berlios.de/maven-plugin/</url>
    <properties/>
</dependency>
Arnaud
On Tue, 28 Sep 2004 09:25:13 -0400, Helck, Christopher
<[EMAIL PROTECTED]> wrote:
I don't understand how maven plugins are managed. Suppose
I'm working

on a project and decide that I need to upgrade a plugin. So, I grap the latest version of a plugin and install it. Do other

people on my

team also need to install the plugin? Since the project.xml

does not
list plugin dependencies, how does maven know which one to use?
Regards,
C. Helck
The information contained in this e-mail is confidential.
This e-mail is intended only for the stated addressee. If you are not an addressee, you must not disclose, copy, circulate or in any other way use or rely on the information contained in this e-mail. if you have received this e-mail in error, please inform us immediately and delete it and all copies from your system.
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
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]

Re: Managining Maven Plugins and dependencues

Reply via email to