Re: Managining Maven Plugins and dependencues

[Jose Gonzalez Gomez]

   I have a fresh install of maven, with maven-hibernate-plugin-1.1, 
with the following in project.xml:

       <dependency>
           <groupId>maven</groupId>
           <artifactId>maven-hibernate-plugin</artifactId>
           <version>1.2</version>
           <type>plugin</type>
       </dependency>
   and the following in maven.xml:
   <goal name="myProject:domain.schema-creation">
       <attainGoal name="hibernate:schema-export"/>
   </goal>
   This downloads maven-hibernate-plugin-1.2, but keeps using 
maven-hibernate-plugin-1.1 unless I install it using maven 
plugin:download. Am I missing anything?

   Best regards
   Jose
Arnaud HERITIER wrote:
You also need to define how the plugin is used.
For example if it is a report you need to add it in your pom:
<report>maven-statcvs-plugin</report>
Otherwise you can call it in a specific goal (with attainGoal).
Arnaud
 

-----Message d'origine-----
De=A0: Jose Gonzalez Gomez [mailto:[EMAIL PROTECTED]
Envoy=E9=A0: mercredi 29 septembre 2004 00:57
=C0=A0: Maven Users List
Objet=A0: Re: Managining Maven Plugins and dependencues
=20
=20
   Arnaud,
=20
   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?
=20
   Best regards
   Jose
=20
Arnaud HERITIER wrote:
=20
   

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]

     

=20
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
=20
=20
=20
#=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D gPopper Menu =
   

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D#
 

Delete from Gmail inbox:   mailto:del|[EMAIL PROTECTED]
Mark message as unread:    mailto:unr|[EMAIL PROTECTED]
Mark message as read:      mailto:rea|[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]