On 26 October 2010 10:30, Guillaume Nodet <[email protected]> wrote: > Itsn't the util project a good location for that ?
As long, IMHO, as we use submodules with sensible names. Util could turn into a dumping ground otherwise. If the util modules is turning into a 'commons' then shouldn't we just call it commons as is the way with other Apache projects, and then people coming to the project will know we're trying to fit into the 'commons' pattern. > > On Tue, Oct 26, 2010 at 10:24, Jeremy Hughes <[email protected]> wrote: >> On 25 October 2010 22:39, Alasdair Nottingham <[email protected]> wrote: >>> It appears that we have multiple classes which basically create a >>> ClassLoader that delegates to a Bundle. Ones I know of are: >>> >>> /blueprint/blueprint-core/src/main/java/org/apache/aries/blueprint/utils/BundleDelegatingClassLoader.java >>> /util/src/main/java/org/apache/aries/util/BundleToClassLoaderAdapter.java >>> /jpa/jpa-container/src/main/java/org/apache/aries/jpa/container/unit/impl/BundleDelegatingClassLoader.java >>> >>> There may be others. I was wondering if it would make sense to try to >>> common these up into one place? >>> >>> Thoughts? >> >> Good idea. I was wondering where you might put this. Since you use the >> word 'common' I think an 'aries commons' module would be a good place >> to put this. Something like trunk/commons/cl ? >> >>> Alasdair >>> >>> -- >>> Alasdair Nottingham >>> [email protected] >>> >> > > > > -- > Cheers, > Guillaume Nodet > ------------------------ > Blog: http://gnodet.blogspot.com/ > ------------------------ > Open Source SOA > http://fusesource.com >
