[jcifs] jcifs-0.7.0b6 now available
Allen, Michael B (RSCH)
Michael_B_Allen at ml.com
Mon Oct 28 14:30:05 EST 2002
> -----Original Message-----
> From: Matthew Tippett [SMTP:matthew at casero.com]
> Sent: Sunday, October 27, 2002 10:21 PM
> To: Allen, Michael B (RSCH)
> Subject: Re: [jcifs] jcifs-0.7.0b6 now available
> Thanks for getting the release out :) Some immeadiate feedback however.
> With 0.7.0b6 there is a requirement of having a servlet API accessible
> to build the smb target.
Just take http out of the depends clause in build.xml for the smb target. We will ship without it after the betas.
> There still exists the SmbFile("smb://DOMAIN/").listFiles() still
> returns URLs like smb://DOMAIN/HOST/.
Ok. I look into it.
> Do you have a defect tracking system that bugs can be logged against?
> (Sourceforge comes to mind).
No. Please post all bugs/issues to the list.
> Thanks again,
> Allen, Michael B (RSCH) wrote:
> > Not quite released because I have to roll it out and get synced with
> jcifs.samba.org but it's the same package:
> > http://users.erols.com/mballen/jcifs/CHANGES.txt
> > http://users.erols.com/mballen/jcifs/jcifs-0.7.0b6.jar
> > http://users.erols.com/mballen/jcifs/jcifs-0.7.0b6.tgz
> > http://users.erols.com/mballen/jcifs/jcifs-0.7.0b6.zip
> > Ted,
> > All character encoding changes look good. Please let us know how it
> works for you.
> > Sujit,
> > Concurrency issue with copyTo is repaired in this build. Please let us
> know how it works for you.
> > Matthew,
> > IPC$ fix is in. You should have no problem listing smb:// now.
> > Chris,
> > Can you delete files (under src/ anyway) before I upload for sync this
> morning? We're building up cruft that no longer exists in the package.
> The information contained in this message is proprietary of Casero Inc.,
> protected from disclosure, and may be privileged. The information is
> intended to be conveyed only to the designated recipient(s) of the
> message. If the reader of this message is not the intended recipient,
> you are hereby notified that any dissemination, use, distribution or
> copying of this communication is strictly prohibited and may be
> unlawful. If you have received this communication in error, please
> notify us immediately by replying to the message and deleting it from
> your computer. Thank you.
More information about the jcifs