The Maven 2 Integration for Eclipse may help - it allows you to easily
add new dependencies to your pom.xml:

http://m2eclipse.codehaus.org/

Flash demo: http://m2eclipse.codehaus.org/Maven_2.0_Plugin_for_Eclipse.html

Matt

On 1/25/07, Michael Mehrle <[EMAIL PROTECTED]> wrote:
Excellent tutorial - I actually didn't know that you could use maven to set
your maven repo. Anyway, I ran mvn install eclipse:eclipse and got both
projects this time - good stuff, thanks.

Actually, I do have something to add to your little tutorial. We all make
small mods to our projects (misc paths and in case of MyEclipse
JSTL/Hibernate/Spring support, etc.) and when we add new dependencies to our
pom we often don't want to recreate a project. Usually building a new
project screws things up. Adding the new resources from your M2_REPO is easy
in Eclipse but not exactly intuitive:

- First, add the new dependency to your POM
- On the command line run 'mvn compile' or 'mvn install' - make sure you
were able to download the jar.
- In Eclipse go to Project->Properties
- Select 'Java Build Path'
- Click 'Add Variable'
- In the new panel select 'M2_REPO'
- Click on 'Extend...'
- Navigate to the version folder and jar file that you want to add
- Double click the jar file
- Cancel all open dialogs.

Done :-)

If you guys know of an easier way to 'properly' add your jar files to a
maven/Eclipse project let me know.

Michael


----- Original Message -----
From: "Matt Raible" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Wednesday, January 24, 2007 8:31 PM
Subject: Re: [appfuse-user] Creating eclipse project for appfuse 2.0


> On 1/24/07, Matt Raible <[EMAIL PROTECTED]> wrote:
>> On 1/24/07, molecool <[EMAIL PROTECTED]> wrote:
>> >
>> > Usually I just run 'mvn eclipse:eclipse' and it creates a full-fledged
>> > project including all the sub modules for me. For some reason I was
>> > only
>> > able to create the core project, which is strange.
>>
>> AFAICT, you need to run "mvn" from the top level before you run "mvn
>> eclipse:eclipse". This is because Eclipse tries to find the core
>> module for the web module and it doesn't exist yet.
>
> FYI... I tried to document this in step #3 of the Eclipse Guide.  Let
> me know if I can improve the wording at all.
>
> http://appfuse.org/display/APF/Eclipse
>
> Matt
>
>>
>> Matt
>>
>> >
>> > The modules seem to be properly configured in the root pom, so this is
>> > strange.... anyone?
>> >
>> > Michael
>> > --
>> > View this message in context:
>> > 
http://www.nabble.com/Creating-eclipse-project-for-appfuse-2.0-tf3096064s2369.html#a8595543
>> > Sent from the AppFuse - User mailing list archive at Nabble.com.
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: [EMAIL PROTECTED]
>> > For additional commands, e-mail: [EMAIL PROTECTED]
>> >
>> >
>>
>>
>> --
>> http://raibledesigns.com
>>
>
>
> --
> http://raibledesigns.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]




--
http://raibledesigns.com

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to