Best practices for Java libraries (When to split documentation)

[Wolfgang Baer]

Stefan Gybas wrote:
> Wolfgang Baer wrote:
> 
>> The Java policy doesn't specify the javadoc handling. Is there a
>> common sense in pkg-java project when to split an own -doc package
>> out ?
> 
> 
> That's your decision, like for regular packages. If the docs are small, 
> don't split them.

Ok, thats the way I handeld it in the first packaging attempts already.

> 
>> The library is in public domain except two classes. It's no problem
>> to remove this classes and therefore also two inheriting classes.
> 
> 
> If those two classes are not DFSG-free you need to remove them from the 
> source package if you want your package in main or contrib. What's the 
> license for these classes?

Sun - and the given licence is non-transferable !

<Cite>
All classes are released to the public domain and may be used for any
purpose whatsoever without permission or acknowledgment. Portions of the
CopyOnWriteArrayList and ConcurrentReaderHashMap classes are adapted
from Sun JDK source code. These are copyright of Sun Microsystems, Inc,
and are used with their kind permission,  as described in this license.
</Cite>

I will remove them from the source package and rename the source
package to concurrent-dfsg

Thanks,

Wolfgang