Re: Best Practice for testing code that uses provided dependencies

2013-10-28 Thread Ron Wheeler
On 27/10/2013 10:36 PM, Russell Gold wrote: On Oct 27, 2013, at 9:38 PM, Ron Wheeler > wrote: On 27/10/2013 7:59 PM, Russell Gold wrote: I’m actually running into the same issue, and my plan was s to take advantage of the situation to provide test vers

Re: Best Practice for testing code that uses provided dependencies

2013-10-27 Thread Russell Gold
On Oct 27, 2013, at 9:38 PM, Ron Wheeler wrote: > On 27/10/2013 7:59 PM, Russell Gold wrote: >> I’m actually running into the same issue, and my plan was s to take >> advantage of the situation to provide test versions of the classes. What I >> found was that the “provided” dependency wound up

Re: Best Practice for testing code that uses provided dependencies

2013-10-27 Thread Ron Wheeler
On 27/10/2013 7:59 PM, Russell Gold wrote: I’m actually running into the same issue, and my plan was s to take advantage of the situation to provide test versions of the classes. What I found was that the “provided” dependency wound up in the test class path. So I think that the fact that it i

Re: Best Practice for testing code that uses provided dependencies

2013-10-27 Thread Russell Gold
I’m actually running into the same issue, and my plan was s to take advantage of the situation to provide test versions of the classes. What I found was that the “provided” dependency wound up in the test class path. So I think that the fact that it is provided should have no impact on how you

Best Practice for testing code that uses provided dependencies

2013-10-27 Thread Ron Wheeler
We have code that depends on "provided" libraries. What is the best way to test the code? I don't particularly want to add the shared libraries to the project since they are large and will add a big load into the SCM and make it hard to check out the project. Can I add the dependency twice,