Markus and I bounced some emails back and forth but we ended up agreeing
that inlining constants was something that the compiler does and there's no
way to stop it. I talked with a friend who has written a Java compiler and
he said that this was necessary, especially in switch/case statements where
the case operand has to be a constant.
So yup, source code analysis seems like the way to go. If we can get those
constants that way we'll be golden. Of course, we'll only be able to get
the constants name - i.e., Foo.BAR - so we'll need to figure out how to get
the package in which the Foo class resides. Maybe by poking around the
classpath? Although that would take some time - walking the classpath,
parsing the jar files, etc....
Yours,
Tom Copeland
[EMAIL PROTECTED]
703-317-5193
Jason van Zyl
<jvanzyl@zenp To: Turbine Developers List
<[EMAIL PROTECTED]>
lex.com> cc:
Subject: Re: [maven] update/todo
02/22/2002
10:23 AM
Please
respond to
"Turbine
Developers
List"
On Fri, 2002-02-22 at 10:08, [EMAIL PROTECTED] wrote:
>
> One problem we're going to have with resolving dependencies via bytecode
is
> discussed here - http://importscrubber.sourceforge.net/limitations.html.
I
> definitely think that checking bytecode for dependencies is very useful,
> but it's going to miss things occasionally....
What about a combination of source and bytecode analysis? I can probably
pick off the static constants before they are inlined. Have you talked
to Markus to see if there's anyway around that little problem?
--
jvz.
Jason van Zyl
[EMAIL PROTECTED]
http://tambora.zenplex.org
--
To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>
--------------------------------------------------------------------------
This email may contain confidential and proprietary information which is
for the sole use of the intended recipient. If you received this email in
error, please notify the sender and delete this email from your computer.
Any review, distribution or retransmission of or reliance on this email by
anyone other than the intended recipient is forbidden.
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
