Re: multi module eclipse:eclipse mewbie
Yes, Eclipse 3.3 On 2/17/08, Arnaud HERITIER [EMAIL PROTECTED] wrote: Do you have eclipse 3.3 ?? On Feb 17, 2008 6:28 PM, deckrider [EMAIL PROTECTED] wrote: On Feb 15, 2008 10:59 PM, Wendy Smoak [EMAIL PROTECTED] wrote: On Feb 15, 2008 9:09 PM, deckrider [EMAIL PROTECTED] wrote: 1. Check out the project, but don't use Eclipse to check it out. 2. Run 'mvn elicpse:eclipse' from the parent. 3. Now start Eclipse and import the existing project. This results in all the children coming into Eclipse as separate modules. However the parent is not available. Is this expected? Am I doing something non-standard? How am I supposed to work on the parent project? Eclipse apparently can't deal with the pom one level up from the modules. What I do is File - New - File, find the pom, click 'Advanced' and check 'Link to file on the filesystem'. That at least makes it available for editing. Odd, that I can't click 'OK' (its grayed out) when I try this. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- .. Arnaud HERITIER .. OCTO Technology - aheritier AT octo DOT com www.octo.com | blog.octo.com .. ASF - aheritier AT apache DOT org www.apache.org | maven.apache.org ... -- ASCII ribbon campaign: () against HTML email /\ against Microsoft attachments Information: http://www.expita.com/nomime.html - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: multi module eclipse:eclipse mewbie
On Feb 15, 2008 10:59 PM, Wendy Smoak [EMAIL PROTECTED] wrote: On Feb 15, 2008 9:09 PM, deckrider [EMAIL PROTECTED] wrote: 1. Check out the project, but don't use Eclipse to check it out. 2. Run 'mvn elicpse:eclipse' from the parent. 3. Now start Eclipse and import the existing project. This results in all the children coming into Eclipse as separate modules. However the parent is not available. Is this expected? Am I doing something non-standard? How am I supposed to work on the parent project? Eclipse apparently can't deal with the pom one level up from the modules. What I do is File - New - File, find the pom, click 'Advanced' and check 'Link to file on the filesystem'. That at least makes it available for editing. Odd, that I can't click 'OK' (its grayed out) when I try this. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: multi module eclipse:eclipse mewbie
Do you have eclipse 3.3 ?? On Feb 17, 2008 6:28 PM, deckrider [EMAIL PROTECTED] wrote: On Feb 15, 2008 10:59 PM, Wendy Smoak [EMAIL PROTECTED] wrote: On Feb 15, 2008 9:09 PM, deckrider [EMAIL PROTECTED] wrote: 1. Check out the project, but don't use Eclipse to check it out. 2. Run 'mvn elicpse:eclipse' from the parent. 3. Now start Eclipse and import the existing project. This results in all the children coming into Eclipse as separate modules. However the parent is not available. Is this expected? Am I doing something non-standard? How am I supposed to work on the parent project? Eclipse apparently can't deal with the pom one level up from the modules. What I do is File - New - File, find the pom, click 'Advanced' and check 'Link to file on the filesystem'. That at least makes it available for editing. Odd, that I can't click 'OK' (its grayed out) when I try this. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- .. Arnaud HERITIER .. OCTO Technology - aheritier AT octo DOT com www.octo.com | blog.octo.com .. ASF - aheritier AT apache DOT org www.apache.org | maven.apache.org ...
Re: multi module eclipse:eclipse mewbie
Looks like your parent project is just of pom type. In this case there wont be an eclipse project generated since there is not artifact to deliver. There are 2 things you can do: 1. Fire a feture request in JIRA so that simple eclipe project type is created from pom type porject. 2. Create a simple project in eclipse manually. Since it wont change (just a placeholder to hold other projects) you will be ok. Eclipse starting from version 3.3 is able to deal nested projects so you will be able to have parent and child projects in the same workspace easily. If you have an older eclipse you can create a separate workspace (I call it integration workspace) and work with the parent project from there. Siarhei On Feb 16, 2008 5:09 AM, deckrider [EMAIL PROTECTED] wrote: Sorry for the silly question but I'm trying to understand the best way to use Eclipse with Maven2 multi module projects. Here is my understanding: 1. Check out the project, but don't use Eclipse to check it out. 2. Run 'mvn elicpse:eclipse' from the parent. 3. Now start Eclipse and import the existing project. This results in all the children coming into Eclipse as separate modules. However the parent is not available. Is this expected? Am I doing something non-standard? How am I supposed to work on the parent project? Thanks in advance for your help and understanding. -- ASCII ribbon campaign: () against HTML email /\ against Microsoft attachments Information: http://www.expita.com/nomime.html - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
multi module eclipse:eclipse mewbie
Sorry for the silly question but I'm trying to understand the best way to use Eclipse with Maven2 multi module projects. Here is my understanding: 1. Check out the project, but don't use Eclipse to check it out. 2. Run 'mvn elicpse:eclipse' from the parent. 3. Now start Eclipse and import the existing project. This results in all the children coming into Eclipse as separate modules. However the parent is not available. Is this expected? Am I doing something non-standard? How am I supposed to work on the parent project? Thanks in advance for your help and understanding. -- ASCII ribbon campaign: () against HTML email /\ against Microsoft attachments Information: http://www.expita.com/nomime.html - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: multi module eclipse:eclipse mewbie
On Feb 15, 2008 9:09 PM, deckrider [EMAIL PROTECTED] wrote: 1. Check out the project, but don't use Eclipse to check it out. 2. Run 'mvn elicpse:eclipse' from the parent. 3. Now start Eclipse and import the existing project. This results in all the children coming into Eclipse as separate modules. However the parent is not available. Is this expected? Am I doing something non-standard? How am I supposed to work on the parent project? Eclipse apparently can't deal with the pom one level up from the modules. What I do is File - New - File, find the pom, click 'Advanced' and check 'Link to file on the filesystem'. That at least makes it available for editing. You might take a look at q4e or m2eclipse (the Eclipse plugins) to see if they've found a way to deal with this annoyance. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
