Hi,
2013/2/27 Sergio Fernández <[email protected]> > > > - c3p0 as connection pool (MARMOTTA-111) > If there is no reply by Friday, I will switch the connection pool to the Tomcat connection pool to be safe. The Tomcat JDBC pool seems much simpler to me anyways. > - UnboundID LDAP SDK for Java (awaiting for LEGAL-160) > LDAP support is completely optional anyways and not needed for the build or running of the core system. The question is for me more about deployment to the Maven repository. Of course it would be convenient to simply add a dependency to the LDAP module to your own project if you need it, but I am not sure if it conforms to the Apache guidelines for publishing on the Maven repository. > - Javassist (LGPL) > Javassist is dual-license (at least in the latest version) LGPL/APL and therefore should be fine. Maybe we need to update to the latest version (which in the case of Javassist might cause problems, it rewrites bytecode). We also need to check if this is really needed, it might be a remainder of Hibernate. > - MySQL java connector (according to LEGAL-21, this is runtime and > optional dependency, so should be fine) > Same as for LDAP. It would be convenient for users to be able to include the library in a binary release (war file or installer), and it would be good to be able to use the library in testing. Otherwise there is no real dependency on the MySQL library. > - JBoss Logging (LGPL) > JBoss Logging has been relicensed to APL some months ago, so it should also not be a problem if we upgrade to the most recent version [1]. This is a transitive dependency of Weld/CDI. [1] http://search.maven.org/#artifactdetails%7Corg.jboss.logging%7Cjboss-logging%7C3.1.2.GA%7Cjar > > And, I think, that's it. Do I forget anything else? > Yes, all CDDL licensed libraries need to be identified and mentioned in a NOTICE or LICENSE file [2]. [2] http://www.apache.org/legal/3party.html#criteriaandcategories Greetings, Sebastian
