Hi, Am 21.11.2012 um 21:08 schrieb Neil Bartlett:
> I have raised FELIX-3773 to track this issue. Thanks. Looking at the references, IMHO for the ASF and thus for the Felix project the question is resolved and the JSON library can be used and re-distributed. The question is, whether for downstream users, this applies as well. IANAL so I cannot answer the question and we never ran into any problem using this library. So, from that POV I would actually prefer to just leave it at that and create the all-in-one build again. Regards Felix > > Regards > Neil > > On Wed, Nov 21, 2012 at 8:02 PM, Neil Bartlett <[email protected]> wrote: > >> Justin, >> >> Wow, yes, I hadn't spotted that. It's was so much more obvious in 4.0... >> >> Houston, we have a problem! >> >> Neil >> >> >> On Wed, Nov 21, 2012 at 7:30 PM, Justin Edelson >> <[email protected]>wrote: >> >>> Neil- >>> Unfortunately, the same license applies to the json.org code embedded in >>> WebConsole 3.0.0 through 3.1.8. >>> >>> Regards, >>> Justin >>> >>> >>> On Wed, Nov 21, 2012 at 2:26 PM, Neil Bartlett <[email protected]> >>> wrote: >>> >>>> Felix, >>>> >>>> I will not be able to use your aggregated bundle, and I think Graham >>> would >>>> not be able to either. The problem is the license for the "org.json" >>>> package which you are proposing to embed and export, which contains the >>>> following unfortunate sentence: >>>> >>>> "The Software shall be used for Good, not Evil" >>>> >>>> While that may sound reasonable, I wish you luck finding two lawyers who >>>> agree on the definitions of "good" and "evil". >>>> >>>> This dependency is why I cannot use Webconsole 4.0, whether or not you >>>> import the package or export yourself. >>>> >>>> Regards, >>>> Neil >>>> >>>> >>>> On Wed, Nov 21, 2012 at 1:20 PM, Graham Charters <[email protected] >>>>> wrote: >>>> >>>>> Thanks, all, for the helpful info. Felix, fwiw, I like your proposal. >>>> The >>>>> purist in me doesn't particularly like aggregate bundles, but the >>>>> pragmatist accepts that they have a place. >>>>> >>>>> Regarding org.json, I looked for the Geronimo bundled version, and >>> there >>>>> was one, but it was for a later version of the library (2009... not >>>> 2007). >>>>> I've not tried building Web Console 4.0.0, so don't know what maven >>>> would >>>>> actually find and use. >>>>> >>>>> Regards, Graham. >>>>> >>>>> >>>>> On 21 November 2012 10:44, Darren <[email protected]> >>> wrote: >>>>> >>>>>> >>>>>>> In the interest of fast deployment, I suggest the Felix project >>>>> revisits >>>>>> this and comes up with a webconsole-all bundle, which exports >>> org.json, >>>>>> Commons IO and Commons FileUpload for ease of deployment. For more >>>>>> controlled, supported, or resource constrained we still have the >>>> default >>>>>> bundle, which only imports. >>>>>> >>>>>> For my (newcomer) situation, that would be ideal as bundles that >>> work >>>> out >>>>>> of the box are more likely to get me experimenting with them. >>>>>> >>>>>> Documentation akin to what PAX web uses would also be helpful. They >>>> have >>>>>> multiple bundles, but explain what each one is for, before >>> introducing >>>>> the >>>>>> bundled bundle (pax-web-jetty-bundle). >>>>>> http://team.ops4j.org/wiki/display/paxweb/Artifacts >>>>>> >>>>>> If Web Console followed a similar strategy, it would also be useful >>> to >>>>>> include more detailed instructions on how to meet the extra >>>> dependencies >>>>>> (as they are not all produced by the Web Console team). The Felix >>>>> commons >>>>>> project looks like the right place to link to download from, but >>> their >>>>>> documentation doesn't include download links. >>>>>> http://felix.apache.org/site/apache-felix-commons.html >>>>>> >>>>>> Would it be possible to get json into Felix commons as well? >>>>>> >>>>>> If you don't have any influence over the Felix commons project, >>> hosting >>>>>> the pom files you contributed to it would allow users to build the >>>>>> dependency bundles themselves. >>>>>> >>>>>> Thanks, >>>>>> Darren >>>>>> >>>>>> >>>>>> >>> --------------------------------------------------------------------- >>>>>> To unsubscribe, e-mail: [email protected] >>>>>> For additional commands, e-mail: [email protected] >>>>>> >>>>>> >>>>> >>>> >>> >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
