Hi Yann,

this does not work - I read on a post from Brett that these options work
only for the plugin registry  and the plugin registry is not activated by
default in m2.
And even when I run the command for the first time today, Maven didn't try
any update, so that's why I don't understand what's happening.

Also I must admit that I don't always understand all the differences
between the <pluginManagement> and <plugins> elements of the <build>
section...

Best Regards / Cordialement,
Fabrice BELLINGARD
DINQ/DSIN/INSI/EATE/IDVS/AIDV
(+33) (01 61) 45 15 91  -  [EMAIL PROTECTED]


                                                                       
             Yann Le Du                                                
             <[EMAIL PROTECTED]                                          
             com>                                                     Pour
                                       Maven Users List                
             03/11/2005 11:48          <users@maven.apache.org>        
                                                                        cc
                                                                       
                 Veuillez                                            Objet
                répondre à             RE: Updating a plugin with  
             Maven Users List          <pluginManagement>?             
             <[EMAIL PROTECTED]                                          
                 che.org>                                              
                                                                       
                                                                       
                                                                       
                                                                       




Hi Fabrice,

I believe you must use -cpu or -U to force the update, or else updates are
checked once a day.

Regards,
Yann

--- [EMAIL PROTECTED] a écrit :

>
>
>
>
> Hi,
>
> I've just seen that version 2.0 of the surefire plugin has been released,
> so of course I decided to use it. In my pom, I specified the following
> lines:
>       <build>
>             ...
>             <pluginManagement>
>                   <plugins>
>                         ...
>                         <plugin>
>                               <groupId>org.apache.maven.plugins</groupId>
>                               <artifactId>maven-surefire-plugin
> </artifactId>
>                               <version>2.0</version>
>                         </plugin>
>                   </plugins>
>             </pluginManagement>
>       </build>
>
> However, when I run "mvn test", Maven didn't try to download version 2.0
> and used the local version 2.0-beta-1. Shouldn't Maven try to update the
> plugin to the version I specified?
> If I specify the plugin (version 2.0) in the <plugins> element of
<build>,
> then the last version gets downloaded and used, but the
> "maven-metadata-central.xml" file is not updated - and therefore
2.0-beta-1
> will stay as the default version to use for the plugin. I have to delete
> "maven-metadata-central.xml" to force Maven to update the plugin...
>
> Am I missing something?
>
> Thanks in advance for your help!
>
>
> Best Regards / Cordialement,
> Fabrice BELLINGARD
> DINQ/DSIN/INSI/EATE/IDVS/AIDV
> (+33) (01 61) 45 15 91  -  [EMAIL PROTECTED]
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>







___________________________________________________________________________

Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger
Téléchargez cette version sur http://fr.messenger.yahoo.com

---------------------------------------------------------------------
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]

Reply via email to