mvn -U i believe should force a check for updates. but depending on how your repositories are configured, you might not get all available updates (ie snapshots) esp if Central/ibiblio for some reason does not have the most recent version of a particular dependency ie its out of sync with another Apache repo etc.
Wayne On 4/1/06, Mark Hobson <[EMAIL PROTECTED]> wrote: > [sending back to users list] > > On 01/04/06, gdub <[EMAIL PROTECTED]> wrote: > > I see. Thank you Mark. So, bottom line, I'm > > SOL for now. I hope a solution is implemented > > soon. This problem precludes me from upgrading > > Maven on my primary workstation. > > Yep, I think this situation hinders more people than MECLIPSE-37 aimed > to help. I'd like to see a fix-for version attached to this issue. > > > Meanwhile, my workaround is to manually > > create create standard layouts with the > > latest POMs for each module I want to > > work on out-of-office, run the eclipse target, > > then copy the sources over--not ideal but > > workable for two or three modules needed over > > a weekend. > > Yes, my workaround is to manually move the files from under the source > tree to a temporary location, mvn eclipse:eclipse, and then move them > back again. Far from ideal.. > > > Since it is a plug-in thing, is there a way > > to generally tell my Maven installation to > > use an earlier version of the plug-in for > > all projects? > > There is - you can simply add a <plugin> block to the <build> block in > your pom, and then specify an explicit <version> tag. > > > Also, why doesn't my office > > machine download the latest plug-in (I don't > > specify any eclipse plug-in configuration in > > my POMs so projects shouldn't be tied to a > > particular plug-in version, right?). It's good > > that it doesn't but it would be nice to > > understand why. > > This is a good point. I remember back in the day m2 used to prompt > the user when newer plugin versions were available. I assumed this > was still the case, but I've just checked by home machine and I'm > using eclipse plugin 2.0 rather than 2.1 that I have at work, which > explains a whole load of eclipse issues.. > > Does anyone know what the current status is for updating m2 plugins? > I've tried the -cpu and -up cli flags but to no avail. Also, it'd be > great to have a cli flag to list the installed plugins and their > versions. > > Cheers, > > Mark > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
