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-cas
On Jul 25, 2010, at 9:54 AM, Peter Janes wrote:
> There's also
> org.codehaus.mojo:build-helper-maven-plugin:reserve-network-port, which only
> assigns random ports (unlike port-allocator, which allows the use of explicit
> ports).
>
> I'm hesitant to put this next bit forward, given Jason's
There's also org.codehaus.mojo:build-helper-maven-plugin:reserve-network-port,
which only assigns random ports (unlike port-allocator, which allows the use
of explicit ports).
I'm hesitant to put this next bit forward, given Jason's implicit approval of
the "POM expression" approach, but what
We created something for the Nexus testing that we could extend or further
generalize:
http://svn.sonatype.org/plugins/trunk/port-allocator-maven-plugin/
On Jul 25, 2010, at 5:26 AM, Kristian Rosenvold wrote:
> The most popular problem when converting to parallel seems to be
> allocation of TCP
The most popular problem when converting to parallel seems to be
allocation of TCP/IP port numbers per-module. Where builds would be
using one shared port-number across all modules, they now need distinct
port-numbers.
A solution I can think of is to make a pom expression like
${dynamicPortNumber}
