Re: [m2] eclipse:eclipse and eclipse 3.2 projects within a project suppo
Hello Max, Max Cooper wrote: If you have a structure like this: root |--module1 |--module2 |--submodule2-1 my structure is a bit simpler, without nested submodules. Max Cooper wrote: ... you would have to make sure that you hide/delete/rename the .project file in both the root and module2 directories for the submodule2-1 project to show up on the import. so fortunately this is not my case. Max Cooper wrote: Eclipse does not support hierarchical project structures. i thought eclipse 3.2 just introduced this new feature ... Max Cooper wrote: IMO, moving your parent pom to a subdir is a better compromise than having all of your files show up two or more times in Eclipse. of course, but this would break a well established maven convention, which i'd like to avoid.. -Max Valerio Schiavoni wrote: baerrach wrote: Because there is no .project file eclipse will show all the subprojects as being available. i don't get this step working...it doesn't show submodule projects as being availble, even if each of them have their respective .project and .classpath any one with my same issue ? thanks, valerio - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/-m2--eclipse%3Aeclipse-and-eclipse-3.2-projects-within-a-project-support.-tf2112924.html#a5979145 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] eclipse:eclipse and eclipse 3.2 projects within a project suppo
On 8/25/06, Valerio Schiavoni [EMAIL PROTECTED] wrote: Eclipse does not support hierarchical project structures. i thought eclipse 3.2 just introduced this new feature ... Yes it does. Hence my original post wondering how to get it to work. The notes I posted worked for me. Try to get it working manually to prove to yourself that it can be done. Just checkout a multi-module project and then try to import the modules as existing projects. If you can't get that to work you may have other problems. Then its just a matter of running mvn eclipse:eclipse from the root, delete the root/.project file and doing the same steps again. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [m2] eclipse:eclipse and eclipse 3.2 projects within a project suppo
I also am using hierarchial projects. I got 3 levels deep and it works fine. It only creates project files for the leaf nodes. The parent poms (packaging=pom) will not get project files. I am having 1 problem with eclipse:eclipse. I have a parent pom that isn't intended to be portable. It uses variables that prevent it from validating, however, I need it so my 100s of sub poms don't have to define the same stuff over and over. Anyway, eclipse:eclipse is barfing on some paths, just curious if there is a way to get it to be less strict or something. -Original Message- From: Barrie Treloar [mailto:[EMAIL PROTECTED] Sent: Friday, August 25, 2006 3:16 AM To: Maven Users List Subject: Re: [m2] eclipse:eclipse and eclipse 3.2 projects within a project suppo On 8/25/06, Valerio Schiavoni [EMAIL PROTECTED] wrote: Eclipse does not support hierarchical project structures. i thought eclipse 3.2 just introduced this new feature ... Yes it does. Hence my original post wondering how to get it to work. The notes I posted worked for me. Try to get it working manually to prove to yourself that it can be done. Just checkout a multi-module project and then try to import the modules as existing projects. If you can't get that to work you may have other problems. Then its just a matter of running mvn eclipse:eclipse from the root, delete the root/.project file and doing the same steps again. - 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]
Re: [m2] eclipse:eclipse and eclipse 3.2 projects within a project suppo
Valerio Schiavoni wrote: Hello Max, Max Cooper wrote: If you have a structure like this: root |--module1 |--module2 |--submodule2-1 my structure is a bit simpler, without nested submodules. Okay, like this: root |--module1 |--module2 Max Cooper wrote: ... you would have to make sure that you hide/delete/rename the .project file in both the root and module2 directories for the submodule2-1 project to show up on the import. so fortunately this is not my case. Generally, this still is the case. You MUST hide/delete the .project file in root so that Eclipse will allow you to add module1 and module2. It is the same issue, but you only have to worry about one level. I have verified that the procedure outlined in this email thread works in Eclipse 3.2, as have others. If it isn't working for you, something is wrong. Max Cooper wrote: Eclipse does not support hierarchical project structures. i thought eclipse 3.2 just introduced this new feature ... Eclipse 3.2 does not support hierarchical project hierarchies. It was rumored that 3.2 would have such support before the release, but it does not. The procedure in this email thread is just a trick to get Eclipse to accept having overlapping projects. This trick allows a hierarchical structure of Maven modules to be mapped into a flat structure of Eclipse projects. Max Cooper wrote: IMO, moving your parent pom to a subdir is a better compromise than having all of your files show up two or more times in Eclipse. of course, but this would break a well established maven convention, which i'd like to avoid.. Moving the parent to a subdir is documented on the Maven site, and many people are using this technique successfully. The Eclipse trick in this thread is not as clean, IMO. -Max - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] eclipse:eclipse and eclipse 3.2 projects within a project suppo
baerrach wrote: Because there is no .project file eclipse will show all the subprojects as being available. i don't get this step working...it doesn't show submodule projects as being availble, even if each of them have their respective .project and .classpath any one with my same issue ? thanks, valerio -- View this message in context: http://www.nabble.com/-m2--eclipse%3Aeclipse-and-eclipse-3.2-projects-within-a-project-support.-tf2112924.html#a5964416 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] eclipse:eclipse and eclipse 3.2 projects within a project suppo
If you have a structure like this: root |--module1 |--module2 |--submodule2-1 ... you would have to make sure that you hide/delete/rename the .project file in both the root and module2 directories for the submodule2-1 project to show up on the import. When Eclipse finds a .project file at a node in the file tree, all projects from the subtree rooted at that node are hidden, because Eclipse does not support hierarchical project structures. IMO, moving your parent pom to a subdir is a better compromise than having all of your files show up two or more times in Eclipse. I would use the technique outlined in this thread ONLY in cases where you could not move the parent pom to a subdirectory. -Max Valerio Schiavoni wrote: baerrach wrote: Because there is no .project file eclipse will show all the subprojects as being available. i don't get this step working...it doesn't show submodule projects as being availble, even if each of them have their respective .project and .classpath any one with my same issue ? thanks, valerio - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
