[tobrien]

I'm confused about the discussion focusing on how Eclipse IDE doesn't support nested projects. I use Eclipse every day to work with a serise of nested projects that I've organized in a tree. I also don't see how the "tree" structure is necessarily something to avoid. For example:

/root
 /apps
 /gui
 /report-tool
 /web
 /admin-war
 /auction-war
 /struts-common
 /modules
 /common
 /model
 /auction-model
 /profile-model
 /persist
 /auction-persist
 /profile-persist

Forget the names of the projects. The point here is that each directory contains a pom.xml, you run "mvn eclipse:eclipse" and then you import every project under /root. How does Eclipse not support this type of hierarchy?

[starksm64]

So let's just get going with maven 2 as the basis since there really are no major obstacles. There are only intangibles like seamless source dependencies that would have to be created regardless. I want to put together a plan for what needs to be done to move the jbossas build to maven with no loss of functionality.

I also want a plan for the preferred project layout in terms of managing artifacts.

Let's get this circulated to the project leads and beat into shape as how to build jboss projects.

[c.vidal]

Hi guys,

If I may, what's not supported is the following:

 /root
 pom.xml
 /module1
 pom.xml
 /module2
 pom.xml

This is the standard Maven 2 layout, but if you run mvn eclipse:eclipse at the root, it will generate the following which is not supported by eclipse:

 /root
 .project
 .classpath
 pom.xml
 /module1
 .project
 .classpath
 pom.xml
 /module2
 .project
 .classpath
 pom.xml

That's the nested kind of projects that eclipse doesn't support.

Whereas, the following alternative (known as "flat" in the M2 doc) is a safe layout:

 /root
 /root
 pom.xml
 /module1
 pom.xml
 /module2
 pom.xml

Because if you run mvn eclipse:eclipse at the root, it will generate the following which is supported by eclipse:

 /root
 /root
 .project
 .classpath
 pom.xml
 /module1
 .project
 .classpath
 pom.xml
 /module2
 .project
 .classpath
 pom.xml

For more information, here is the Maven 2 documentation:
http://maven.apache.org/guides/mini/guide-ide-eclipse.html

By the way, I'm really glad that you guys are looking into migrating the JBoss build system to Maven 2. As a long time Maven (1 and 2) user and a JBossAS afficionados, it has always been tricky to use JBoss libraries from a Maven 2 project (and before Maven 1). Such a move will make things a lot easier !

Is there a road map regarding that migration plan ?

Cheers

[c.vidal]

A drawback of the "flat" layout is that it is not supported by the Continuum continous integration server, whereas the "nested" is ...
http://66.249.93.104/search?q=cache:bT0nlnj5bXAJ:jira.codehaus.org/browse/CONTINUUM-462+continuum+flat+layout&hl=fr&gl=fr&ct=clnk&cd=1&client=firefox-a

So you have to choose between eclipse and continuum ...

Just my 2 cents ;)

[starksm64]

No explicit roadmap exists, we just have been trying to map out how to get started and one of the big holdup is migrating from cvs to svn as we really need to refactor the legacy/monolithic codebase but don't wan't to loose history.

Ruel has been tracking the proposed dev guide to maven here:
http://wiki.jboss.org/wiki/Wiki.jsp?page=MavenBuildCreation

Once we get past the svn migration we will really start to flesh out a migration plan.

Some know issues are:

1. We need control over what repository is used with a project. I want to be able to lock down where what repository can be used in a given build as part of the project definition.

2. The maven canonical project structure is too fine grained for many projects. We need some custom plugins to better support higher level artifiacts such as installer fragments.