Feature/javans improvements

[prabhu]

In deep mode, jar namespaces are retained as properties in the cdx document.
Improved requirements.txt parsing

[prabhu]

@heubeck could you test this branch by passing --deep for both java and war/jar file as path. The resulting cdx document must have a property called Namespaces with all the class names. I am also interested in finding out what happens with shaded jars in case you have any.

[heubeck]

@heubeck could you test this branch by passing --deep for both java and war/jar file as path. The resulting cdx document must have a property called Namespaces with all the class names. I am also interested in finding out what happens with shaded jars in case you have any.

Sorry for my late reply, @prabhu.
Unfortunately (or luckily?) I've neither wars nor (shaded) jars to analyze, just source code repositories.

Will compare some samples with/without --deep analysis, at least it lasts (much) longer to create them :P

Do you think, --deep is a good default parameter, when analyzing source code repos, or should it only be used in special cases?

[prabhu]

You can use with java source as well. Thank you

[heubeck]

You can use with java source as well. Thank you

thx. but run-time is not acceptable for a default arg ;)

[prabhu]

You can use with java source as well. Thank you

thx. but run-time is not acceptable for a default arg ;)

It's a good point. Maybe it's time to revisit dotenv support and accept all arguments via env and config files.

[heubeck]

Maybe it's time to revisit dotenv support and accept all arguments via env and config files.

That would simplify my apps configuration, as I'll pass though custom cdxgen config using my github apps config: https://github.com/MediaMarktSaturn/technolinator/blob/main/docs/Repository_Config.md

[prabhu]

Maybe it's time to revisit dotenv support and accept all arguments via env and config files.

That would simplify my apps configuration, as I'll pass though custom cdxgen config using my github apps config: https://github.com/MediaMarktSaturn/technolinator/blob/main/docs/Repository_Config.md

Interesting idea! Shall we use the config directory structure .config/cdxgen.json and accept the language, package manager, repo, and directory-specific overrides?

[heubeck]

that would be the galactic-problem-solving-solution ;)
maybe without .config path, just .cdxgen.conf or so
any chance not doing .json? 😕

[prabhu]

that would be the galactic-problem-solving-solution ;) maybe without .config path, just .cdxgen.conf or so any chance not doing .json? 😕

The root directories are getting polluted, so there is a movement to promote dotconfig directories. Since cdxgen is a node package json is usually the default format for config files. But noticed that js-yaml is included with the package so we can support both yaml and json?

[heubeck]

yaml or json is great.
.config in the root is also fine, but for directory overrides?