> a pom.xml can only list a single source folder. If you have more than one (for whichever reason) I agree that this example demonstrates that the Maven model

> a pom.xml can only list a single source folder. If you have more than one (for whichever reason) I agree that this example demonstrates that the Maven model is broken, but why would you structure your project like this rather than using another module or a submodule? Maybe it's just lack of experience, but I highly prefer the rigidity of Maven projects compared to some of the messes that more expressive build systems allow.