On Thu, 2005-10-06 at 19:06 +0000, John Fallows wrote:
> On 9/28/05, Trygve Laugstøl <[EMAIL PROTECTED]> wrote:
> > On Mon, 2005-09-26 at 22:02 +0000, John Fallows wrote:
> > > On 9/25/05, Trygve Laugstøl <[EMAIL PROTECTED]> wrote:
> > > > On Sat, 2005-09-24 at 04:31 +0000, John Fallows wrote:
> > > > > On 9/23/05, Trygve Laugstøl <[EMAIL PROTECTED]> wrote:
> > > > > > On Fri, 2005-09-23 at 08:03 +0000, John Fallows wrote:
> >
> > [snip]
> >
> > > > [1]: http://jira.codehaus.org/browse/MNG-932
> > >
> > > Yes, I understand that it would be generally useful to deliver a
> > > subset of the unit test code as a JAR.
> > >
> > > The above proposal still stands though, although the name "mock" can
> > > be treated as a placeholder for that subset until we have a better
> > > name.
> >
> > Not sure I agree, what more than distributing the test do you need?
> 
> We need to make sure that not all the test code is delivered in the
> JAR, just the mocks.
> 
> The reason is that this mock JAR is essentially a public API for
> testing, so any other test implementation code for the API project
> should not be included.
> 
> This will prevent test authors using the mock JAR from inadvertently
> establishing a dependency on non-public test code in their own tests,
> that would then break when the API tests are changed.

I think that the above JIRA issue is sufficient for your use case too as
it will have to include some form of includes/excludes thing. At least
there's a lot of stuff that's shared between installing a -test and a
-mock jar that will have to be resolved (as commented in the issue)
first.

> >
> > > Alternatively, is there any mileage in the idea of having completely
> > > separate sub-modules for main, mock, and test, all inside the
> > > api-module?
> >
> > Don't think so, but I also think I'm missing some information here :)
> 
> Let me know what you think, now that the above additional requirement
> is more clear.

--
Trygve


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to