Hi Vincent,
I'm +0 on this. The minor drawback is the even longer package names and
that we once again will fragment big parts of the CVS history. Another
option would be to state that only documented API is public API, and
then exclude every non-public API class from the javadoc generation.
-
I'm +1 for this refactoring, though I probably won't have time to help.
Cheers,
Nick
On 10/31/03 1:00 PM, "Vincent Massol" <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I'd like to perform a full overhaul of our package organization. The
> reason is that we are currently not showing our users what API i
Hi,
I'd like to perform a full overhaul of our package organization. The
reason is that we are currently not showing our users what API is public
and what API is not public. Unfortunately, Java does not provide a
built-in solution for this.
I'd like to propose to use the scheme used in Eclipse de
