The only well-known use-case I know of is all sorts of container-plugins (like maven-jety-plugin) + surefire. The state is shared between at least two different plugins, which to my understanding means it's best pushed from the outside & in (or pulled from a common source).
I think all the use-cases I've seen only involve 1 port per MavenProject, but I know you guys will surprise me with some twists on this. This isn't a problem which HAS to be solved for 3.0, since these problems are being solved already - often pushing the values into different plugins from pom properties. But the guy with 40 modules in his reactor gets a lot of tedious book-keeping to do, and when you add a module later you break things etc. Kristian --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
