Ok, that makes sense. A separate module sounds good to me, although if they are used in the Stripes unit tests, I can see why they would be in the main module. It could be awkward to write tests in separate module from the code under test, just to facilitate the mocks being separate.
-Josh On Sun, Apr 6, 2014 at 1:42 PM, Larry Meadors <[email protected]>wrote: > They are intended to be used to test your stripes applications, so in > that respect, they are useful outside of the context of the stripes > project. > > However, they are not useful in a production deployment - having them > in the main project is akin to deploying JUnit with your war file. > > Larry > > > On Apr 6, 2014 11:28 AM, "Joshua Chaitin-Pollak" <[email protected]> > wrote: > > > > They don't need to be in a separate module, they could probably just be > moved to > > src/test/java/ and Maven will automatically exclude them. > > > > > > On Sun, Apr 6, 2014 at 7:44 AM, Larry Meadors <[email protected]> > wrote: > >> > >> Is there a reason that the test components > >> (net.sourceforge.stripes.mock) aren't separated out into a > >> stripes-test module so they don't get deployed as part of production > >> applications? > >> > -- Joshua Chaitin-Pollak Chief Technology Officer Assured Labor, Inc. www.assuredlabor.com www.empleolisto.com.mx www.trabalhoja.com.br
------------------------------------------------------------------------------
_______________________________________________ Stripes-development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/stripes-development
