On Dec 10, 2010, at 8:08 PM, Bryan Loofbourrow wrote: > You don't need separate projects for this. You just need a bunch of > developer-facing pom files with different <modules> lists. They can certainly > live in the same directory. This is something we definitely take advantage > of, for producing interesting developer build sets.
What is the semantic difference between multiple POMs and a single POM containing the different module lists in profiles? It seems like the former is harder to support because a change outside the module sets requires changing every POM. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
