In the mean time, can you publish a SNAPSHOT? Also, is anyone looking at releasing this stuff? Am I on the wrong mailing list (I couldn't find one for commons-fileupload)?

Thanks,

-dain

On Nov 2, 2006, at 12:38 AM, Henri Yandell wrote:

Our (Commons) nightly build machine (vmbuild.apache.org) was on a
vmware zone that hasn't come back after the machine migration. It took
care of both the nightly dist build and the m1 snapshot repo
deployments.

I'll pester for info again on it tomorrow; last I heard was that we
don't have vmware expertise and so it's a case of finding nudging
those who were involved with infra back when it was down to look into
it.

It's all in SVN, so if nothing's forthcoming I'll look into setting
something up (unless someone else volunteers - always appreciated :)
).

Sad that we pestered Craig to get it off of his workstation, and we've
not managed to achieve his quality of service.

Hen

On 10/29/06, Dain Sundstrom <[EMAIL PROTECTED]> wrote:
Has this code been Released yet?  The latest version I see is 1.1.1
and it doesn't seem to contain the FileItemIterator class.  Also
there don't seem to be any nightly snapshots available.

In the mean time I can build this by hand, but I'd prefer a Release
or SNAPSHOT in a maven repo.

Thanks for any help,

-dain

On May 23, 2006, at 5:10 PM, Dain Sundstrom wrote:

> Wow.
>
> I can't wait to get my hands on this code.
>
> -dain
>
> On May 23, 2006, at 4:24 AM, Yoav Shapira wrote:
>
>> Hola,
>> +1 to you getting commons-fileupload karma and doing it yourself ;)
>>
>> Yoav
>>
>> On 5/23/06, Jochen Wiedmann <[EMAIL PROTECTED]> wrote:
>>>
>>> Hi,
>>>
>>> I have developed a modified version of the commons-fileupload, which
>>> allow a true streaming mode. In other words, there's no need for
>>> internal byte arrays or temporary disk files, you simply iterate
>>> through
>>> the items, get an InputStream on the items, read and process the
>>> InputStream (for example, run an XML parser on it) and that's it.
>>> The
>>> API remains unchanged and the modifications are strictly internally.
>>>
>>> For obvious reasons, the patches are non-trivial. So far I have
>>> splitted
>>> some changes into three patches, which I have posted in Jira issues.
>>> However, to get this patches in, one after the other, I see as my
>>> only
>>> chances, if an existing developer would express interest on the
>>> changes,
>>> review and guide my work and accept patches step by step. Is there
>>> anyone who volunteers doing the job? Perhaps, being an active ws
>>> committer, I might after some time as well receive Karma for
>>> commons-fileupload and finish the work, if I have earned some trust.
>>>
>>> Regards,
>>>
>>> Jochen
>>>
>>>
>>> --------------------------------------------------------------------
>>> -
>>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>>> For additional commands, e-mail: [EMAIL PROTECTED]
>>>
>>>
>>
>>
>> --
>> Yoav Shapira
>> Nimalex LLC
>> 1 Mifflin Place, Suite 310
>> Cambridge, MA, USA
>> [EMAIL PROTECTED] / www.yoavshapira.com
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to