Return-Path: 
 <users-return-19636-apmail-maven-users-archive=maven.apache.org@maven.apache.org>
Delivered-To: apmail-maven-users-archive@www.apache.org
Received: (qmail 30281 invoked from network); 29 Oct 2004 06:53:12 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur-2.apache.org with SMTP; 29 Oct 2004 06:53:12 -0000
Received: (qmail 2571 invoked by uid 500); 29 Oct 2004 06:52:56 -0000
Delivered-To: apmail-maven-users-archive@maven.apache.org
Received: (qmail 2467 invoked by uid 500); 29 Oct 2004 06:52:56 -0000
Mailing-List: contact users-help@maven.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:users-unsubscribe@maven.apache.org>
List-Subscribe: <mailto:users-subscribe@maven.apache.org>
List-Help: <mailto:users-help@maven.apache.org>
List-Post: <mailto:users@maven.apache.org>
List-Id: "Maven Users List" <users.maven.apache.org>
Reply-To: "Maven Users List" <users@maven.apache.org>
Delivered-To: mailing list users@maven.apache.org
Received: (qmail 2431 invoked by uid 99); 29 Oct 2004 06:52:55 -0000
X-ASF-Spam-Status: No, hits=0.0 required=10.0
	tests=RCVD_BY_IP,SPF_HELO_PASS,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (hermes.apache.org: domain of bgidley@gmail.com designates
 64.233.184.203 as permitted sender)
Received: from [64.233.184.203] (HELO wproxy.gmail.com) (64.233.184.203)
  by apache.org (qpsmtpd/0.28) with ESMTP; Thu, 28 Oct 2004 23:52:54 -0700
Received: by wproxy.gmail.com with SMTP id 69so1308432wri
        for <users@maven.apache.org>; Thu, 28 Oct 2004 23:52:45 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references;
        b=MnBlTTNTnT9d5ywsYpL3LZs96CJlNcvtjtOJk5mjxDlxtWtptqfb/3y8MOGaWLKiEebGtm1Bp8QA1+uUlP+yt73Ls15raZO4yRfcNAa0gPoCYOjbAKprJi/YhsM0B4qtuhfmTyj+V6f12+ZGYf9smh4+mzgGiW9VesDVrM0aVj4=
Received: by 10.38.81.16 with SMTP id e16mr1733933rnb;
        Thu, 28 Oct 2004 23:52:45 -0700 (PDT)
Received: by 10.38.88.14 with HTTP; Thu, 28 Oct 2004 23:52:45 -0700 (PDT)
Message-ID: <7a04bff104102823525c1e111b@mail.gmail.com>
Date: Fri, 29 Oct 2004 07:52:45 +0100
From: Ben Gidley <bgidley@gmail.com>
Reply-To: ben.gidley@anite.com
To: Maven Users List <users@maven.apache.org>,
	Brett Porter <brett.porter@gmail.com>
Subject: Re: Need help with upgrading a plugin
In-Reply-To: <9e3862d8041028133561e1d4a7@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
References: <CB281A6E81992343A25EF31D86BD13B61E6BA0@usnjexch1.ebs.com>
	 <-4037343840201372208@unknownmsgid>
	 <9e3862d8041028133561e1d4a7@mail.gmail.com>
X-Virus-Checked: Checked
X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N

As a quick and dirty fix I add the following goal to the maven.xml of
our projects and tell people to run it if they get plugin problems

<goal name="antelope:upgradePlugins">
		<j:forEach var="dep" items="${pom.dependencies}">
				<j:if test="${dep.type =='plugin'}">
					<maven:get plugin="${dep.artifactId}" property="plugin" 
						var="plugin" />
					
						<ant:echo> 
###################################################################### 
Fetching ${dep.artifactId} Plugin You may have to run your goal again 
###################################################################### 
				</ant:echo>
						<j:set var="groupId" value="${dep.groupId}"/>
						<j:set var="artifactId" value="${dep.artifactId}"/>
						<j:set var="version" value="${dep.version}"/>
						<attainGoal name="plugin:download"/>
					</j:if>

		</j:forEach>		
	</goal>


On Fri, 29 Oct 2004 06:35:28 +1000, Brett Porter <brett.porter@gmail.com> wrote:
> I would suggest that the plugin dependency will work, but only if you
> uninstall the original.
> 
> The mechanism has problems when two different versions of on plugin are loaded.
> 
> 
> 
> 
> On Thu, 28 Oct 2004 09:34:35 -0700, Charles Daniels <cjd4@yahoo.com> wrote:
> > This is a known issue.  Adding a plugin as a dependency doesn't quite
> > work as you might expect.  In fact, in my experience, adding a plugin as
> > a dependency can cause other little problems.  I suggest you remove the
> > plugin as a dependency and manually download the plugin via the
> > plugin:download goal.  You should probably also manually delete the
> > plugin jar files from your MAVEN_HOME/plugins directory prior to running
> > plugin:download.  If you simply stick to using plugin:download whenever
> > you wish to upgrade to a newer plugin version, your older version will
> > automatically be removed.
> >
> >
> >
> > > -----Original Message-----
> > > From: Helck, Christopher [mailto:chelck@ebs.com]
> > > Sent: Thursday, October 28, 2004 9:27 AM
> > > To: Maven Users List
> > > Subject: Need help with upgrading a plugin
> > >
> > > Note: This is a repost/rephrasing of an ealier question I sent out.
> > >
> > > Previous posts have led me to believe that I can upgrade a plugin by
> > > specifying the plugin in my POM. I've tried this and it
> > > partially works.
> > > The new plugin is downloaded and installed in my local repository, but
> > > Maven does not invoke the updated plugin. In this case I'm
> > > trying to use
> > > the latest version of the JXR plugin.
> > >
> > > Here's the relevent parts of my POM:
> > >
> > >   <dependencies>
> > >     <dependency>
> > >       <groupId>maven</groupId>
> > >       <artifactId>maven-jxr-plugin</artifactId>
> > >       <version>1.4.2</version>
> > >       <type>plugin</type>
> > >     </dependency>
> > >     ...
> > >   </dependencies>
> > >
> > >   <reports>
> > >     <report>maven-jxr-plugin</report>
> > >     ...
> > >   </reports>
> > >
> > >
> > > When I run "maven site" and it tries to build the java cross
> > > reference I
> > > get the error:
> > >
> > > BUILD FAILED
> > > File.... /home/chelck/.maven/cache/maven-jxr-plugin-1.4.1/plugin.jelly
> > >
> > > Version 1.4.2 of jxr is downloaded and in my cache next to
> > > 1.4.1. So why
> > > isn't 1.4.2 being used?
> > >
> > > Any ideas? Thanks,
> > >
> > > -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.
> > >
> > > EBS Dealing Resources International Limited.  Registered
> > > address:  55-56 Lincoln's Inn Fields, London WC2A 3LJ, United
> > > Kingdom. Registered number 2669861.
> > >
> > > EBS Dealing Resources, Inc, registered in Delaware. Address:
> > > 535 Madison Avenue, 24th Floor, New York, NY 10022, USA, and
> > > One upper Pond road, Building F - Floor 3, Parsippany, NJ 07054, USA.
> > >
> > > EBS Dealing Resources Japan Limited, a Japanese Corporation.
> > > Address: Asteer Kayabacho Bldg, 6th Floor, 1-6-1, Shinkawa,
> > > Chuo-Ku,  Tokyo 104-0033, Japan.
> > >
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
> 
> 


-- 
Thanks

Ben

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org