Service provider module resolution <was> Re: Services/configuration/context webrevs

[Paul Sandoz]

On Aug 7, 2012, at 11:36 AM, Alan Bateman <Alan.Bateman at oracle.com> wrote:
>> :
>> No, it needs to be separated out as a project, there is exploded source, and i want to open it in a IDE (plus it will be updated when moving to TestNG, notice that there is a test dimension for testing the various class loaders, a TestNG data provider can be used to abstract this). We also may have other projects in the future.
>> 
>> When this patch goes in i will be updating the runtime tests to include more test code related to service instance iteration failure.
>> 
> My comment was actually about the additional level rather the source tree. When open in an IDE or with TestNG then I assume that the shell test isn't interesting and could remain at the same level as the other shell scripts.

I consider the shell script to be part of the project, it's the ad-hoc project file that builds and executes, and could be the one kicks off TestNG (not sure yet). If the project directory is renamed or moved somewhere else we should not have to update or move that script.


> If this is all going to be reorganized then it's no big deal but it is critical that all the infrastructure we use support TestNG before we can really move over.
> 

Yes, the plan is to look closely at what lambda is doing and follow in its wake.

Paul.