Arguably, if perhaps impractically, maven should run with a security manager that prevented any one plugin from making some global change to the JVM that could have evil effects on other plugin. For example, from making the call in the subject.
On the other, it's hard for me to think of a legitimate reason for any plugin to want non-headless operation. This concerns me because jfreechart, used in code I'm wrapping in a plugin, makes my Mac's GUI flash if headless isn't set. It seems to me that it might be a legitimate idea for maven itself to just set headless, at least when invoked from the shell. Yes, of course, I could put it in MAVEN_OPTS, and I will if this suggesting is met with derision or worse. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
