[Clirr-devel] [ clirr-Feature Requests-1701623 ] Indicate input jar file name in reports

[SourceForge.net <no...@so...>]

Feature Requests item #1701623, was opened at 2007-04-16 17:36
Message generated for change (Comment added) made by lkuehne
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=590802&aid=1701623&group_id=89627

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Nascif Abousalh Neto (nascif)
Assigned to: Nobody/Anonymous (nobody)
Summary: Indicate input jar file name in reports

Initial Comment:
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.


----------------------------------------------------------------------

>Comment By: Lars Kühne (lkuehne)
Date: 2007-04-16 22:55

Message:
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".

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=590802&aid=1701623&group_id=89627