On Mar 17, 2009, at 7:27 PM, Peter Firmstone wrote:
What are our options? Your thoughts? Are there other options?
1. Find an Apache Licensed compiler rewrite ClassDep?
2. Ask Sun to License the tools.jar code subset under the Apache
License?
3. Move the functionality of ClassDep outside of River. We could
host a project "Java Class Dependency Tool" on SourceForge that
combined ClassDep with Apache v2 License and GPLv2 with Classpath
Exception under GPLv3 with Classpath exception. We can then provide
a download link for that project on the apache river download site?
4. Do nothing for now.
I don't know if it is practical for now, but I've experimented with
rewriting the functionality of ClassDep using a byte code analysis
tool -- I used ASM, but there are others. I thought this produced a
cleaner result and would mean not depending on tools.jar.
- Tim
