On Wed, 16 Mar 2005 19:33:26 -0700, Chad Woolley <[EMAIL PROTECTED]> wrote: > I got this working, but I don't know how :(. > > Apparently, I had a "0.5" version cached somewhere, and that was > screwing me up. This obviously resulted from me previously building and > installing the HEAD version of the plugin (which has been incremented to > 0.5). > > However, what I don't understand is where it was! I explicitly deleted: > /maven/plugins/maven-emma-plugin-0.x.jar (not sure if this was 0.4 or 0.5) > ~/.maven/repository/emma/plugins > ~/.maven/cache/maven-emma-plugin-0.x
I'm not an expert in this but in the cache directory (~/.maven/cache) there are some files (especially plugins.cache, I believe) in which information about cached plugins is stored. Probably if you deleted entries concerning emma plugin you wouldn't get the following message but then again it's probably intended - it shows you that the plugin referenced in cache no longer exist so the reference is invalidated. And that's what you want, right? -- Lukasz Bajorski tel. +48 508 609 414 GG: 3318146 www.jroller.com/page/benjie > > ... And I still got this message on the next build: > > __ __ > | \/ |__ _Apache__ ___ > | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ > |_| |_\__,_|\_/\___|_||_| v. 1.0.2 > > plugin maven-emma-plugin-0.5 is cached (dynatag dep) but no longer present > Cache invalidated due to out of date plugins > Attempting to download vmstest-SNAPSHOT.jar. > > Where was the 0.5 version being cached?!? > > Anyway, after the 0.5 references disappeared, it worked fine. > > Also, I did NOT need a reference to the plugin in my POM with the > type=plugin (I never did for other plugins). Was this my real problem? > Is this the preferred solution for automatically > downloading/installing plugins instead of my updateplugins goal? It > seemed kind of hackish. > > If I have time to dig in and get more info, I'll post back here :) > > Thanks for the help, > Chad > > Kenney Westerhof <[EMAIL PROTECTED]> wrote: > >> > >>Hi Chad, > >> > >> > >>Seems I made a mistake - plugin:install is indeed intended to be used from > >>within the plugin project itself. > >> > >>I think something else is the problem.. When you just specify > >>a dependency of type 'plugin' in your project.xml, it should automatically > >>install it. Maybe it's only available in the second run, but it works. > >>I've tested it myself: > >> > >>$ cat maven.xml > >><project xmlns:j="jelly:core"> > >> <goal name="updateplugins"> > >> <j:set var="type" value="plugin"/> > >> <j:set var="groupId" value="emma"/> > >> <j:set var="artifactId" value="maven-emma-plugin"/> > >> <j:set var="version" value="0.4"/> > >> <attainGoal name="plugin:download"/> > >> </goal> > >></project> > >> > >>$ maven -Dmaven.repo.remote=http://www.neonics.com/maven/ > >># (my 'local remote' repository) > >> > >>build:start: > >> > >>updateplugins: > >>plugin:download-artifact: > >> [echo] repo is 'http://www.neonics.com/maven/' > >> [echo] trying to download > >>http://www.neonics.com/maven//emma/plugins/maven-emma-plugin-0.4.jar > >>9K downloaded > >> > >>plugin:download: > >> [delete] /home/forge/.maven/plugins not found. > >> [copy] Copying 1 file to /home/forge/local/maven/plugins > >>BUILD SUCCESSFUL > >>Total time: 3 seconds > >>Finished at: Tue Mar 15 17:57:01 CET 2005 > >> > >> > >>$ maven -g |grep emma > >>[emma] ( NO DEFAULT GOAL ) > >> emma ........................... Generate test coverage reports with > >>EMMA. > >>[maven-emma-plugin] ( NO DEFAULT GOAL ) > >> > >><snip/> > >> > >> > >>Do you get similar output? > >>My guess is that you have some file permission issue on your repository. > >>Please check if > >>${maven.local.home}/repository/emma/plugins/maven-emma-plugin-0.4.jar > >>exists.. (it is also installed in ${maven.home}/plugins/emma/.....) > > --------------------------------------------------------------------- > 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]
