From ivy-user-return-5553-apmail-ant-ivy-user-archive=ant.apache.org@ant.apache.org Fri Jul 10 22:26:21 2009 Return-Path: Delivered-To: apmail-ant-ivy-user-archive@www.apache.org Received: (qmail 10001 invoked from network); 10 Jul 2009 22:26:19 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 10 Jul 2009 22:26:19 -0000 Received: (qmail 69177 invoked by uid 500); 10 Jul 2009 22:26:28 -0000 Delivered-To: apmail-ant-ivy-user-archive@ant.apache.org Received: (qmail 69127 invoked by uid 500); 10 Jul 2009 22:26:28 -0000 Mailing-List: contact ivy-user-help@ant.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ivy-user@ant.apache.org Delivered-To: mailing list ivy-user@ant.apache.org Received: (qmail 69117 invoked by uid 99); 10 Jul 2009 22:26:28 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 10 Jul 2009 22:26:28 +0000 X-ASF-Spam-Status: No, hits=-4.0 required=10.0 tests=RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of prvs=744238dc4f=shawn.castrianni@halliburton.com designates 34.254.247.12 as permitted sender) Received: from [34.254.247.12] (HELO NP1MAIL002.halliburton.com) (34.254.247.12) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 10 Jul 2009 22:26:16 +0000 Received: from np1exhu011.corp.halliburton.com (np1exhu011.corp.halliburton.com [34.34.132.81]) by NP1MAIL002 (8.14.3/8.14.3) with ESMTP id n6AMPtd1024002 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for ; Fri, 10 Jul 2009 17:25:55 -0500 Received: from NP1EXCH012.corp.halliburton.com ([34.34.132.75]) by np1exhu011.corp.halliburton.com ([34.34.132.81]) with mapi; Fri, 10 Jul 2009 17:25:55 -0500 From: Shawn Castrianni To: "'ivy-user@ant.apache.org'" Date: Fri, 10 Jul 2009 17:25:54 -0500 Subject: RE: is ivy dead? Thread-Topic: is ivy dead? Thread-Index: AcoBrQu/FxFh/RfHQJC5ktWM7dRIbwAABVew Message-ID: <34721A41A7BCF54ABC3B116219A8C1C2057B68A549@NP1EXCH012.corp.halliburton.com> References: <007e01c9fe8d$52eb83a0$4600a8c0@referentia.com> <293214.38929.qm@web30805.mail.mud.yahoo.com> In-Reply-To: <293214.38929.qm@web30805.mail.mud.yahoo.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-HALSTAMP: TRUE X-Proofpoint-Virus-Version: vendor=fsecure engine=1.12.7400:2.4.4,1.2.40,4.0.166 definitions=2009-07-10_11:2009-07-03,2009-07-10,2009-07-10 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx engine=5.0.0-0811170000 definitions=main-0907100162 X-Virus-Checked: Checked by ClamAV on apache.org I use ivy for my job and, therefore, any urgent issue or enhancement can be= resolved by offering paid development from the company's budget to any of = the ivy committers. I am sure any of the ivy committers would like to make= some extra money. --- Shawn Castrianni -----Original Message----- From: Maarten Coene [mailto:maarten_coene@yahoo.com]=20 Sent: Friday, July 10, 2009 5:12 PM To: ivy-user@ant.apache.org Subject: Re: is ivy dead? Hi Jim, I understand your frustration. I have the same feeling when I report issues= to some commercial products and never get a response. But please keep in mind that Ivy is not a commercial product. The developer= s of Ivy are not paid by Apache for their work on Ivy. This means we do fix= some bugs, commit some new features when we have some free time to work on= it. I can only speek for myself, but the last couple of months I didn't had muc= h free time left to work on Ivy. But I'm confident this will improve in the= near future... regards, Maarten ----- Original Message ---- From: Jim Newsham To: ivy-user@ant.apache.org Sent: Tuesday, July 7, 2009 12:58:48 AM Subject: Re: is ivy dead? I share the same frustration. It seems that bugs which were reported months ago have no assigned owner, no evaluation, and no activity... regardless of priority level. Maybe a more sensitive way of rephrasing the question is: Is ivy being actively developed and maintained? What is the development cycle? Are maintenance fixes being made to released versions? How quickly are bugs evaluated? How quickly can we expect a major bug to be fixed/released in a maintenance release? It's not that I feel a need to draw attention to the particular issues that I'm experiencing. I've learned to work around those. It's for the community's benefit. Jim The issues that I've run into are: retrieve with "sync" is broken (IVY-1044); cleancache sometimes does NOT clean the cache (IVY-1080).=20=20 On Jun 22, 2009, at 4:50 PM, Alex Zhukov wrote: >=20 > Hello All, >=20 > I opened a critical bug http://issues.apache.org/jira/browse/=20 > IVY-1087 on June 2, no reaction from developers. On June 15 I=20=20 > increased the priority to Blocker, still no reaction from=20=20 > developers. Can some one tell me if ivy project is dead or=20=20 > developers are not interested in maintaining it any more? This is an open source project. Sometimes activity is high, sometimes=20=20 not so high. Developers are on holidays or have a stressful time with=20=20 their day time project. Whatever. And obviously, looking at the mailing list you are using, this project=20= =20 seems to be busy and far from dead. I can understand that it is=20=20 sometimes frustrating that an important issue is not fixed. But I=20=20 think it is not a nice style to play with the 'Is this project dead?'=20=20 phrase to raise attention for an issue. This is mud-slinging. I think=20=20 the fact that within the period of three weeks no one has commented on=20= =20 a certain issue does not justify this at all. =20=20=20=20=20=20 ---------------------------------------------------------------------- This e-mail, including any attached files, may contain confidential and pri= vileged information for the sole use of the intended recipient. Any review= , use, distribution, or disclosure by others is strictly prohibited. If yo= u are not the intended recipient (or authorized to receive information for = the intended recipient), please contact the sender by reply e-mail and dele= te all copies of this message.