Because then you couldn't just copy your workspace to another filesystem
and keep using it... As it is the workspace is totally
self-contained. Granted the setup and versions of Eclipse using it need
to be reasonably compatible. We don't version control
.classpath or .project files, so their presence is not really a problem,
if you svn checkout the project there is not a trace of the
fact that you used Eclipse to develop it.
Eli Doran wrote:
Also, I was thinking in a "perfect" world Eclipse would not dirty your
project directories with .classpath and .project files either. Why
can't it store those in a eclipse data directory anyway, sheesh. Like
maybe ~/.eclipse/projectName/classpath
:)
Eli Doran wrote:
Thanks for the response. :)
I have the maven projects setup using the <module> elements in the
parent project's pom and everything works happily with maven.
There are two reasons I put the pom below the root.
1. i like all build information to be kept in a "build" directory
and all the source in "source" leaving the root to only contain
things like the license, readme, etc.
2. i still use Ant as well and my projects are both ant and maven
ready. So, I put both the ant build scripts and the pom in "build"
and everything works well.
Then eclipse enters the picture and the maven plugin wants the pom in
the root. Doh. :) I suppose I could also put ant's build.xml in the
root and have it import the other scripts from "build" ... anyway,
that's why I was asking. Other than working around those 2 quirks I'm
enjoying using Eclipse and the m2eclipse plugin.
thank you,
eli
Tod Harter wrote:
The way we handle subprojects is:
The top level pom is itself an eclipse project, pom. Thus in the
workspace the top level pom is ~/workspace/pom/pom.xml and it
specifies its modules with
<modules>
<module>../submoduleA</module>
<module>../submoduleB</module>
...
</modules>
Submodules are just normal projects named submoduleA, submoduleB,
etc. They can specify the parent pom in the normal manner.
I don't know of a way to put a pom BELOW the root directory of a
module or submodule. It doesn't seem like a really useful feature,
generally. Deviating from standard maven layouts is always an uphill
battle at best... In a perfect world eclipse would let you nest
subprojects/submodules beneath their parents in the fashion maven
would like to do it, and even using the ../submoduleN technique
tends to expose various bugs in recursive builds, but at present it
is the only real game in town as far as I can see.
Eli Doran wrote:
Thank you for making this plugin. It's very helpful. :)
First, I was wondering if there is a way to configure the plugin to
look for the project's pom.xml file in a subdirectory of the
project instead of the root? For example instead of at "/pom.xml" I
want to place it in "/build/pom.xml".
I'm fairly new to eclipse (please, don't cringe ;) and I'm
wondering if the plugin supports a parent project of multiple
subprojects? I have the projects setup and can use the command line
successfully affecting the subprojects. I don't see how to setup
the parent project in eclipse though.
I have the 3 subprojects setup in eclipse each as their own
project. I defined 3 external tools calling maven for each of the
projects.
I added a the parent project, enabled maven2 with the pom.xml file
it has as the parent project. However, it wants to add all the
source locations from the subprojects and when i run the external
tool with a goal it does not affect the subprojects. Running an
install doesn't work as it doesn't locate the subprojects and run
through them.
But it works happily from the command line. A call "mvn install"
will do an install on all 3 subprojects.
See where I'm breaking it? Or, am I attempting to do something
currently unsupported?
Thank you
Eli Doran
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
