Jason van Zyl wrote: > That is distinctly different than multiple source directories for your > application. And here we are trying satisfy these requirements and scale > by letting the plugins deal with these different requirements instead of > trying to jam everything into the POM.
I believe that the POM is the proper place for defining what goes in your project. Plugins should retrieve information from there and proceed with their work. Right now many plugins rely on project.properties file rather than POM, wich I think is not right. Of course we should always use our best judgement to avoid cluttering the POM, but I thing that the source directories (java, aspect, unit test, and others that arise) are crucial for defining the project, and therefore they should be in the POM. I really like Michal's proposal with sources/source/type elements. It puts the emphasis on the plugins undestating a specific type of sources, and allows us remove funcitonality from Maven core - it only manages information on abstract source sets. I think this kind of change that it's really worth pursuing. R. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
