Actually it sounds like you just want dependency:resolve which does exactly what you ask. This one is released in the mojo version: org.codehaus.mojo:dependency-maven-plugin:1.0
-----Original Message----- From: John Casey [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 11, 2006 1:19 PM To: Maven Developers List Subject: Re: RE: manually managing external dependencies in maven 2 You might be able to use the "go-offline" mojo in the maven-dependency-plugin, which is still in snapshots before its next release IIRC. You would have to add: <pluginRepositories> <pluginRepository> <id>apache.snapshots</id> <url>http://people.apache.org/repo/m2-snapshot-repository</url> </pluginRepository> </pluginRepositories> Then, you could call/bind the go-offline mojo to download the new dependencies to the local repository. You could also use "@requiresDependencyResolution test" in the class-level javadocs for your own mojo, which would make it download new dependencies before running...that's probably more elegant, in fact. Is that what you wanted to do? -john On 10/11/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Hello, > > A simple solution would be to run "mvn -U" (i.e. run a CLI command) > which will update all dependencies in the repository. > > There should also be a goal which just downloads all dependencies > without compiling. > > But a clean way to browse the dependency tree (including "update > this") from Java code would be nice, too. Don't forget to post here if > you find a solution! > > Regards, > > -- > Aaron Digulla > > fogwolf <[EMAIL PROTECTED]> schrieb am 11.10.2006 16:39:43: > > > > > Thanks for the suggestion. This Eclipse plugin looks good & does a > > lot > of > > what the plugin I've written does, but I'd still like to know how to > control > > the download of external dependencies, since my plugin does more > > custom things I've written based on my development environment here. > > Could > anyone > > help with that? > > > > Thanks! > > > > > > Manuel Ledesma wrote: > > > > > > Look at this page, it might help u > > > > > > http://maven.apache.org/eclipse-plugin.html > > > > > > -----Original Message----- > > > From: fogwolf [mailto:[EMAIL PROTECTED] > > > Sent: Tuesday, October 10, 2006 5:24 PM > > > To: [email protected] > > > Subject: manually managing external dependencies in maven 2 > > > > > > > > > Hi, > > > > > > I'm using Maven 2 for managing my Java projects in Eclipse & am > wondering > > > how I can manually get Maven to check for any new external > dependencies in > > > my pom.xml & automatically download them to the local repository > without > > > having to call "maven compile". I have a Java Mojo that I run > > > after > adding > > > dependencies to a project's pom which updates Eclipse's .classpath > file > > > with > > > any added dependencies but then Eclipse flags the project with an > error if > > > it's not a dependency already stored in my local repository. How > > > could > I > > > add > > > a step to download any new dependencies from this plugin I've written? > > > > > > Thanks! > > > -- > > > View this message in context: > > > > > http://www.nabble.com/manually-managing-external-dependencies-in-maven > -2-tf2 > > > 419629.html#a6745832 > > > Sent from the Maven Developers mailing list archive at Nabble.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] > > > > > > > > > > > > > -- > > View this message in context: http://www.nabble.com/manually- > > managing-external-dependencies-in-maven-2-tf2419629.html#a6757750 > > Sent from the Maven Developers mailing list archive at Nabble.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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
