Step 1

Replace the current Maven 1 build with an Ant build.

Step 2

• split src/main into src/core and src/bundled (for bundled modules?)
• split main.pom into core.pom, bundled.pom and external.pom (or thirdparty.pom?)
• use a naming convention for any tests that require a third party library that we don't intend to include in the complete install

E.g. for now, assuming AntBuilder lives in bundled (not core) we could split the current AntTest in two, e.g. AntBuilderTest and AntBuilderExternalLibsTest. Any dependencies for AntBuilderTest must have compile or runtime scope in bundled.pom. The functionality represented in AntBuilderTest is what we advertise as "runs out of the box - for a full install". Anything in AntBuilderExternalLibsTest would also use jars in the external.pom file. We can then create a page like the ant optional task library dependencies page but I suggest we use pom format rather than listing jars individually.

So, going back to the AntBuilder example, the main functionality for AntBuilder would be covered in the AntBuilderTest which might require dependencies such as ant.jar and ant-launcher.jar. If we wanted ant junit task to also work out of the box we would have a test for it in AntBuilderTest and include ant-junit.jar as another of our dependencies. If not, we could still have a test for it in AntBuilderExternalLibsTest and it would get mentioned in external.pom. Ant tasks are probably not a good example here but as another example, any SqlTests which rely on a real database would be in SqlXxxExternalLibsTest. Unit tests or system/integration tests that only rely on JDBC core libraries would be part of either core or bundled poms.