And that means that we can't have it in SVN. However, it is okay if
the user dynamically loads and installs the library/app after getting
the build or source from ASF.
/Janne
On Sep 3, 2008, at 16:21 , Andrew Jaquith wrote:
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 <[EMAIL PROTECTED]>
wrote:
I think the Apache policy is quite clear: LGPL and GPL cannot be
included in ASF projects.
http://www.apache.org/legal/resolved.html
/Janne
On Wed, Sep 03, 2008 at 11:38:15AM +0200, Juan Pablo Santos
Rodríguez wrote:
Hi all,
recently found apiviz <http://code.google.com/p/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<http://www.jboss.org/file-access/default/
members/netty/freezone/api/3.0/index.html>)
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 <http://www.graphviz.org> 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
