Well, this is somewhat related to the old story, to include api into implementation or not to include and import from its own bundle. Sure, util is not api, but i can somewhat understand the inclusion of those to libs into the respective bundles. Also because they are just two classes.
Anyhow, let the community decide. (my vote is 0 here) Remember: This is not related to the maven convertion. Just what to embed in the final bundles. (one line in osgi.bnd) On Sat, Dec 12, 2009 at 6:23 PM, Brian Topping <[email protected]> wrote: > Hi guys, > > As I get into the tree, I notice that the util project contents (all two > files) are duplicated into every jar. I can assume there's a good reason > that might have been desirable, but there's some havoc with Maven to do so. > > As I look through the dependencies on these two files, there are really > only calls to o.a.a.util.Codec from the ace-log project and calls to > o.a.a.util.VersionRange from the ace-client-repository-helper-bundle > project. > > Any reasons I'm not fully understanding to not move these to those > respective projects and doing away with the util project until we have a > stronger need for something like it in the future? > > Cheers, Brian > > p.s. Sorry if this detail granularity is too small... just don't want to > make any stupid assumptions as I get started. > -- Toni Menzel Independent Software Developer Professional Profile: http://okidokiteam.com [email protected] http://www.ops4j.org - New Energy for OSS Communities - Open Participation Software.
