[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [equinox-dev] Getting info for dynamic imports through the console
|
From the output it is not clear if they are optionally
imported or not - it reports them as unresolved direct constraints and missing
imported packages.
Is diag just reporting about
optionally imported packages? Isn't that the only way it could know which
packages are potentially dynamically imported?
"Kirchev, Lazar"
<l.kirchev@xxxxxxx>
Sent
by: equinox-dev-bounces@xxxxxxxxxxx
07/08/2009 09:00 AM
|
Please respond
to
Equinox development mailing list
<equinox-dev@xxxxxxxxxxx> |
|
|
To
| "Equinox development mailing list"
<equinox-dev@xxxxxxxxxxx>
|
|
cc
|
|
|
Subject
| RE: [equinox-dev] Getting info for
dynamic imports through the console |
|
Thanks, Then I will open a bug for the diag, and an
enhancement request for providing info for the dynamically imported packages. I
will try to provide patches shortly.
Lazar
From: equinox-dev-bounces@xxxxxxxxxxx [mailto:equinox-dev-bounces@xxxxxxxxxxx] On Behalf Of Thomas Watson
Sent: Wednesday, July 08,
2009 4:53 PM
To: Equinox development mailing list
Subject:
RE: [equinox-dev] Getting info for dynamic imports through the
console
The diag command appears to have a bug then. I do not expect
that behavior. There currently is no way to get information about dynamically
imported packages from the console. You should open a bug and contributions are
welcome ;-)
Tom
"Kirchev, Lazar"
---07/08/2009 08:38:37 AM---But then why if the bundle imports dynamically
packages, which are not provided by any other bundle, the diag command returns
t
From:
| 
"Kirchev, Lazar" <l.kirchev@xxxxxxx>
|
To:
| 
"Equinox
development mailing list" <equinox-dev@xxxxxxxxxxx>
|
Date:
| 
07/08/2009
08:38 AM
|
Subject:
| 
RE:
[equinox-dev] Getting info for dynamic imports through the
console |
But then why
if the bundle imports dynamically packages, which are not provided by any other
bundle, the diag command returns that the dynamically imported packages are
missing? This really does not affect the resolving of the bundle and it gets
resolved correctly, but still are returned by diag. When a bundle providing
these packages is installed and activated, diag stops returning the dynamically
imported packages as missing.
But my question was more about how I can check through the
console what packages a bundle imports dynamically?
Lazar
From: equinox-dev-bounces@xxxxxxxxxxx [mailto:equinox-dev-bounces@xxxxxxxxxxx] On Behalf Of Thomas Watson
Sent: Wednesday, July 08,
2009 4:22 PM
To: Equinox development mailing list
Subject:
Re: [equinox-dev] Getting info for dynamic imports through the console
The diag command only shows info on why a bundle could not
resolve. Dynamic imports never prevent a bundle from resolving. Dynamic import
wires are created (well) dynamically, the bundle command only shows imports for
statically imported packages.
Tom
"Kirchev, Lazar"
---07/08/2009 06:48:41 AM---Hello,
From:
| 
"Kirchev, Lazar" <l.kirchev@xxxxxxx>
|
To:
| 
"Equinox
development mailing list" <equinox-dev@xxxxxxxxxxx>
|
Date:
| 
07/08/2009
06:48 AM
|
Subject:
| 
[equinox-dev]
Getting info for dynamic imports through the
console |
Hello,
I have the
following question regarding dynamic imports info. The bundle <id> console
command does not return the dynamic imports of a bundle, and in the same time
the diag <id> command states that there are no unresolved imports for this
bundle. So is this the intended behavior of the bundle <id> command? Is it
possible to get info through a console command which packages are dynamically
imported by the bundle?
Kind regards,
Lazar Kirchev_______________________________________________
equinox-dev mailing
list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev
_______________________________________________
equinox-dev
mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev
_______________________________________________
equinox-dev mailing
list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev
