[prev in list] [next in list] [prev in thread] [next in thread] 

List:       jpackage-discuss
Subject:    Re: [JPackage-discuss] Java Package Search
From:       <R.Apel () t-systems ! com>
Date:       2008-06-26 13:43:44
Message-ID: 44D7FF08C0F1C047B611DAD72B180E7501CD3E69 () S4DE8PSAABE ! t-systems ! com
[Download RAW message or body]

Indexing jar files (among other class path units) for elements they
provide could indeed be a very useful entry to fine grained
Provide/Require relationships between such class path units.

I have been experimenting with the creation of "class path unit
descriptors" (xml based, db4 based) containing all of the details for 

- public members provided by classes contained in the cpunit, i.e.
including formal details (signatures) of provided fields and method etc.

- foreign public members required by classes contained in the cpunit and
their bytecode.

Having such indexes enables you to calculate possible variants of formal
satisfaction of requirements.

Which set (or alternative sets) of libraries would satisfy this and that
library's requirements on a class member level?

Convex closure considerations apply, of course...

And the volume of data to be handled isn't small, of course. So
efficient access is an issue.

_______________________________________________
JPackage-discuss mailing list
JPackage-discuss@zarb.org
https://www.zarb.org/mailman/listinfo/jpackage-discuss
[prev in list] [next in list] [prev in thread] [next in thread]