Regarding why Maven tries to use 2.8-SNAPSHOT and isn't successful I'm somewhat puzzled. You didn't post the full error output, so I can't say for sure. Also, I need to know more about your Artifactory setup to spot the problem.
/Anders On Wed, Feb 3, 2010 at 16:59, Rick R <[email protected]> wrote: > On Wed, Feb 3, 2010 at 3:49 AM, Anders Hammar <[email protected]> wrote: > > > Ok, first I would like to point you at some Maven books. They are great > to > > get the basics: > > http://books.sonatype.com > > > > Yes I need to read that more thoroughly. I did look through it once and > tried to refer to even in this case, but it was one of those things where I > didn't even really know where to look since wasn't sure of the exact cause. > > > > Try this on the command line: > > mvn org.apache.maven.plugins:maven-eclipse-plugin:2.7:eclipse > > > > > Perfect! Yes that worked! > > > > By adding the > > following xml section to your project, you configure Maven to use v2.7 of > > the plugin (but only when executed for this project or a project that > > inherits from this): > > <build> > > <pluginManagement> > > <plugins> > > <plugin> > > <groupId>org.apache.maven.plugins</groupId> > > <artifactId>maven-eclipse-plugin</artifactId> > > <version>2.7</version> > > </plugin> > > </plugins> > > </pluginManagement> > > </build> > > > > > Perfect also! (This is now what I've added to my project's pom so this > issue > doesn't keep happening.) > > > > > The schema for pom.xml is found here: > > http://maven.apache.org/maven-v4_0_0.xsd > > > > > Ok thanks. Although even looking at that schema it makes it difficult for > me > as a newb to look at and say "ok from that schema create the > pluginManagement definition as you did above. > > *So the only last question I have 'Where did things go wrong in my attempt > to use mvn eclipse:eclipse?' Even if I run just a simple archetype jar (no > dependency on my company repo) and then run mvn eclipse:eclipse without > declaring the version like you mentioned I'll get the issue, so I guess > it's > something wrong with the eclipse 2.8 snapshot not being in the public repo? > I would think that if I went to the maven eclipse plugin info > http://maven.apache.org/plugins/maven-eclipse-plugin/eclipse-mojo.htmlthat > it would mention the help you gave me (declaring the version in my pom or > settings) since I would think others would run into the same issues as > myself (or else I guess everyone is just more up-to-speed and instantly > knows what to do.:) > > > > > As a last point I would like you to talk to your local Maven people as > > well. > > They know > > your local environment and should be able to help you. I can't solve > > problems in your local environment. > > > > Ha, I know you can't. But the guy setting the local repo up was newb also. > We're trying to push for maven to be used here so learning on the fly. > > Thanks again for your help. I did learn a LOT through this whole ordeal. >
