CVS jcifs/debian/patches

Wolfgang B??r wbaer-guest at haydn.debian.org
Wed Sep 21 18:13:04 UTC 2005 

Update of /cvsroot/pkg-java/jcifs/debian/patches
In directory haydn:/tmp/cvs-serv15649/debian/patches

Modified Files:
	01_build_xml.patch 02_index_doc_relative.patch 
Log Message:
jcifs (1.2.3-1) unstable; urgency=low

  * New upstream release
  * Upload to unstable
  * Registered documentation with doc-base
  * libant1.6-java to ant transition
  * Updated FSF address
  * Fixed double spaces in description to fix linda warning
  * Standards-Version 3.6.2 (no changes)


--- /cvsroot/pkg-java/jcifs/debian/patches/01_build_xml.patch	2005/05/06 11:16:18	1.1.1.1
+++ /cvsroot/pkg-java/jcifs/debian/patches/01_build_xml.patch	2005/09/21 18:13:04	1.2
@@ -1,20 +1,11 @@
---- build.xml.orig	2005-02-11 04:30:21.000000000 +0100
-+++ build.xml	2005-02-19 13:53:31.000000000 +0100
-@@ -80,10 +80,16 @@
-         <!--copy file="docs/allclasses-frame.html" tofile="docs/api/allclasses-frame.html" overwrite="yes"/-->
-     </target>
- 
--    <target name="all" depends="jar,docs,javadoc"/>
-+    <target name="all" depends="jar,javadoc"/>
+--- build.xml.orig	2005-09-11 17:16:07.000000000 +0200
++++ build.xml	2005-09-11 17:16:30.000000000 +0200
+@@ -47,7 +47,7 @@
  
-     <target name="clean">
-         <delete dir="build" quiet="true"/>
-+	 <delete quiet="true">
-+            <fileset dir=".">
-+             <include name="jcifs-${version}.jar"/>
-+            </fileset>
-+        </delete>
-+        <delete dir="docs/api" quiet="true"/>												 
+     <target name="compile" depends="dependencies">
+         <mkdir dir="build"/>
+-        <javac srcdir="src" destdir="build" debug="on"/>
++        <javac srcdir="src" destdir="build" debug="on" target="1.3"/>
+         <copy file="src/jcifs/util/mime.map" tofile="build/jcifs/util/mime.map" overwrite="yes"/>
+         <copy file="src/jcifs/http/ne.css" tofile="build/jcifs/http/ne.css" overwrite="yes"/>
      </target>
- 
-     <target name="allclean" depends="clean">
--- /cvsroot/pkg-java/jcifs/debian/patches/02_index_doc_relative.patch	2005/05/06 11:16:18	1.1.1.1
+++ /cvsroot/pkg-java/jcifs/debian/patches/02_index_doc_relative.patch	2005/09/21 18:13:04	1.2
@@ -1,5 +1,5 @@
---- docs/index.html.orig	2005-02-11 14:55:22.000000000 +0100
-+++ docs/index.html	2005-02-11 15:22:01.000000000 +0100
+--- docs/index.html.orig	2005-08-24 19:34:14.000000000 +0200
++++ docs/index.html	2005-09-11 17:10:20.000000000 +0200
 @@ -88,28 +88,26 @@
  <TR>
  <TD class="leftpane" width="350" valign="top">
@@ -19,10 +19,10 @@
  <br>
  <h2>Developer Information</h2>
 -<a href="src/docs/api/">JCIFS API Documentation</a>
-+<a href="api/">JCIFS API Documentation</a>
++<a href="api/index.html">JCIFS API Documentation</a>
  <br>
 -<a href="src/docs/api/overview-summary.html#scp">Setting Client Properties</a>
-+<a href="api/overview-summary.html#scp">Setting Client Properties</a>
++<a href="overview.html#scp">Setting Client Properties</a>
  <br>
 -<a href="src/docs/resolver.html">Setting Name Resolution Properties</a>
 +<a href="resolver.html">Setting Name Resolution Properties</a>
@@ -38,58 +38,32 @@
  <br>
  <a href="http://www.gnu.org/licenses/lgpl.html">JCIFS is Licensed Under the LGPL</a>
  <br>
-@@ -198,9 +196,7 @@
- <h2>Other</h2>
- <a href="http://lists.samba.org/listinfo/jcifs">Join the JCIFS Mailing List</a>
+@@ -206,7 +204,7 @@
+ <br>
+ <a href="src/src/jcifs/">Browse the Source</a>
  <br>
--<a href="src/src/jcifs/">Browse the Source</a>
--<br>
 -<a href="src/docs/batching.html">Batching</a>
 +<a href="batching.html">Batching</a>
  <br>
  <a href="http://www.fsf.org/copyleft/lgpl.html">GNU Library General Public License</a>
  <br>
-@@ -296,13 +292,13 @@
- <ul>
- 
- <li>
--The <a href="src/docs/ntlmhttpauth.html">NTLM HTTP Authentication Filter</a>, which adds easy Single Sign On (SSO) functionality to Java Servlet containers, is clearly the most popular feature of JCIFS. Eric did a great job of deciphering the details of <a href="http://davenport.sourceforge.net/ntlm.html">that protocol</a>. The filter is mind-numbingly easy to install as all it requires is the JCIFS jar and a filter section in your <a href="view-source:http://jcifs.samba.org/src/examples/web.xml">web.xml</a> with two or three init parameters [1].
-+The <a href="ntlmhttpauth.html">NTLM HTTP Authentication Filter</a>, which adds easy Single Sign On (SSO) functionality to Java Servlet containers, is clearly the most popular feature of JCIFS. Eric did a great job of deciphering the details of <a href="http://davenport.sourceforge.net/ntlm.html">that protocol</a>. The filter is mind-numbingly easy to install as all it requires is the JCIFS jar and a filter section in your <a href="view-source:http://jcifs.samba.org/src/examples/web.xml">web.xml</a> with two or three init parameters [1].
- </li>
- <li>
- The performance of JCIFS is one of its more surprising achievements. Consider the client can enumerate 5GB of files and directories in less than 10 seconds [2]. To reduce memory usage and increase concurrency JCIFS automatically reuses existing transports and sessions. One nice artifact of this design is that the NTLM HTTP Authentication Filter scales to thousands of active clients. And because the negotiated credentials are cached in the user's HTTP session the number of concurrent user's supported can be many times greater than that.
- </li>
- <li>
--The <a href="src/docs/api/jcifs/smb/SmbFile.html#copyTo(jcifs.smb.SmbFile)">SmbFile.copyTo()</a> method is a venerable feature in itself. All file and directory attributes and timestamps are mirrored perfectly [3]. It employs an extra thread to write data while the next read operation is in progress. This optimization makes JCIFS the fastest client available for copying large trees of files and directories across hosts (neither of which needs to be the local machine).
-+The <a href="api/jcifs/smb/SmbFile.html#copyTo(jcifs.smb.SmbFile)">SmbFile.copyTo()</a> method is a venerable feature in itself. All file and directory attributes and timestamps are mirrored perfectly [3]. It employs an extra thread to write data while the next read operation is in progress. This optimization makes JCIFS the fastest client available for copying large trees of files and directories across hosts (neither of which needs to be the local machine).
- </li>
- <li>
- Accessing DFS volumes (sub-trees of files and directories that actually reside on another host) is fully transparent to the user. The client may be redirected multiple times in the middle of any operation. After a redirection has occurred the mapping is cached but the cache is only queried for transports that indicate they host DFS volumes.
-@@ -311,22 +307,22 @@
- SMB signing is robust and negotiated automatically with servers that require it.
- </li>
- <li>
--The <a href="src/docs/api/jcifs/smb/SmbRandomAccessFile.html">SmbRandomAccessFile</a> implementation is a complete drop in replacement for the standard java.io.RandomAccessFile. When opened with SmbFile.FILE_NO_SHARE share access this class is a legitimate database API.
-+The <a href="api/jcifs/smb/SmbRandomAccessFile.html">SmbRandomAccessFile</a> implementation is a complete drop in replacement for the standard java.io.RandomAccessFile. When opened with SmbFile.FILE_NO_SHARE share access this class is a legitimate database API.
- </li>
- <li>
--Named Pipes of all types are fully supported. TransactNamedPipe, CallNamedPipe, and standard file I/O style pipes are all supported using a <a href="http://jcifs.samba.org/src/docs/pipes.html">single generic API</a> that conforms to the InputStream/OutputStream model.
-+Named Pipes of all types are fully supported. TransactNamedPipe, CallNamedPipe, and standard file I/O style pipes are all supported using a <a href="http://jcifs.samba.org/pipes.html">single generic API</a> that conforms to the InputStream/OutputStream model.
- </li>
- <li>
--JCIFS' <a href="src/docs/resolver.html">name resolution capability</a> is very sophisticated. WINS, DNS, NetBIOS broadcast queries, and remote lmhosts files are supported well. Which services and the order in which each service is queried is fully configurable. The name service cache policy is also adjustable.
-+JCIFS' <a href="resolver.html">name resolution capability</a> is very sophisticated. WINS, DNS, NetBIOS broadcast queries, and remote lmhosts files are supported well. Which services and the order in which each service is queried is fully configurable. The name service cache policy is also adjustable.
- </li>
- <li>
- JCIFS implements the <a href="http://www.ietf.org/internet-drafts/draft-crhertel-smb-url-07.txt">SMB URL Draft Specification V07</a> and processes all SMB URLs through an SMB URL proticol handler. This same handler is used to build standard java.net.URL objects which means once the protocol handler is registered SMB URLs can be used with any application that uses URLs (e.g. -Djava.rmi.server.codebase=smb://mymachine/c/download/myapp.jar).
- </li>
- 
- </ul>
--Other features include NTLM and LMv2 Authentication [4], optimal request batching, <a href="ntstatus.txt">NT STATUS codes</a>, full transactions, large file support, Unicode support from the ground up [5], NTLM HTTP <a href="src/docs/httpclient.html">authentication wrappers for HTTP and HTTPS clients</a>, a simple logging facility, and extensive documentation. If that's not enough, there's always <a href="http://sourceforge.net/projects/jcifs-ext/">jcifs-ext</a> where bleeding edge JCIFS extensions live.
-+Other features include NTLM and LMv2 Authentication [4], optimal request batching, <a href="ntstatus.txt">NT STATUS codes</a>, full transactions, large file support, Unicode support from the ground up [5], NTLM HTTP <a href="httpclient.html">authentication wrappers for HTTP and HTTPS clients</a>, a simple logging facility, and extensive documentation. If that's not enough, there's always <a href="http://sourceforge.net/projects/jcifs-ext/">jcifs-ext</a> where bleeding edge JCIFS extensions live.
- <p></p>
--But the best feature of JCIFS is the simplicity of <a href="src/docs/api/">the API</a> itself. We have diligently resisted "feature creep". The SMB URL allows addressing resources with wonderful ease. The SmbFile class is a drop in replacement for java.io.File so if you know how to use that, you know how to use JCIFS.
-+But the best feature of JCIFS is the simplicity of <a href="api/">the API</a> itself. We have diligently resisted "feature creep". The SMB URL allows addressing resources with wonderful ease. The SmbFile class is a drop in replacement for java.io.File so if you know how to use that, you know how to use JCIFS.
- <p></p>
- JCIFS is now one of the most sophisticated and powerful CIFS clients available free or otherwise. It is used in production environments by many large commercial organizations and the Open Source model has worked well for us as these users have contibuted valuable feekback that has made JCIFS rock solid.
- <p></p>
+@@ -225,19 +223,6 @@
+ <BR>
+ A mistake in the 1.2.2 release broke port 445 communication entirely. It has been fixed. The exact error (with a sufficiently high loglevel) was "Invalid payload size: 1".
+ <P></P>
+-<script type="text/javascript"><!--
+-google_ad_client = "pub-9339567651298204";
+-google_ad_width = 728;
+-google_ad_height = 90;
+-google_ad_format = "728x90_as";
+-google_ad_type = "text";
+-google_ad_channel ="";
+-google_color_border = "E0E0FF";
+-google_color_bg = "FFFFFF";
+-google_color_link = "000080";
+-google_color_url = "808080";
+-google_color_text = "000000";
+-//--></script><script src="http://pagead2.googlesyndication.com/pagead/show_ads.js" type="text/javascript"></script>
+ <P></P>
+ <EM>jcifs-1.2.2 released / Exception "cannot assign requested address" Fixed, Clusters, NetApp Filer, and More</EM>
+ <BR>

More information about the pkg-java-commits mailing list