Yes, I did presume that the case at hand involved incompatible licensing or the source code could be used in the Apache project without any fuss. A Category B Java Package dependency would be awkward but I presume surmountable.
-----Original Message----- From: Ross Gardler [mailto:rgard...@opendirective.com] Sent: Thursday, September 27, 2012 13:56 To: Dennis Hamilton; dev@community.apache.org Subject: RE: Some clarification needed for Apache Extra projects - Apache Extra in specific Sent from my tablet On Sep 27, 2012 9:51 PM, "Dennis E. Hamilton" <orc...@apache.org> wrote: [ ... ] > 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. > Why? Perhaps you are assuming that all code at extras is incompatibly licensed, that is not the case, or perhaps you have some other reason in mind. Ross > - Dennis > > -----Original Message----- > From: Luciano Resende [mailto:luckbr1...@gmail.com] > Sent: Thursday, September 27, 2012 10:24 > To: dev@community.apache.org > 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/ >
