Suggestion: use library dependencies from local repository (~/.m2/repository) as preferred alternative to `.library-dependencies`

IBM / codenet-minerva-code-analyzer

Java source code (and/or binary) to JSON based system dependency graph generator.

Apache License 2.0

1 stars 3 forks source link

Suggestion: use library dependencies from local repository (~/.m2/repository) as preferred alternative to `.library-dependencies` #33

Open scottkurz opened 2 months ago

scottkurz commented 2 months ago

Copying dependencies to .library-dependencies takes up space and now requires an extra .gitignore or possible clean action.

Since this tool is already Maven-aware could it simply build whatever "classpath" it's using this directory for and point to the JARs in the local ~/.m2/repository. This may require some piece of the Maven lifecycle to have run to download those deps but this is probably already happening.

sinha108 commented 2 months ago

@scottkurz: The .library-dependencies directory is now removed at the end of the analysis run, so it exists only temporarily while the analysis is running (also the directory has been renamed to _library_dependencies); this should avoid the space/clenaup issues you mentioned.