I'm currently making some experimentation using ASM library to analyse jars in order to identify dependencies.
I would like to end up with a tool (in the form of a taglib) that allows to manage more properly the dependencies of the module. The kind of tool I currently foresee for compile dependencies are: - A task that fail a build is some jar are not required in a compile path. - A task that produce a report helping to identify that a jar is required in the compile path. Then, I would like to dig further into the runtime dependencies. For that, I think it should be possible to write a tool to which we give sets of root classes and methods, and that can deduce the runtime dependencies. In order to resolve the reflection, or some other dynamic call, the tool should be able to use some assertion provided by the user that limit the possible execution path. Such runtime analysis could be used to help to document correct runtime classpath, and could also be used to find dead code in an application. I would like to share the code. However even if such a tool could be a nice companion of ivy, I don't think it should be included directly in ivy. And it doesn't fit into the core of ant neither. So I'm worndering where to place it? We have a sandbox in the ant svn. There is also the apache lab. Or I could start a project on sourceforge, google code or somewhere else. What would you advice? -- Gilles Scokart --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
