Moved com.sun.jini.landlord.LeasedResource into jsk-dl.jar. This was done to accomodate outrigger-dl.jar's reliance on com.sun.jini.landlord.LeasedResource from com.sun.jini.outrigger.StorableResource. In the ant based build, LeasedResource was included using classdepandjar. Using a Maven build, outrigger-dl depends on river-dl (new name for jsk-dl). Adding LeasedResource to river-dl made sense. The approach taken to populate the source tree in the maven-zed structure is to load exiting jars, and for each entry in the loaded jar, copy the source files into each respective module's src directory, taking care not to duplicate any classes between modules. Making he change to jsk-dl.jar's build allows the river-dl module to be created correctly.
Moved com.sun.jini.landlord.LeasedResource into jsk-dl.jar. This was done to accomodate outrigger-dl.jar's reliance on com.sun.jini.landlord.LeasedResource from com.sun.jini.outrigger.StorableResource. In the ant based build, LeasedResource was included using classdepandjar. Using a Maven build, outrigger-dl depends on river-dl (new name for jsk-dl). Adding LeasedResource to river-dl made sense. The approach taken to populate the source tree in the maven-zed structure is to load exiting jars, and for each entry in the loaded jar, copy the source files into each respective module's src directory, taking care not to duplicate any classes between modules. Making he change to jsk-dl.jar's build allows the river-dl module to be created correctly.

git-svn-id: e208463f0da49ce01d17e17a21a9293a7ba6b26a@1590726 13f79535-47bb-0310-9956-ffa450edef68

pfirmstone/JGDMS,pfirmstone/JGDMS,pfirmstone/JGDMS,pfirmstone/river-internet,pfirmstone/river-internet,pfirmstone/JGDMS,pfirmstone/river-internet