commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Honton, Charles" <>
Subject RE: [ALL] Commons Parent reports
Date Wed, 14 Mar 2012 16:27:11 GMT
As a user of commons libraries, I look at several reports.  I'll consult Javadoc first.  In
the case the javadoc is silent about behavior, I look at JXR.  When I am debugging my code's
interaction with the commons library, I want to have the sources available to my IDE, so that
I can step through the commons library.


-----Original Message-----
From: Gilles Sadowski [] 
Sent: Wednesday, March 14, 2012 1:51 AM
Subject: Re: [ALL] Commons Parent reports

On Tue, Mar 13, 2012 at 01:52:32PM -0400, Gary Gregory wrote:
> On Mar 13, 2012, at 12:40, Gilles Sadowski <> wrote:
> >>>
> >>>>> [...]
> >>>>>
> >>>>> The tools are there, but you have to tell people that they _must_
use them.
> >>>>
> >>>> Commons has already enough rules and process. As long as the releases
> >>>> are have clean code I wouldn't be too anal about the commits in
> >>>> between.
> >>>
> >>> I think that the main disagreement is here. Source code must be a clear
> >>> for the _developers_. To put it bluntly, I don't care that the releases
> >>> cleanly formatted code, as almost nobody is going to read those packaged
> >>> sources!
> Au contraire, most users will /only/ look at the source jar because
> that is what you use in the debugger!

Here IMHO you are talking about _developers_.
By users I meant people who include the classes JAR in their classpath.
They will at most look at the API docs.


To unsubscribe, e-mail:
For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message