>> >> Telling people to edit and maintain two poms is also likely to lead to >> widespread derision. >> >> Here's another thought experiment in design. This may merely be me >> recapitulating Steven's idea. Say that for Maven 3.1 we wanted to fix >> this issue once and for all. So, we make maven 3.1 default to reading >> pom5.xml. (5 for the model version). If there isn't one of those, it >> goes looking for pom.xml. deploy:deploy creates pom.xml from pom5.xml, >> and deploys that too. (Artifact is 'pom5'.) >>
> > That is my idea (that I developed in discussions with brian fox and > others... so not entirely my idea) > Sometimes I don't really understand something until I can rewrite it coherently. I hope my disclaimer was sufficient. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
