Luciano's account identifies a clean, bright line between Apache Extras and any
Apache project.
One point of clarification, however, since I see this statement repeatedly.
It is clear that an Apache Extras project should not *deliver* packages or
components on any org.apache.xxx... class path.
*Using* packages and definitions on such class paths is a different story.
Those are usable under provisions of the ALv2 license.
I see no useful purpose in prohibition external code declaring entities having
types defined on an org.apache.xxx class path. Obvious cases are the
provision of interfaces, declaration of subordinate classes, and declaration of
instances of classes all defined for public use in org.apache.xxx... packages.
I think any prohibition on *use* must be in the reverse direction. The Apache
project source code cannot have such dependencies on entities defined in an
org.apache-extras.xxx... package.
- Dennis
-----Original Message-----
From: Luciano Resende [mailto:[email protected]]
Sent: Thursday, September 27, 2012 10:24
To: [email protected]
Subject: Re: Some clarification needed for Apache Extra projects - Apache Extra
in specific
[ ... ]
I'd also mention that the Apache Extras projects should not use
org.apache.xxx packages, but org.apache-extras.xxx package.
[ ... ]
--
Luciano Resende
http://people.apache.org/~lresende
http://twitter.com/lresende1975
http://lresende.blogspot.com/
