Just been playing around with eclipse projects. I see that
eclipse:eclipse makes a separate project for each pom, whilst
retaining the option to add project references if you want to.
Wouldn't it make more sense though, for eclipse:eclipse to add a new
source folder under an existing eclipse project? As a graphical
illustration:
Current eclipse:eclipse result:
MyUtilProj [classpath REPO/junit]
MyModelProj [ref MyUtilProj] [classpath: REPO/jaxen, REPO/junit,
REPO/myutil.jar]
MyGUIProj [ref MyModelProj] [classpath: REPO/servlets, REPO/
httpunit, REPO/mymodel.jar]
Suggestion:
MyKillerApp [classpath: REPO/jaxen, REPO/servlets, REPO/junit etc,
REPO/httpunit]
- utilsrc
- modelsrc
- guisrc
which would seem more in keeping with how you would manage a project
before you had heard of Maven (maybe not in the experience of
others). Also there is a practical advantage that when you press F3
to navigate to a type, you go straight to the source file. With the
current arrangement (maybe its my ide settings, but I don't think so)
you get the unwanted choice of going the the class in the jar file
artifact (and "would you like to attach source" etc).
Additionally, my personal favourite, is that when you go to the Java
Browsing perspective, you can see all the code under one package
source tree - just make sure MyKillerApp is highlighted on the left!
I believe to get this to work, you would need to configure the
eclipse plugin with the location of an existing eclipse project for
it to append a source folder to (it would create the project if it
doesn't exist). Although this is extra info to tell the plugin you
would get to remove the info about project dependency.
In fact because all the artifact poms have a parent pom in common,
you wouldn't even have to specify an eclipse project, it would create
one based on the name of the parent.
-AW
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
