Christian Müller ha scritto: > Following the discussion about licensing problems causes me to ask a further > question. > > I am thinking about impelementing the GeoXACML specification for geotools as > GSOC 2009 project. > > http://www.opengeospatial.org/standards/geoxacml > > This is a geospatial extension for XACML (authorization) and uses SAML > (authentification). For both exist OS implementations > > > XACML http://code.google.com/p/enterprise-java-xacml/ > SAML: https://spaces.internet2.edu/display/OpenSAML/Home/ > > Both use the Apache 2.0 License > > Is this a problem ?. If it is, I can stop thinking over the project.
As Adrian points out, there are incompatibility problems with the two licenses. However, I would not be so concerned about those. Let's run a mvn dependency:tree on the geotools main module: ------------------------------------------------------------------------ [INFO] Building Main module [INFO] task-segment: [dependency:tree] [INFO] ------------------------------------------------------------------------ [INFO] [dependency:tree] [INFO] org.geotools:gt-main:jar:2.6-SNAPSHOT [INFO] +- org.geotools:gt-api:jar:2.6-SNAPSHOT:compile [INFO] | \- org.geotools:gt-referencing:jar:2.6-SNAPSHOT:compile [INFO] | +- java3d:vecmath:jar:1.3.1:compile [INFO] | +- commons-pool:commons-pool:jar:1.3:compile [INFO] | \- org.geotools:gt-metadata:jar:2.6-SNAPSHOT:compile [INFO] | +- org.opengis:geoapi:jar:2.2-SNAPSHOT:compile [INFO] | \- net.java.dev.jsr-275:jsr-275:jar:1.0-beta-2:compile [INFO] +- org.geotools:gt-sample-data:jar:2.6-SNAPSHOT:test [INFO] +- com.vividsolutions:jts:jar:1.9:compile [INFO] +- jdom:jdom:jar:1.0:compile [INFO] +- junit:junit:jar:4.4:provided [INFO] +- org.easymock:easymock:jar:2.3:test [INFO] +- commons-beanutils:commons-beanutils:jar:1.7.0:compile [INFO] | \- commons-logging:commons-logging:jar:1.1.1:compile (version managed from 1.0.3) [INFO] +- org.geotools:gt-epsg-wkt:jar:2.6-SNAPSHOT:test [INFO] \- javax.media:jai_core:jar:1.1.3:provided [INFO] ------------------------------------------------------------------------ As you can see, even the main module itself depends on two Apache licensed libraries, commons-pool, and commons-logging. If you look around there are plenty of LGPL java libraries that do use libraries coming from Apache Jakarta projects, and I'm not aware of any trobles ever arose from that. Anyways, I agree that as a community we should consider switching to LGPL 3.0 if that fixes the formal problem with having Apache style dependencies (we can discuss in a separate topic). Cheers Andrea -- Andrea Aime OpenGeo - http://opengeo.org Expert service straight from the developers. ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
