Re: Fortress IP clearance
Hi, yesterday, I imported the Fortress core pom.xml into Luna (eclipse) which gives the list of libs the fukll project depends on (including transitive deps). Here is the (impressive) list : antlr/antlr/2.7.7/antlr-2.7.7.jar avalon-framework/avalon-framework/4.1.4/avalon-framework-4.1.4.jar bsf/bsf/2.4.0/bsf-2.4.0.jar com/adobe/xmp/xmpcore/5.1.2/xmpcore-5.1.2.jar com/drewnoakes/metadata-extractor/2.6.2/metadata-extractor-2.6.2.jar com/fifesoft/rsyntaxtextarea/2.5.1/rsyntaxtextarea-2.5.1.jar com/googlecode/juniversalchardet/juniversalchardet/1.0.3/juniversalchardet-1.0.3.jar com/googlecode/mp4parser/isoparser/1.0-RC-1/isoparser-1.0-RC-1.jar com/thoughtworks/xstream/xstream/1.4.4/xstream-1.4.4.jar com/unboundid/unboundid-ldapsdk/2.3.3/unboundid-ldapsdk-2.3.3.jar commons-beanutils/commons-beanutils/1.7.0/commons-beanutils-1.7.0.jar commons-beanutils/commons-beanutils-core/1.8.0/commons-beanutils-core-1.8.0.jar commons-codec/commons-codec/1.2/commons-codec-1.2.jar commons-collections/commons-collections/3.2.1/commons-collections-3.2.1.jar commons-configuration/commons-configuration/1.6/commons-configuration-1.6.jar commons-httpclient/commons-httpclient/3.1/commons-httpclient-3.1.jar commons-io/commons-io/2.4/commons-io-2.4.jar commons-jexl/commons-jexl/1.1/commons-jexl-1.1.jar commons-lang/commons-lang/2.4/commons-lang-2.4.jar commons-logging/commons-logging/1.1.1/commons-logging-1.1.1.jar commons-net/commons-net/3.3/commons-net-3.3.jar commons-pool/commons-pool/1.6/commons-pool-1.6.jar de/l3s/boilerpipe/boilerpipe/1.1.0/boilerpipe-1.1.0.jar dom4j/dom4j/1.6.1/dom4j-1.6.1.jar edu/ucar/netcdf/4.2-min/netcdf-4.2-min.jar excalibur-datasource/excalibur-datasource/1.1.1/excalibur-datasource-1.1.1.jar excalibur-instrument/excalibur-instrument/1.0/excalibur-instrument-1.0.jar excalibur-logger/excalibur-logger/1.1/excalibur-logger-1.1.jar excalibur-pool/excalibur-pool/1.2/excalibur-pool-1.2.jar javax/activation/activation/1.1/activation-1.1.jar javax/mail/mail/1.5.0-b01/mail-1.5.0-b01.jar javax/ws/rs/jsr311-api/1.1-ea/jsr311-api-1.1-ea.jar jcharts/jcharts/0.7.5/jcharts-0.7.5.jar jdom/jdom/1.0/jdom-1.0.jar junit/junit/4.11/junit-4.11.jar log4j/log4j/1.2.17/log4j-1.2.17.jar logkit/logkit/2.0/logkit-2.0.jar net/sf/ehcache/ehcache-core/2.6.9/ehcache-core-2.6.9.jar net/sf/jtidy/jtidy/r938/jtidy-r938.jar net/sf/opencsv/opencsv/2.3/opencsv-2.3.jar org/apache/ant/ant/1.9.1/ant-1.9.1.jar org/apache/ant/ant-launcher/1.9.1/ant-launcher-1.9.1.jar org/apache/commons/commons-compress/1.5/commons-compress-1.5.jar org/apache/commons/commons-jexl/2.1.1/commons-jexl-2.1.1.jar org/apache/commons/commons-lang3/3.1/commons-lang3-3.1.jar org/apache/cxf/cxf-common-utilities/2.5.10/cxf-common-utilities-2.5.10.jar org/apache/directory/api/api-all/1.0.0-M22/api-all-1.0.0-M22.jar org/apache/directory/server/apacheds-all/2.0.0-M16/apacheds-all-2.0.0-M16.jar org/apache/httpcomponents/httpclient/4.2.6/httpclient-4.2.6.jar org/apache/httpcomponents/httpcore/4.2.5/httpcore-4.2.5.jar org/apache/httpcomponents/httpmime/4.2.6/httpmime-4.2.6.jar org/apache/geronimo/specs/geronimo-jms_1.1_spec/1.1.1/geronimo-jms_1.1_spec-1.1.1.jar org/apache/geronimo/specs/geronimo-stax-api_1.0_spec/1.0.1/geronimo-stax-api_1.0_spec-1.0.1.jar org/apache/jmeter/ApacheJMeter_components/2.11/ApacheJMeter_components-2.11.jar org/apache/jmeter/ApacheJMeter_core/2.11/ApacheJMeter_core-2.11.jar org/apache/jmeter/ApacheJMeter_java/2.11/ApacheJMeter_java-2.11.jar org/apache/jmeter/jorphan/2.11/jorphan-2.11.jar org/apache/james/apache-mime4j-core/0.7.2/apache-mime4j-core-0.7.2.jar org/apache/james/apache-mime4j-dom/0.7.2/apache-mime4j-dom-0.7.2.jar org/apache/mina/mina-core/2.0.7/mina-core-2.0.7.jar org/apache/pdfbox/pdfbox/1.8.1/pdfbox-1.8.1.jar org/apache/pdfbox/fontbox/1.8.1/fontbox-1.8.1.jar org/apache/pdfbox/jempbox/1.8.1/jempbox-1.8.1.jar org/apache/poi/poi/3.9/poi-3.9.jar org/apache/poi/poi-scratchpad/3.9/poi-scratchpad-3.9.jar org/apache/poi/poi-ooxml/3.9/poi-ooxml-3.9.jar org/apache/poi/poi-ooxml-schemas/3.9/poi-ooxml-schemas-3.9.jar org/apache/tika/tika-core/1.4/tika-core-1.4.jar org/apache/tika/tika-parsers/1.4/tika-parsers-1.4.jar org/apache/ws/xmlschema/xmlschema-core/2.0.3/xmlschema-core-2.0.3.jar org/apache/xmlbeans/xmlbeans/2.3.0/xmlbeans-2.3.0.jar org/apache/xmlgraphics/xmlgraphics-commons/1.5/xmlgraphics-commons-1.5.jar org/aspectj/aspectjrt/1.6.11/aspectjrt-1.6.11.jar org/beanshell/bsh/2.0b5/bsh-2.0b5.jar org/bouncycastle/bcmail-jdk15/1.45/bcmail-jdk15-1.45.jar org/bouncycastle/bcmail-jdk15on/1.49/bcmail-jdk15on-1.49.jar org/bouncycastle/bcpkix-jdk15on/1.49/bcpkix-jdk15on-1.49.jar org/bouncycastle/bcprov-jdk15/1.45/bcprov-jdk15-1.45.jar org/bouncycastle/bcprov-jdk15on/1.49/bcprov-jdk15on-1.49.jar org/ccil/cowan/tagsoup/tagsoup/1.2.1/tagsoup-1.2.1.jar org/codehaus/woodstox/stax2-api/3.1.1/stax2-api-3.1.1.jar org/codehaus/woodstox/woodstox-core-asl/4.2.0/woodstox-core-asl-4.2.0.jar org/gagravarr/vorbis-java-core/0.1/vorbis-java-core-0.1.jar
Re: Fortress IP clearance
On 10/15/2014 01:34 AM, Emmanuel Lécharny wrote: At this point, and focusing on Fortress-core only, I wouls suggest we simply get rid of Uboundid dependency, and then we should be good to go. Anyone has another take on this matter ? Seems reasonable, though as previously stated there will be a bit of work to complete the DAO integration with apache ldap API (password policy + a couple of utility entities - suffix and container) to pass all of the junit tests. The realm package is just fortress + a tomcat lib so might be worth doing at same time as core.
Re: Fortress IP clearance
Le 07/10/14 15:30, Shawn McKinney a écrit : Hi Emmanuel, I have accepted the role of committer on private mailing and emailed a copy of ICLA form to the secretary. AFIK these are the sole tasks assigned to me currently. Thanks for the help. Hi Shawn, let's pursue this conversation on the dev mailing list. I'mcurrently filling parts of the IP clearance document, but at some point, I'll need your help. Typically, here are the info I'll need : - the code base URL, with a MD5/SHA checksum, at the very date of the donation (ie, if we have some modification after this date, then they should be retained and injected into teh code base when moved to The ASF repository. All in all, it's a matter of building a zip and sign it, and move it to a place we can download it (can be teh latest release, for instance) - a Corporate CLA (from Joshua tree and Symas) as to be fulfilled and sent to The ASF - The list of all the people having worked on the code base, with their consent - The list of dependencies with their licence have to be checked to be sure they are compatible (ie, Apache, BSD, Artistic, MIT/X, MIT/W3C, MPL 1.1, or something with essentially the same terms). Tell me what item you can deal with ! Thanks !
Re: Fortress IP clearance
On 10/08/2014 05:38 AM, Emmanuel Lécharny wrote: Typically, here are the info I'll need : - the code base URL, with a MD5/SHA checksum, at the very date of the donation (ie, if we have some modification after this date, then they should be retained and injected into teh code base when moved to The ASF repository. All in all, it's a matter of building a zip and sign it, and move it to a place we can download it (can be teh latest release, for instance) What date are we considering the donation date - today? Assuming it is that, I will download latest snapshot from each of the four repos (core, commander, enmasse, realm), sign, and then upload to one of our file servers. On 10/08/2014 05:38 AM, Emmanuel Lécharny wrote: - a Corporate CLA (from Joshua tree and Symas) as to be fulfilled and sent to The ASF Yes, I will arrange this. On 10/08/2014 05:38 AM, Emmanuel Lécharny wrote: The list of all the people having worked on the code base, with their consent Again yes, no problem. On 10/08/2014 05:38 AM, Emmanuel Lécharny wrote: The list of dependencies with their licence have to be checked to be sure they are compatible (ie, Apache, BSD, Artistic, MIT/X, MIT/W3C, MPL 1.1, or something with essentially the same terms). So here I am assuming the dependencies in the pom.xml are not adequate. Rather we need to list the resolved dependencies, i.e. located in the /lib folder, for each project. I will take care of this too.
Re: Fortress IP clearance
Le 08/10/14 14:21, Shawn McKinney a écrit : On 10/08/2014 05:38 AM, Emmanuel Lécharny wrote: Typically, here are the info I'll need : - the code base URL, with a MD5/SHA checksum, at the very date of the donation (ie, if we have some modification after this date, then they should be retained and injected into teh code base when moved to The ASF repository. All in all, it's a matter of building a zip and sign it, and move it to a place we can download it (can be teh latest release, for instance) What date are we considering the donation date - today? Assuming it is that, I will download latest snapshot from each of the four repos (core, commander, enmasse, realm), sign, and then upload to one of our file servers. Well, the date is not important. What is important is that the zip you sign will be the one we will take the date from. What I meant was that you can't say teh code is donated on april first and provide a zip with source dating from may stj, with many changes since 01/04. In other words, produce the zip, and we use the production date. On 10/08/2014 05:38 AM, Emmanuel Lécharny wrote: - a Corporate CLA (from Joshua tree and Symas) as to be fulfilled and sent to The ASF Yes, I will arrange this. Cool. On 10/08/2014 05:38 AM, Emmanuel Lécharny wrote: The list of all the people having worked on the code base, with their consent Again yes, no problem. Cool. On 10/08/2014 05:38 AM, Emmanuel Lécharny wrote: The list of dependencies with their licence have to be checked to be sure they are compatible (ie, Apache, BSD, Artistic, MIT/X, MIT/W3C, MPL 1.1, or something with essentially the same terms). So here I am assuming the dependencies in the pom.xml are not adequate. Rather we need to list the resolved dependencies, i.e. located in the /lib folder, for each project. I will take care of this too. Not sure if the dependencis are not adequate, we just have to be sure that all the dependencies have a compatible license. And of course, the dependencies they themselves depend on...
