eclipse .classpath generation in a multiproject with eclipse:eclipse

2006-11-22 Thread AndreasWuest
hello, i have a question concerning the usage of eclipse in a multiproject build. i have a project that has the following structure : + project + ear + ejb + web The project contains a pom.xml with the defined modules: modules moduleear/module moduleejb/module

Re: eclipse .classpath generation in a multiproject with eclipse:eclipse

2006-11-22 Thread Thomas Recloux
The maven eclipse plugin creates eclipse .project and .classpath files for each maven project ( : pom.xml file). You should read this guide : http://maven.apache.org/guides/mini/guide-ide-eclipse.html 2006/11/22, AndreasWuest [EMAIL PROTECTED]: hello, i have a question concerning the usage of

Re: eclipse .classpath generation in a multiproject with eclipse:eclipse

2006-11-22 Thread AndreasWuest
i have seen the guide, but it did not really convice me. so this guide tells me that i need at least two eclipse instances. one that only servers as a cvs client, and one which is used as java ide. i can't see the disadvantage of having a .project and a .classpath created in the parent, with

Re: eclipse .classpath generation in a multiproject with eclipse:eclipse

2006-11-22 Thread Thomas Recloux
i have seen the guide, but it did not really convice me. so this guide tells me that i need at least two eclipse instances. one that only servers as a cvs client, and one which is used as java ide. You can't use an other cvs client for the root pom ? i can't see the disadvantage of having a

Re: eclipse .classpath generation in a multiproject with eclipse:eclipse

2006-11-22 Thread Barrie Treloar
On 11/23/06, AndreasWuest [EMAIL PROTECTED] wrote: i have seen the guide, but it did not really convice me. so this guide tells me that i need at least two eclipse instances. one that only servers as a cvs client, and one which is used as java ide. i can't see the disadvantage of having a