> As for creating my own maven, sure I can do that if it seems to be > necessary, though forking a project has significant costs, both in the > initial code and in maintenance.
No one is suggesting that you "create your own Maven" but rather simply suggesting that it might be a good idea to simply use InstallAnywhere or a similar tool to create an "official" Maven installation for your company that would include, among other things, the settings.xml file or other configuration files that you deem necessary. Then you can distribute this package to everyone who needs to use Maven in your company and it will come "ready to go." > I'd actually been thinking more along the lines of a plug-in that > parses settings.xml and fails out if it doesn't like what it sees. Sounds like a job for the enforcer plugin. > I'm just curious why this fairly important bit of configuration is > left out on the desktop where it is hard to manage. What alternative would you propose?? Feel free to design and implement such a system, and then donate the changed source code back to the Maven project for possible future inclusion in a future release. Personally, I have ZERO interest in such a feature and do not anticipate working on it. Wayne --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
