Re: Status of the Sandbox?

On Mon, 19 Feb 2007 01:08:19 -0800, Henri Yandell [EMAIL PROTECTED] wrote: On 2/19/07, Torsten Curdt [EMAIL PROTECTED] wrote: compress - Despite our attempt to get this released, nothing seems to have happened here. Anyone? IMO the API still needs work. I was trying to implement another

Commons Parser

Hi all, i am connecting from an Java Appserver to MQ at the moment, and it's the fifth time in my life that i have to handle character-messages from a host. Usually i implement something static to interpret what the host tells me: HV101020060003TESTTESTTEST This String could be read at least

patch for compress (was: Re: How patching the homepage?)

The homepage is/will get generated by maven so patches to src/site are welcome ...and then someone just needs to get them online. Thanks. Sorry for that idiot question, i should have a closer look... Well here is a patch for the site. It moves out the old examples and includes a new one.

[compress] Next steps

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, i would like to start a discussion about the next steps of [compress]. Now that the first code has been checked in, i would like to figure out what we have to do for a 0.1 release. Ideas: - - simplify the interface as Mario suggested - - write

Re: [VFS][compress] Re: [EMAIL PROTECTED]: Project commons-compress (in module jakarta-commons-sandbox) failed

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Rahul Akolkar wrote: (added [vfs] to subject) On 7/31/06, Torsten Curdt [EMAIL PROTECTED] wrote: - commons-compress : Commons Compression Package - commons-vfs : Jakarta commons - excalibur-fortress-bean : Repository of

Re: [compress] Draft 8

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Great :-) I am eager to do this delete stuff on top of this. - - Chris Torsten Curdt wrote: The grants has been received by Jim. I've merged the changes from Chris into my working copy of compress ...any objections to do a svn commit ? :-) Ok

Re: [vfs] split of vfs

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Initially, this sandbox contains the following filesystems: * bz2 * tar * webdav * smb The user can activate them by simply plugging the commons-vfs-sandbox.jar into the classpath. I think this is a great idea?and would like to see that

Re: [vfs] split of vfs

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 What legal issues are you refering? - From the users mailinglist: * we depend on jcifs (samba/smb) which changed its license in the past to lgpl, so this is a violation of the ASF rules we currently investigate. (Mario) The ASF has prove it can

Re: [vfs] split of vfs

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 This way the core would be independent of the implementation, as well building the .bz2 or something like will not be dependent of the external libs used only by the specifics like webdav, ftp, etc... If some implementation needs an external lib

Re: [compress] Status

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Niall Pemberton wrote: Slightly OT for this thread, but compress now has a nightly build: http://people.apache.org/builds/jakarta-commons/nightly/commons-compress/ That's great :-) Will email my fax number to Torsten/Chris and see if I can a)

Re: [compress] Status

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Chris - do you have any more recent changes or should we go with draft 8? I think it's better now to commit and let others participate. I have no recent changes and would like to wait till the code is in the repos. Regards, Chris -BEGIN PGP

[compress] Draft 8

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hey all, here is draft 8: * http://grobmeier.de/commons-compress-draft-8.zip I mainly have rebuild the factorys: - - Archiver is now know as Archive - - reduced reflection-magic - - Decompressor and Compressor is now know as Compressor (just one

Re: [compress] Draft 8

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Some comments: * you use File*Streams instead of simply InputStream/OutputStream, any reason for this?If no, please change it accordingly. sorry, thought i changed that allready. I will do so * simplify the archiver interface. e.g. I think

Re: I wrote several methods for IOCommons FileUtil. How can I donate it to IOCommons?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Are you developer of compress? i am just contributing, as you do. There's no owner at the moment for compress, as far as i know. Regards, Chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.1 (MingW32) Comment: Using GnuPG with Mozilla -

Re: I wrote several methods for IOCommons FileUtil. How can I donate it to IOCommons?

they have meaning. Compression is definitely not a specialized aspect of IO. Compression is critical to handling IO well and belongs in an IO package. On 6/18/06, C. Grobmeier [EMAIL PROTECTED] wrote: +1 to put this in Compress. I really don't get the point why this should be in IO. As Martin

Re: I wrote several methods for IOCommons FileUtil. How can I donate it to IOCommons?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 +1 to put this in Compress. I really don't get the point why this should be in IO. As Martin said, i see compress as specialized IO. For me it would be also OK if IO would depend on compress. in my latest draft is allready a CompressUtils class where

Re: [compress] Draft 7

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Cheers, o) The usage of the Archiver is still awkward. You create an Archiver, then set the filename of the archive. Why not have an Archive interface representing the archive and a ArchiveFactory Archive arch = ArchiveFactory.getInstance(new

[compress] Draft 7

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hey all, here is draft 7: http://grobmeier.de/commons-compress-draft-7.zip where mainly the factory has changed. It's possible now to get an archiver by name and by file/extension. As usual, comments are welcome. If there are not too many open

Re: [all] latest multidoc

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Henri Yandell wrote: I bring this up from time to time; slowly moving it along etc. http://people.apache.org/~bayard/multidoc-jnr/ The current status is that it contains 104 Commons javadocs. It uses both the jars in the maven repository (for

Re: [compress] Draft 6

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 will pugh wrote: Yeah. I agree valueOf would work just fine, but unless I'm missing something, the current implementation doesn't have this. The purpose of my comments was to say that I thought it should have something along those lines. The

Re: [compress] Draft 6

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 ...so what's the benefit over the usual factory + constructor instantiation then? Archive arch = new TarArchive(new File(my.tar)); Archive arch = ArchiveFactory.newInstance(new File(my.tar); Archive arch = ArchiveFactory.newInstance(tar); i

[compress] Draft 6

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, here is a new draft: http://www.grobmeier.de/commons-compress-draft-6.zip I have changed a lot of things discussed with draft 5. The API is easier now. Everything what seems to be unnecessary has been deleted. Compress is working with Files and

Re: [compress] New draft 5

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Henri Yandell wrote: If you could fill out the software grant: http://www.apache.org/licenses/#grants and either fax or postal-mail it (see instructions in first paragraph of http://www.apache.org/licenses/icla.txt;). [x] done via fax Please

Re: [compress] New draft 5

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Henri Yandell wrote: If you could fill out the software grant: http://www.apache.org/licenses/#grants and either fax or postal-mail it (see instructions in first paragraph of http://www.apache.org/licenses/icla.txt;). I will fill out the

Re: [compress] New draft 5

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Sandy McArthur wrote: On 4/30/06, C. Grobmeier [EMAIL PROTECTED] wrote: here is a new draft for the compress interface: * http://grobmeier.de/commons-compress-draft-5.zip Same as before, suggestions as a stream of consciousness, take the ones

Re: [compress] New draft 5

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 My fault for only just joining in etc, but why have the underlying Tar/Zip classes become package scoped? Does the bridging API replace all need to dig into the lower-level APIs? I was not thinking enough about this. In my fault i was thinking

Re: [compress] New draft 5

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 So my comments: o Don't like that compressor does both compression and decompression. I'm ambivalent on this one. If we would do so, we have 4 different interfaces. But i like the look. o Always use File not String +1. Only use 'String

[compress] New draft 5

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello all, here is a new draft for the compress interface: * http://grobmeier.de/commons-compress-draft-5.zip I have improved a lot of things, based on the comments of Sandy (thanks for that). This draft is not perfect, as you can see in the todo

Re: [all] Jira?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 James Carman wrote: I'm +1. JIRA is much more user friendly and intuitive, IMHO. I like JIRA too. I have reported a lot of bugs for other OS projects using JIRA, cause it's intuitive. As i saw the commons bugzilla instance first time i was really

Re: [compress] Moving forward...

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Brett said that it provides an archive bridging API, so I was wondering how that part of the Plexus one compared to your work Chris. I presume their one is tried and tested in Maven 2, so that's a pro for pulling it over into the Commons component

Re: [compress] Moving forward...

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Henri Yandell wrote: http://svn.plexus.codehaus.org/trunk/plexus-components/plexus-archiver/ btw. How does that compare to what you have Chris? It's quite similar to what we have. But i would prefer to build upon the old commons code, enhance it

Re: [compress] Moving forward...

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 * VFS release is held up by lack of a stable/promoted compress. Mario said so. * Maven (in plexus at codehaus) have a fork of compress with bugs fixed. True. Plexus has not factory, so it's not perfectly usable * Chris has an archive bridging

Re: Contributing Code

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I'd love to see your code, although I don't think we should merge until we get the code contributed. It looks like contributing code gets a bit harder when there are more than one person involved in writing it. It's easily possible to merge if

Re: Contributing Code

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 will pugh wrote: I thought it made sense to go into compress, but I think that depends on how close compress is to releasing. As I mentioned before, this code has a number of things to finish before it's ready for primetime. I would estimate

Re: [Id, Compress] question about status of the subproject 'Id' and 'Compress'

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, i wanted to ask what the status of the two subprojects 'Id' and Compress' currently are and what tasks will have to be solved to get them moved into the proper repository. for compress: at the moment there are 2,3 non-comitters out there

Re: Contributing Code

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I am interested in contributing code to commons. I wrote a ModifiableZip class, that basically implements all the methods on ZipFile, but provides new methods for adding, removing and modifying entries in an existing zip file. The basics

Re: Contributing Code

. -Original Message- From: C. Grobmeier [mailto:[EMAIL PROTECTED] Sent: Friday, April 21, 2006 8:16 AM To: Jakarta Commons Developers List Subject: Re: Contributing Code Hi, I am interested in contributing code to commons. I wrote a ModifiableZip class, that basically implements all

Re: Unsubscribe me please, thanks.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I have read lists in which the admins have sent (automatically) a simple user guide for the list, with unsubsribe information, about do's and dont's etc. Sending such an email could be quite cool- thinking on the [tag]-issue :-) Chris. Boris Unckel

Re: [compress] Interface is ready

want. Could you simply try out with this example? Regards and thx for the information, Chris Thanks, Hari. On 4/6/06, C. Grobmeier [EMAIL PROTECTED] wrote: Hi, Does this work with Solaris tar, since Solaris tar is different from GNU tar ? If not , is there a plan to do so ? Won't

Re: [compress] Interface is ready

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Does this work with Solaris tar, since Solaris tar is different from GNU tar ? If not , is there a plan to do so ? Won't making TarEntry an interface with Solaris/GNU implementations be a good idea ? This is just an idea off the top of my

Re: [compress] Interface is ready

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello Sandy, thousand thanks for your comments and the time you have spent for this. I will work through this all and prepare another draft soon. Thank you very much, Chris The following is a stream of things I don't think are right in the order

Re: [compress] Interface is ready

not for other operations. I think it's more easy to recognize that you have to use Archiver for archiving and Compressor for compressing instead to know what the methods do exactly. Cheers + Thanks, Chris Stephen C. Grobmeier wrote: Hey all, i have just uploaded this: http

[compress] Interface is ready

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hey all, i have just uploaded this: http://www.grobmeier.de/commons-compress-draft-4.zip Tar, Zip and BZip2 is now implemented by the 2 new interfaces. Please check it out, and tell me, if something more i have to do before it can be comitted to the

Re: [compress] Introducing the Compress-Interface

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 It appears to target the compress goals, is an active project(?) with releases, and most importantly uses a sane license (ASL). I'm not sure how much of a one-man show it is; but maybe we could be helping out there rather than trying to create

Re: commons-vfs release

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 You've got my time if you need it. Push on with getting each one of these moving, and whenever you hit a karma issue, just hit me and I'll deal with patches etc. I'll try to find time to dig into the issues themselves, but far more realistic to

Re: [compress] Discussing compress

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I have updated: http://grobmeier.de/commons-compress-draft-2.zip + input/output streams are all in finally-blocks + Examples for the old tar/bzip2 way included + Patch in Bug 30494 included: fixes these examples :-) Cheers, Chris C. Grobmeier wrote

[compress] Introducing the Compress-Interface

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, after thinking a lot about the difference of archivers and compressors, i am not sure how to proceed with it. At the moment [1], we have an Archiv Interface. This fits fine for Tar and Zip. If we imagine gunzip or bzip2 as an archive for an

Re: [compress] Discussing compress

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 hi, I actually think commons-archiver is a better name (the library I have used is plexus-archiver [1], which is derived from the same code and I want to merge them here). Note that there is also the unpack/decompress portion as well. +1 to the

Re: [compress] Discussing compress

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 1) Please take care to always close your input/output streams. ie. do this in a finally() block so that in any case (excpetion) the streams were closed OK, i will check this tonight or tomorrow evening :-) 2) you cant handle directories now,

Re: commons-vfs release

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 What would be the work involved in getting compress released? Any idea? - - fixing the 3 (or 4) Bugs - - preparing an commonly used interface - - having functions for deleting files from a compressed file (optional, i think) - - clean up of the old

Re: [email] ant dist fails / dependencies not found

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dion Gillard wrote: The javamail jars cannot be distributed by themselves as they are licensed under the Sun Binary Code License. How about building against the Geronimo versions?

Re: [email] ant dist fails / dependencies not found

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thank you. I think i will document this in the build-file and sent it to you soon for a possible patch. I really don't like build-files with comments :-) - - Chris Dennis Lundberg wrote: matthew.hawthorne wrote: C. Grobmeier wrote: -BEGIN PGP

[email] ant dist fails / dependencies not found

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, ant dist fails, cause the dependencies cannot be found. http://www.ibiblio.org/maven/javamail/jars/javamail-1.3.3.jar http://www.ibiblio.org/maven/javamail/jars/javamail-1.3.3.jar ... brought an I/O Exception, trying to download this from

Re: [email] ant dist fails / dependencies not found

the terms. I think it would be better to kick off these get/ Tags and tell the user he has to download these apis manually. How is this solved with maven? I guess this will result in an error too. Regards, Chris On 2/28/06, C. Grobmeier [EMAIL PROTECTED] wrote: Hello, ant dist fails, cause

Re: [email] ant dist fails / dependencies not found

it have to be, but this is not comfortable. Does maven work with this? Chris. On 2/28/06, C. Grobmeier [EMAIL PROTECTED] wrote: Dion Gillard wrote: The javamail jars cannot be distributed by themselves as they are licensed under the Sun Binary Code License. I thought the generated ant

[compress] Discussing compress

Hello, not knowing how to start best, i would like to kick off an discussion about the goals of [compress]. As i wrote in an email before ages, i have allready started to check out the existing lib and want to see this component working. I noticed, that compress ist divided into three

Re: [compress] Discussing compress

I was thinking that something like Compress.getInstance(String compressorType); like Crypto would be nice. This way you can get a unique entry point for every compression algorithm that can provide its own methods to compress/decompress/add files etc etc. you are speaking of a factory method.

Re: [compress] Discussing compress

Mario Ivankovits wrote: Hi! Compress.getInstance(String compressorType); +1 or even better Compress.getInstance(CompressorType compressorType); Yes, better. Thanks So, from my point of view compress should avoid having a configuration at all and should concentrate to be a compact library.

Re: [compress] Discussing compress

but be sure to only work with streams in your public API. So you might have to decompress and recompress the archive in a local temp folder to make those operations work. I think in your local temp directory you should NOT use the original filenames of the archive as they might contain invalid

Re: [compress] Discussing compress

Hello again :-) How do you change a file? Replacement would be not so good. I think a modify is a: delete and add operation. How do you delete a file and shrink the archive? I thought about reading the zip spec and cutting out the bytes i don't need. And all this heavily depends on

Re: [compress] Discussing compress

How do you delete a file and shrink the archive? I thought about reading the zip spec and cutting out the bytes i don't need. I am not aware of a file operation which allows you to cut out a number of bytes from a file. I think there exists a cut from end, but AFAIK this is not available in

Re: commons-email needs care

Cheers, recommended readings: * http://jakarta.apache.org/site/getinvolved.html * http://jakarta.apache.org/commons/patches.html Regards, Chris Piero Ottuzzi wrote: Hi there, yesterday I used commons-email 1.0 and I found it is quite buggy (for the jakarta quality meter). I found many bugs

Re: [lang] StringUtils.interrupt

as an adjustment to one of those, although I don't know how common a case it is. Stephen C. Grobmeier wrote: Hello all, building my websites guestbook, i figured out that somebody entered a big string (exactly: an URL). This blew up my complete layout. HTML doesn't give any solution on this, you simply

[lang] StringUtils.interrupt

Hello all, building my websites guestbook, i figured out that somebody entered a big string (exactly: an URL). This blew up my complete layout. HTML doesn't give any solution on this, you simply can't break up this stupid long string. Looking at commons lang i found a lot of

Re: [compress] what to do with?

Is there anything in particular you are interested in Chris? I would like to add stuff to the zip-implementation, for example deleting files from a zipfile. I would like to see this component released and so i am also interested to discuss the api or to check the Ant implementation Stefan

Re: [compress] what to do with?

Hi, I am interested in help with compress. I already read the code and checked out the zip-spec, but couldn't code something till now. Imaging an simple standalone compression helper makes me feel good. Chris Brett Porter wrote: I intend to resuscitate compress, but I wouldn't want to have

Re: [cli][patch 0/2] Some minor fixes

... please, do us a favour and put them into Bugzilla, so they do not get lost. Any effort by the maintainers is on a voluntary basis and you don't know, when they have the time to look. A mailing list is not the proper archive for proposed changes, bugfixes and patches. Hi, i agree with

Re: Gump VM

So what can we do? I read about timers in the book killer game programming in java :-), where this things are important. Maybe this is a direction for you. Use the following instead of System.currentTimeMillis(): 1) Suns undocumented Class (Java2): sun.misc.Perf 2) Java 5: System.nanoTime()

Re: [test] Awake dormant component

Alex Karasulu once created the test component and I had already at that time a special interest in this. I would like to awake this dormant component, maintain and add stuff. just for info, what did this component? can't find any information about this. Thanks Chris

Re: [compress] playing around

that is less popular might mean longer response times on mailing lists or in Bugzilla, if you take up spreading the word as a challenge, I'm sure you'll find much joy along the way as well. -Rahul James -Original Message- From: C. Grobmeier [mailto:[EMAIL PROTECTED] Sent: Tuesday

Re: [compress] playing around

Whats the zip-problem? You want to create a simple zipfile and always have to google and try to figure out what this and that means instead of simple writing: ZipFile zip = new ZipFile(/home/Cy/yourzip.zip); zip.add(/home/Cy/yourfile1.zip); zip.add(/home/Cy/yourfile2.zip); zip.create(); No

Re: [compress] playing around

In other words, if your solution also allows to change/update zip files (or even more abstract jar/tar too), chances are good to have this integrated in commons-vfs too ;-) sounds like one should play around with compress :-)

[compress] playing around

Hi, i want to play around with some commons components to get a deeper understanding. I would like to start with compress. The examples are not online at the moment. I wanted to ask if somebody has a link with examples for me or other information about the roadmap or todo. Cheers + Thx,

[compress] playing around

Sorry for the double-post. For your comfort i sent my message again. -- Hi, i want to play around with some commons components to get a deeper understanding. I would like to start with compress. The examples are not online at the moment. I wanted to ask if somebody has a link with examples

Re: [all] Commons Manual

Maybe this is of interest: * Programming guidelines: do's and don'ts Chris Phil Steitz wrote: I am +1 (in the sense of will help :-) for anything involving improving docs. My one request would be that we start with the docs that already exist and target the main commons web site to house

Re: [all] Together, and bricks apart

At least one of you release checkers ;-) should setup a wiki to describe every step to do, this helps the release manager and those checking it. Especially if you are a newbie in the release cycle it might be a great start AND it defines standards. I like Marios idea. Very new to