You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by Phil Steitz <ph...@steitz.com> on 2003/12/07 20:29:44 UTC

[general] jars, dlls in CVS

I noticed quite a few Windows DLLs and jar files fly by when I checkout 
out the directory code. I assume that mavenization will eliminate the need 
to store jars in svn.  I don't know exactly what to do about the DLLs, but 
we need to make sure that at the very least, we are not storing or 
distributing anything that we do not have rights to.  Below is a list of 
what find turned up for *.dll and *.jar.  We should remove any 
questionable files (in terms of licensing) from the repo ASAP.

DLLs:
directory/ldap/trunk/installer/bin/cygwin1.dll
directory/ldap/trunk/installer/bin/cygpopt-0.dll
directory/ldap/trunk/berkeley/lib/native/Windows/x86/libdb_java41.dll
directory/ldap/trunk/berkeley/lib/native/Windows/x86/msvci70.dll
directory/ldap/trunk/berkeley/lib/native/Windows/x86/msvcp70.dll
directory/ldap/trunk/berkeley/lib/native/Windows/x86/msvcr70.dll
directory/ldap/trunk/berkeley/lib/native/Windows/x86/libdb41.dll

jars:
directory/ldap/trunk/test/lib/JUnitDoclet.jar
directory/ldap/trunk/test/lib/optional.jar
directory/ldap/trunk/test/lib/junit.jar
directory/ldap/trunk/test/lib/xml-apis.jar
directory/ldap/trunk/test/lib/xercesImpl.jar
directory/ldap/trunk/test/lib/ant.jar
directory/ldap/trunk/installer/lib/xercesImpl.jar
directory/ldap/trunk/installer/lib/junit.jar
directory/ldap/trunk/installer/lib/xml-apis.jar
directory/ldap/trunk/clients/lib/logkit-1.1.jar
directory/ldap/trunk/clients/lib/snacc-2.3.jar
directory/ldap/trunk/clients/lib/avalon-framework-20020713.jar
directory/ldap/trunk/clients/lib/commons-collections.jar
directory/ldap/trunk/clients/lib/excalibur-cli-1.0.jar
directory/ldap/trunk/berkeley/lib/xml-apis.jar
directory/ldap/trunk/berkeley/lib/db.jar
directory/ldap/trunk/berkeley/lib/xercesImpl-2.0.2.jar
directory/ldap/trunk/berkeley/lib/excalibur-configuration-1.0.jar
directory/ldap/trunk/modjdbc/lib/drivers/oracle/classes12.jar
directory/ldap/trunk/modjdbc/lib/drivers/oracle/classes111.jar
directory/ldap/trunk/modjdbc/lib/drivers/mysql/mysql-connector-java-2.0.14-bin.jar
directory/ldap/trunk/modjdbc/lib/drivers/sqlserver/jtds-0.4.jar
directory/ldap/trunk/modjdbc/lib/avalon-excalibur-4.1.jar
directory/ldap/trunk/common-test/lib/commons-lang-1.1-dev.jar
directory/ldap/trunk/replication/lib/openjms-0.7.2.jar
directory/ldap/trunk/replication/lib/jms_1.0.2a.jar
directory/ldap/trunk/replication/lib/openjms-client-0.7.2.jar
directory/ldap/trunk/replication/lib/exolabcore-0.3.3.jar
directory/ldap/trunk/modjdbm/lib/jdbm-0.12.jar

Phil

RE: [general] jars, dlls in CVS

Posted by Alex Karasulu <ao...@bellsouth.net>.
These were removed.  I don't think anything else is an issue.
But just in case can others do a double take again.

> directory/ldap/trunk/berkeley/lib/native/Windows/x86/libdb_java41.dll
> directory/ldap/trunk/berkeley/lib/native/Windows/x86/msvci70.dll
> directory/ldap/trunk/berkeley/lib/native/Windows/x86/msvcp70.dll
> directory/ldap/trunk/berkeley/lib/native/Windows/x86/msvcr70.dll
> directory/ldap/trunk/berkeley/lib/native/Windows/x86/libdb41.dll
> directory/ldap/trunk/clients/lib/snacc-2.3.jar
> directory/ldap/trunk/berkeley/lib/db.jar
> directory/ldap/trunk/modjdbc/lib/drivers/oracle/classes12.jar
> directory/ldap/trunk/modjdbc/lib/drivers/oracle/classes111.jar
> directory/ldap/trunk/modjdbc/lib/drivers/sqlserver/jtds-0.4.jar
> directory/ldap/trunk/installer/bin/cygwin1.dll
> directory/ldap/trunk/installer/bin/cygpopt-0.dll

Alex

RE: [general] jars, dlls in CVS

Posted by Alex Karasulu <ao...@bellsouth.net>.
> directory/ldap/trunk/modjdbc/lib/drivers/mysql/mysql-connector-java-
> 2.0.14-bin.jar

Besides this one up here which I missed on the original list, all these 
below should be ok.  

BTW these are a result of a full import of the sf.net CVS repo and were not
intentially added.  In fact I had to blow away a CVSROOT directory as well.

> The ones that I was referring to were the ones on the list in the lower
> part of Alex's mail, which I presume we were planning to leave in until
> mavenization was complete:
> 
> directory/ldap/trunk/test/lib/JUnitDoclet.jar
> directory/ldap/trunk/test/lib/optional.jar
> directory/ldap/trunk/test/lib/junit.jar
> directory/ldap/trunk/test/lib/xml-apis.jar
> directory/ldap/trunk/test/lib/xercesImpl.jar
> directory/ldap/trunk/test/lib/ant.jar
> directory/ldap/trunk/installer/lib/xercesImpl.jar
> directory/ldap/trunk/installer/lib/junit.jar
> directory/ldap/trunk/installer/lib/xml-apis.jar
> directory/ldap/trunk/clients/lib/logkit-1.1.jar
> directory/ldap/trunk/clients/lib/avalon-framework-20020713.jar
> directory/ldap/trunk/clients/lib/commons-collections.jar
> directory/ldap/trunk/clients/lib/excalibur-cli-1.0.jar
> directory/ldap/trunk/berkeley/lib/xml-apis.jar
> directory/ldap/trunk/berkeley/lib/db.jar
> directory/ldap/trunk/berkeley/lib/xercesImpl-2.0.2.jar
> directory/ldap/trunk/berkeley/lib/excalibur-configuration-1.0.jar
> directory/ldap/trunk/modjdbc/lib/avalon-excalibur-4.1.jar
> directory/ldap/trunk/common-test/lib/commons-lang-1.1-dev.jar
> directory/ldap/trunk/replication/lib/openjms-0.7.2.jar
> directory/ldap/trunk/replication/lib/jms_1.0.2a.jar
> directory/ldap/trunk/replication/lib/openjms-client-0.7.2.jar
> directory/ldap/trunk/replication/lib/exolabcore-0.3.3.jar
> directory/ldap/trunk/modjdbm/lib/jdbm-0.12.jar
> 
> Phil

Re: [general] jars, dlls in CVS

Posted by Phil Steitz <ph...@steitz.com>.
Peter Donald wrote:
> On Mon, 8 Dec 2003 07:47 am, Henri Yandell wrote:
> 
>>Agreed. Make sure when you remove them, that they are forcibly deleted on
>>the machine and not just cvs remove'd. I imagine the sqlserver jar is also
>>bad.
> 
> 
> jtds is BSD-L licensed and fine as long as you also distribute the license 
> with it. The berley dlls are also fine to distribute IIRC (if licenses are 
> included) but cygwin is very suspect.
> 

The ones that I was referring to were the ones on the list in the lower 
part of Alex's mail, which I presume we were planning to leave in until 
mavenization was complete:

directory/ldap/trunk/test/lib/JUnitDoclet.jar
directory/ldap/trunk/test/lib/optional.jar
directory/ldap/trunk/test/lib/junit.jar
directory/ldap/trunk/test/lib/xml-apis.jar
directory/ldap/trunk/test/lib/xercesImpl.jar
directory/ldap/trunk/test/lib/ant.jar
directory/ldap/trunk/installer/lib/xercesImpl.jar
directory/ldap/trunk/installer/lib/junit.jar
directory/ldap/trunk/installer/lib/xml-apis.jar
directory/ldap/trunk/clients/lib/logkit-1.1.jar
directory/ldap/trunk/clients/lib/avalon-framework-20020713.jar
directory/ldap/trunk/clients/lib/commons-collections.jar
directory/ldap/trunk/clients/lib/excalibur-cli-1.0.jar
directory/ldap/trunk/berkeley/lib/xml-apis.jar
directory/ldap/trunk/berkeley/lib/db.jar
directory/ldap/trunk/berkeley/lib/xercesImpl-2.0.2.jar
directory/ldap/trunk/berkeley/lib/excalibur-configuration-1.0.jar
directory/ldap/trunk/modjdbc/lib/drivers/mysql/mysql-connector-java-
2.0.14-bin.jar
directory/ldap/trunk/modjdbc/lib/avalon-excalibur-4.1.jar
directory/ldap/trunk/common-test/lib/commons-lang-1.1-dev.jar
directory/ldap/trunk/replication/lib/openjms-0.7.2.jar
directory/ldap/trunk/replication/lib/jms_1.0.2a.jar
directory/ldap/trunk/replication/lib/openjms-client-0.7.2.jar
directory/ldap/trunk/replication/lib/exolabcore-0.3.3.jar
directory/ldap/trunk/modjdbm/lib/jdbm-0.12.jar

Phil

Re: [general] jars, dlls in CVS

Posted by Peter Donald <pe...@realityforge.org>.
On Mon, 8 Dec 2003 07:47 am, Henri Yandell wrote:
> Agreed. Make sure when you remove them, that they are forcibly deleted on
> the machine and not just cvs remove'd. I imagine the sqlserver jar is also
> bad.

jtds is BSD-L licensed and fine as long as you also distribute the license 
with it. The berley dlls are also fine to distribute IIRC (if licenses are 
included) but cygwin is very suspect.

-- 
Cheers,

Peter Donald
------------------------------------------------------
 Mark Twain: "In the real world, the right thing never
happens in the right place at the right time. It is 
the task of journalists and historians to rectify 
this error."
------------------------------------------------------

Re: [general] jars, dlls in CVS

Posted by Henri Yandell <ba...@generationjava.com>.

On Mon, 8 Dec 2003, Peter Donald wrote:

> On Mon, 8 Dec 2003 07:32 am, Phil Steitz wrote:
> > >>directory/ldap/trunk/installer/bin/cygwin1.dll
> > >>directory/ldap/trunk/installer/bin/cygpopt-0.dll
> > >>directory/ldap/trunk/berkeley/lib/native/Windows/x86/libdb_java41.dll
> > >>directory/ldap/trunk/berkeley/lib/native/Windows/x86/msvci70.dll
> > >>directory/ldap/trunk/berkeley/lib/native/Windows/x86/msvcp70.dll
> > >>directory/ldap/trunk/berkeley/lib/native/Windows/x86/msvcr70.dll
> > >>directory/ldap/trunk/berkeley/lib/native/Windows/x86/libdb41.dll
> > >>directory/ldap/trunk/modjdbc/lib/drivers/sqlserver/jtds-0.4.jar
> > >>directory/ldap/trunk/modjdbc/lib/drivers/oracle/classes12.jar
> > >>directory/ldap/trunk/modjdbc/lib/drivers/oracle/classes111.jar
> > >>directory/ldap/trunk/clients/lib/snacc-2.3.jar
> > >
> > > Here this stuff will slowly make its way out of the
> > > repo as we switch some existing ant builds over to
> > > maven.
> >
> > Thanks.  Are you sure that all of these jars are OK to distribute?
>
> Some are NOT and should not be in Apaches repos. In particular the oracle
> classes*.jarand snacc jar can not be distributed.

Agreed. Make sure when you remove them, that they are forcibly deleted on
the machine and not just cvs remove'd. I imagine the sqlserver jar is also
bad.

What are the rules on dll distribution? I assume many of those we cannot
do, including cygwin which I assume is GPL.

Basicallly everything Phil lists should be forcibly deleted from
minotaur's CVS repo. Good catch Phil.

Hen

Re: [general] jars, dlls in CVS

Posted by Peter Donald <pe...@realityforge.org>.
On Mon, 8 Dec 2003 07:32 am, Phil Steitz wrote:
> >>directory/ldap/trunk/installer/bin/cygwin1.dll
> >>directory/ldap/trunk/installer/bin/cygpopt-0.dll
> >>directory/ldap/trunk/berkeley/lib/native/Windows/x86/libdb_java41.dll
> >>directory/ldap/trunk/berkeley/lib/native/Windows/x86/msvci70.dll
> >>directory/ldap/trunk/berkeley/lib/native/Windows/x86/msvcp70.dll
> >>directory/ldap/trunk/berkeley/lib/native/Windows/x86/msvcr70.dll
> >>directory/ldap/trunk/berkeley/lib/native/Windows/x86/libdb41.dll
> >>directory/ldap/trunk/modjdbc/lib/drivers/sqlserver/jtds-0.4.jar
> >>directory/ldap/trunk/modjdbc/lib/drivers/oracle/classes12.jar
> >>directory/ldap/trunk/modjdbc/lib/drivers/oracle/classes111.jar
> >>directory/ldap/trunk/clients/lib/snacc-2.3.jar
> >
> > Here this stuff will slowly make its way out of the
> > repo as we switch some existing ant builds over to
> > maven.
>
> Thanks.  Are you sure that all of these jars are OK to distribute?

Some are NOT and should not be in Apaches repos. In particular the oracle 
classes*.jarand snacc jar can not be distributed.


-- 
Cheers,

Peter Donald
Non-Reciprocal Laws of Expectations:
        Negative expectations yield negative results.
        Positive expectations yield negative results.

Re: [general] jars, dlls in CVS

Posted by Phil Steitz <ph...@steitz.com>.
Alex Karasulu wrote:
> All this needs to go.  I'll blow it way now.
> 
> 
>>directory/ldap/trunk/installer/bin/cygwin1.dll
>>directory/ldap/trunk/installer/bin/cygpopt-0.dll
>>directory/ldap/trunk/berkeley/lib/native/Windows/x86/libdb_java41.dll
>>directory/ldap/trunk/berkeley/lib/native/Windows/x86/msvci70.dll
>>directory/ldap/trunk/berkeley/lib/native/Windows/x86/msvcp70.dll
>>directory/ldap/trunk/berkeley/lib/native/Windows/x86/msvcr70.dll
>>directory/ldap/trunk/berkeley/lib/native/Windows/x86/libdb41.dll
>>directory/ldap/trunk/modjdbc/lib/drivers/sqlserver/jtds-0.4.jar
>>directory/ldap/trunk/modjdbc/lib/drivers/oracle/classes12.jar
>>directory/ldap/trunk/modjdbc/lib/drivers/oracle/classes111.jar
>>directory/ldap/trunk/clients/lib/snacc-2.3.jar
> 
> 
> Here this stuff will slowly make its way out of the 
> repo as we switch some existing ant builds over to 
> maven.
> 

Thanks.  Are you sure that all of these jars are OK to distribute?

If not, we should probably blow away the questionable ones in the repo, 
but distribute the list (with expected locations) so folks can grab for 
themselves and build and add ask svn to ignore them.  Obviously, there is 
no problem with the Apache stuff -- I don't recognize some of the others, 
though, and we need to be careful about this kind of thing.

Phil

> 
>>directory/ldap/trunk/test/lib/JUnitDoclet.jar
>>directory/ldap/trunk/test/lib/optional.jar
>>directory/ldap/trunk/test/lib/junit.jar
>>directory/ldap/trunk/test/lib/xml-apis.jar
>>directory/ldap/trunk/test/lib/xercesImpl.jar
>>directory/ldap/trunk/test/lib/ant.jar
>>directory/ldap/trunk/installer/lib/xercesImpl.jar
>>directory/ldap/trunk/installer/lib/junit.jar
>>directory/ldap/trunk/installer/lib/xml-apis.jar
>>directory/ldap/trunk/clients/lib/logkit-1.1.jar
>>directory/ldap/trunk/clients/lib/avalon-framework-20020713.jar
>>directory/ldap/trunk/clients/lib/commons-collections.jar
>>directory/ldap/trunk/clients/lib/excalibur-cli-1.0.jar
>>directory/ldap/trunk/berkeley/lib/xml-apis.jar
>>directory/ldap/trunk/berkeley/lib/db.jar
>>directory/ldap/trunk/berkeley/lib/xercesImpl-2.0.2.jar
>>directory/ldap/trunk/berkeley/lib/excalibur-configuration-1.0.jar
>>directory/ldap/trunk/modjdbc/lib/drivers/mysql/mysql-connector-java-
>>2.0.14-bin.jar
>>directory/ldap/trunk/modjdbc/lib/avalon-excalibur-4.1.jar
>>directory/ldap/trunk/common-test/lib/commons-lang-1.1-dev.jar
>>directory/ldap/trunk/replication/lib/openjms-0.7.2.jar
>>directory/ldap/trunk/replication/lib/jms_1.0.2a.jar
>>directory/ldap/trunk/replication/lib/openjms-client-0.7.2.jar
>>directory/ldap/trunk/replication/lib/exolabcore-0.3.3.jar
>>directory/ldap/trunk/modjdbm/lib/jdbm-0.12.jar
> 
> 
> Alex
> 
> 
> 
>

RE: [general] jars, dlls in CVS

Posted by Alex Karasulu <ao...@bellsouth.net>.
All this needs to go.  I'll blow it way now.

> directory/ldap/trunk/installer/bin/cygwin1.dll
> directory/ldap/trunk/installer/bin/cygpopt-0.dll
> directory/ldap/trunk/berkeley/lib/native/Windows/x86/libdb_java41.dll
> directory/ldap/trunk/berkeley/lib/native/Windows/x86/msvci70.dll
> directory/ldap/trunk/berkeley/lib/native/Windows/x86/msvcp70.dll
> directory/ldap/trunk/berkeley/lib/native/Windows/x86/msvcr70.dll
> directory/ldap/trunk/berkeley/lib/native/Windows/x86/libdb41.dll
> directory/ldap/trunk/modjdbc/lib/drivers/sqlserver/jtds-0.4.jar
> directory/ldap/trunk/modjdbc/lib/drivers/oracle/classes12.jar
> directory/ldap/trunk/modjdbc/lib/drivers/oracle/classes111.jar
> directory/ldap/trunk/clients/lib/snacc-2.3.jar

Here this stuff will slowly make its way out of the 
repo as we switch some existing ant builds over to 
maven.

> directory/ldap/trunk/test/lib/JUnitDoclet.jar
> directory/ldap/trunk/test/lib/optional.jar
> directory/ldap/trunk/test/lib/junit.jar
> directory/ldap/trunk/test/lib/xml-apis.jar
> directory/ldap/trunk/test/lib/xercesImpl.jar
> directory/ldap/trunk/test/lib/ant.jar
> directory/ldap/trunk/installer/lib/xercesImpl.jar
> directory/ldap/trunk/installer/lib/junit.jar
> directory/ldap/trunk/installer/lib/xml-apis.jar
> directory/ldap/trunk/clients/lib/logkit-1.1.jar
> directory/ldap/trunk/clients/lib/avalon-framework-20020713.jar
> directory/ldap/trunk/clients/lib/commons-collections.jar
> directory/ldap/trunk/clients/lib/excalibur-cli-1.0.jar
> directory/ldap/trunk/berkeley/lib/xml-apis.jar
> directory/ldap/trunk/berkeley/lib/db.jar
> directory/ldap/trunk/berkeley/lib/xercesImpl-2.0.2.jar
> directory/ldap/trunk/berkeley/lib/excalibur-configuration-1.0.jar
> directory/ldap/trunk/modjdbc/lib/drivers/mysql/mysql-connector-java-
> 2.0.14-bin.jar
> directory/ldap/trunk/modjdbc/lib/avalon-excalibur-4.1.jar
> directory/ldap/trunk/common-test/lib/commons-lang-1.1-dev.jar
> directory/ldap/trunk/replication/lib/openjms-0.7.2.jar
> directory/ldap/trunk/replication/lib/jms_1.0.2a.jar
> directory/ldap/trunk/replication/lib/openjms-client-0.7.2.jar
> directory/ldap/trunk/replication/lib/exolabcore-0.3.3.jar
> directory/ldap/trunk/modjdbm/lib/jdbm-0.12.jar

Alex