incubator-jspwiki-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrew Jaquith <>
Subject Re: question on third party libraries license
Date Wed, 03 Sep 2008 13:21:57 GMT
That is true... That said, there is nothing stopping us from using  
another tool (gpl/lgpl) if it is already available at runtime...

On Sep 3, 2008, at 8:52 AM, Janne Jalkanen <>  

> I think the Apache policy is quite clear: LGPL and GPL cannot be
> included in ASF projects.
> /Janne
> On Wed, Sep 03, 2008 at 11:38:15AM +0200, Juan Pablo Santos RodrĂ­gue 
> z wrote:
>> Hi all,
>> recently found apiviz <>, a doclet  
>> which
>> adds UML class diagrams to javadocs, at package and class levels.  
>> It can be
>> integrated easely with <javadoc>'s Ant task, and generated javadocs  
>> look
>> very nice (example<

>> >)
>> so, I thought it may be can included (got it running inside jspwiki's
>> build.xml last night). I'm only concerned about it's being lgpl  
>> licensed, so
>> I'm not very sure if we're allowed to use it. Also, this doclet  
>> relies on
>> graphviz <> for diagram generation, which is  
>> CPL
>> licensed.
>> So, the questions are: first, do you think this it is worth having?  
>> if
>> graphviz isn't found, then the doclet falls back to standard javadoc
>> generation, so if you don't want to use it you're not forced to.  
>> And second,
>> how does the license of this type of external libraries affect  
>> JSPWiki
>> (i.e.: when can we use them)?: in this case we are using a (possibly)
>> license-conflicting library to generate javadocs, but apiviz is not  
>> part of
>> them, it is used to *generate* them. Don't know if I'm explaining  
>> clearly..
>> I'm also thinking of cobertura right know, which could be another  
>> nicety to
>> add, but it's GPL licensed.
>> regards,
>> jp

View raw message