Mikhail Loenko wrote:
BTW AFAIK we do not test whether manifests list all imports/exports
So if we create data from manifests then it could be insufficient and
we might have the same failures we had yesterday.
Yes... but we already have the manifests. They have to be right for OSGi.
So given that we need to have this dependency information, and have it
be correct, for the manifests, why not focus on getting that right, and
forever more leverage that beauty, goodness and truth?
geir
Thanks,
Mikhail
2006/4/12, Anton Avtamonov <[EMAIL PROTECTED]>:
On 4/12/06, Geir Magnusson Jr <[EMAIL PROTECTED]> wrote:
Why have a static file? Why not just generate from the modules
manifests? Then the error can only be in one place - the dependent
module... right?
If they have enough info - of course! That would be excellent.
I suppose it is a bit not trivial since the required information is
not the modules the particular module is depended on, but all the
modules which depend on the particular module. However it should be
not hard to revert.
Did I catch your idea right?
--
Anton Avtamonov,
Intel Middleware Products Division
---------------------------------------------------------------------
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
