That's a link to one approach. Another approach is to enable the Maven2 nature for your project, which should make it use the dependencies in your pom.xml file without needing to regenerate the .classpath file every time you add a dependency.
-K -- Kathryn Huxtable Middleware Architect Core Middleware Information Technology, a division of Information Services The University of Kansas On 2/27/06 6:41 PM, "KC Baltz" <[EMAIL PROTECTED]> wrote: > http://maven.apache.org/guides/mini/guide-ide-eclipse.html > > > > -----Original Message----- > From: Ashish Srivastava [mailto:[EMAIL PROTECTED] > Sent: Monday, February 27, 2006 4:24 PM > To: users@maven.apache.org > Subject: import statements in Eclipse and maven2 > > > Hi, > I am using maven2 plugin on Eclipse and working on a > project which uses maven2. In the eclipse' Java editor > all the import statements (and the classes) are > underlined red as if it could not find the jars. How > can I configure the project to read the pom.xml and > work out all the dependencies? > > -Ashish > > __________________________________________________ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam protection around > http://mail.yahoo.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]
