Hi Cameron,
My workspace ends up having one eclipse project per Geronimo module. The projects build paths are configured to build against dependent project outputs. Yes, that means that if you make a change in a module such as 'system', it will trigger async builds in the dependent projects.
Right now I've only verified this works with the /specs and /modules. But I'm it will work for all the other modules.
The hard part about this is that after you run 'maven eclipse' in the root source folder, you still need to import all those individual projects into your workspace. Anybody have any ideas on how to automate importing multiple projects into a workspace?
Regards, Hiram
[EMAIL PROTECTED] wrote:
I like the sound of this.
How do you setup your eclipse workspace to allow development of geronimo ?
I presume that a separate project is required for each folder under /sandbox, /modules and /applications
Then how do you create a project for the 'geronimo' (root) folder to access other files / folders ?
Thanks,
Cameron
-----Original Message-----
From: Hiram Chirino [mailto:[EMAIL PROTECTED] Sent: Monday, 12 July 2004 2:06 PM
To: [EMAIL PROTECTED]
Subject: Making the maven eclipse target to work with the Reactor
Hi,
I figured out how to get the maven reactor to use the maven eclipse target so that it generates the eclipse project files that I need to work with Geronimo. So if no one minds I'm going to commit a quick change that will allow you to just run 'maven eclipse' at the root of the Geronimo project.
Regards, Hiram
