I'm currently investigating the same thing, with
http://maven.apache.org/guides/mini/guide-ide-eclipse.html as my point
of reference. I just today created the desired structure - which indeed
requires one 'complete' checkout in a client tool like TortoiseSVN, as
suggested in the guide. From eclipse I use the flat layout.
I've just started with the journey and am especially interested in how
the reporting (aggregation) is going to behave.
Jan.
jan_bar wrote:
Hi,
I have spent quite a time looking for good J2EE directory layout that will
work with maven, Eclipse and SVN (CVS). It's not clear to me how you solve
this problem. So far here are two options and their troubles:
1. Flat layout (parent POM folder is located next to EJB, WAR, ... folders).
This plays nice with Eclipse/SVN, but has troubles: maven1 cannot handle
this structure, maven2 plugins has issues with this structure (release
plugin), this is not standard layout
2. Almost flat layout (parent POM is one folder up from the EJB, WAR, ...
folders). This is maven2 recommended layout, but it doesn't fit into
Eclipse/SVN. Developers are required to use SVN/CVS clients to check out the
whole layout to some folder and then each EJB, WAR are linked into
workspace. You cannot use Eclipse CVS/SVN plugin to checkout the parent POM
without fiddling with files - moving checkouted files out of workspace
(possible space for errors).
3. ?
I don't like any of the two solutions, solution 2 will require to use
another CVS/SVN client (all developers must learn it) or to follow some
guidelines.
Thanks for any idea, Jan
---------------------------------------------------------------------
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]
