Hm, OK, fair enough. I'm not sure if this applies to the work you're
doing, but there is another aspect to this: right now the package
hierarchy doesn't make it clear where common code goes -- there should
be a specific package, org.apache.derby.common or something like that.
David
Jeremy Boynes wrote:
David Van Couvering wrote:
You might want to take a look at DERBY-289 ("enable code sharing
between Derby client and engine"). Any rearrangement of jar files
should probably take this into consideration.
With the desire to have a single entry on the classpath, I was planning
on including the common code in all jars where it was needed.
--
Jeremy
