Wow, thanks for the awesome tip! That's has helped clear things up
enourmously.
It was actually fairly simple to flatten the Maven modules the way I
suspected. It was vastly more difficult to 'flatten' the Eclipse
projects in the file system - well actually it was easy to flatten the
Eclipse projects, it was really difficult to figure out how.
Also, the reference you gave me has tons more considerations on dealing
with Maven in Jazz-land.
Cheers, Eric
On 2011-04-18 5:38 PM, Barrie Treloar wrote:
On Tue, Apr 19, 2011 at 8:17 AM, Eric Kolotyluk
<[email protected]> wrote:
I apologize if this is a newbie question, but I'm looking for a quick
answer...
I'm using Sonatype Maven plug-in for Eclipse and I have set up a project
with several modules. The way the plug-in arranged them on the file system
is:
You may have better luck on the m2e mailing list, or ask the Team
Concert lists how a hierarchical layout is supported.
You may be able to use the guidance at
http://maven.apache.org/plugins/maven-eclipse-plugin/reactor.html
*Read this carefully*
Especially "Note, you have to delete the .project-file of your parent
project before."
You need to do this as the "import" step will produce a blank list of
projects to import, but if you delete the .project file and try the
sub-projects are now available in the list.
Eclipse doesn't really support "projects within projects" so your
mileage may vary", however a lot of us have this working ok.
You can also try turning off Team support for the sub-projects and
only uses the main project for checkin/checkout.
---------------------------------------------------------------------
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]
