#20 Indicate input jar file name in reports

[Nascif Abousalh Neto]

Clirr allows you to specify multiple jar files at once as input, but the output reports (both text and xml) do not differentiate between them.

In a large code base, the means the consumer of the report might have to do the "detective" work of mapping the packages back to the .jar files that contains them.

[Lars Kühne]

Logged In: YES
user_id=401384
Originator: NO

Nascif, could you provide a use case where this has been a real problem for you? Was it an open source project I could look at? If not, how many jars, how many class files, etc? I'm asking to figure out the priority of this RFE.

Note to implementor: Keep in mind that it's probably not a good idea to hardcode the notion of a "jar" in the output. I'm thinking about IDE plugins where the source file would probably be more appropriate, so each class should have the more general notion of an "origin" instead of a "jar".

[Nascif Abousalh Neto]

Logged In: YES
user_id=263845
Originator: YES

Hi Lars,

Unfortunately it is not in an open source project. My use case it to add Clirr to a "repository scanner" that compares the jar files produced by all the projects in an enterprise against the previous night or week build. In that case, a large number of .jar files might be provided as input at once.

But another, more common use case would be any project that creates multiple jar files as output, that are then aggregated to create a large application. It would be helpful to be able to identify the source of each file listed in the Clirr output.