Yes. But while this solves this problem for this one situation, singletons pop up everywhere. It might not be MY library but it might be something else.
File names, database table names, port numbers. I’m sure I’m missing something. With containers, all of this stuff is solved and I don’t need to code around these issues. On Tue, Feb 24, 2015 at 10:08 AM, Aldrin Leal <[email protected]> wrote: > If you set the port number to zero, you'd get a random one. Try looking at > some tests out there to find out how > > for reference: > http://stackoverflow.com/questions/2231467/dynamically-choosing-port-number > > > -- > -- Aldrin Leal, <[email protected]> > Master your EC2-fu! Get the latest ekaterminal public beta > http://www.ingenieux.com.br/products/ekaterminal/ > > On Tue, Feb 24, 2015 at 3:05 PM, Kevin Burton <[email protected]> wrote: > > > The ‘singleton’ problem with maven tests around port numbers, file names, > > is a big problem that’s bitten me over the years. > > > > I’d love if Maven could fork tests or with parallelism, run tests in a > > container. > > > > Right now I have two modules running tests and they are conflicting on > > ports. > > > > If they were run in containers the ports wouldn’t conflict. > > > > -- > > > > Founder/CEO Spinn3r.com > > Location: *San Francisco, CA* > > blog: http://burtonator.wordpress.com > > … or check out my Google+ profile > > <https://plus.google.com/102718274791889610666/posts> > > <http://spinn3r.com> > > > -- Founder/CEO Spinn3r.com Location: *San Francisco, CA* blog: http://burtonator.wordpress.com … or check out my Google+ profile <https://plus.google.com/102718274791889610666/posts> <http://spinn3r.com>
