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 properly set src and output folders.
correct me if i am wrong, but the only disadvantage would be the fact,
that it might be complicated to collect all the
data and create the correct paths, or do i miss something ? once the src
and output folders are set correctly everything
is supposed to work fine, no need for two eclipse instances and
inconvenient importing actions.
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 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>
<module>ear</module>
<module>ejb</module>
<module>web</module>
</modules>
each of the modules contains a pom.xml of its own, well the usual stuff.
in the standalone version (without eclipse) everything works fine.
the problem occurs when i import that project into eclipse and try to
compile
the project. after creating the
.classpath and .project files with mvn eclipse:eclipse from the project
directory
i have a .classpath and a .project file in each of my module
directories, not
in my project directory !
however eclipse ignores the created files in the modules directories, it
expects
one file to be created in the project directory (root of the project).
so is there
a way to tell the plugin to create a proper classpath and project file
for the root
directory (the parent).
the file .classpath content is supposed to look something like :
<classpath>
<classpathentry output="ear/target/classes" kind="src"
path="ear/src/main/java"/>
<classpathentry output="ejb/target/classes" kind="src"
path="ejb/src/main/java"/>
<classpathentry output="ejb/target/classes" kind="src"
path="ejb/target/generated-sources/xdoclet"/>
<classpathentry output="web/target/classes" kind="src"
path="web/src/main/java"/>
.....
<classpathentry kind="con"
path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
<classpathentry kind="output" path="bin"/>
</classpath>
basically i need for the source files of each module a specific output
directory (usually
the classes in the target directory).
so what is needed is a kind of merged .classpath file in my project
directory that
contains the individual .classpath file information from the mdules, so
the eclipse ide can
compile the java classes and put them into the correct (module) output
folders.
i can provide a testcase on request.
thanks in advance,
andy
---------------------------------------------------------------------
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]
