Hi all, following Andy's advice and an internal discussion here with the Stanbol people, I suggest to proceed towards the release as follows: - I will replace c3p0 beginning of next week with the tomcat JDBC connection manager - we configure all optional modules with inappropriate dependencies (ldclient-provider-ldap, mysql tests, ...) so they are only built when a certain maven profile is active; in this way we can avoid them getting deployed anywhere while interested users can still build them themselves
The only "big" task is replacing c3p0, but I expect it to take no longer than a day. :) Greetings, Sebastian 2013/2/27 Andy Seaborne <[email protected]> > 3) Artifacts with licences that are not compatible with the ASF >> policies. I know this block a proper Apache release, also a >> incubating one? >> > > An incubating release is no different to any other release. There are > only "releases". > > Just to note: the headers on the files need to be sorted out but I think > you have the license plugin setup. The exact text is given in: > > http://www.apache.org/legal/**src-headers.html<http://www.apache.org/legal/src-headers.html> > > which is the "granted, no copyright" version. > > There's a tool help: > > http://creadur.apache.org/rat/ > > Are any files exceptions (i.e. third party source code)? > > Andy >
