Return-Path: Delivered-To: apmail-incubator-ivy-user-archive@locus.apache.org Received: (qmail 51540 invoked from network); 21 Jan 2007 17:22:20 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 21 Jan 2007 17:22:20 -0000 Received: (qmail 64772 invoked by uid 500); 21 Jan 2007 17:22:26 -0000 Delivered-To: apmail-incubator-ivy-user-archive@incubator.apache.org Received: (qmail 64741 invoked by uid 500); 21 Jan 2007 17:22:25 -0000 Mailing-List: contact ivy-user-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ivy-user@incubator.apache.org Delivered-To: mailing list ivy-user@incubator.apache.org Received: (qmail 64732 invoked by uid 99); 21 Jan 2007 17:22:25 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 21 Jan 2007 09:22:25 -0800 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of easyproglife@gmail.com designates 66.249.82.230 as permitted sender) Received: from [66.249.82.230] (HELO wx-out-0506.google.com) (66.249.82.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 21 Jan 2007 09:22:17 -0800 Received: by wx-out-0506.google.com with SMTP id i26so1078240wxd for ; Sun, 21 Jan 2007 09:21:56 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=bN5AVe4O3vce0byk76t5IDOdbDhApUJSqMUEJXwJq87ni3e4m43l9VoXOXiZKN2BmFTfqppkzxYyVdaIefeJhZDUtDDzCxEZAvi7uqRiGlNdKG+GOo30qlyTuNudQphOWj2GSDtfo7cHmo8dt7GrOD0J+S06Xa3ts1XyrVwRsVM= Received: by 10.70.74.1 with SMTP id w1mr8883951wxa.1169400116166; Sun, 21 Jan 2007 09:21:56 -0800 (PST) Received: by 10.70.98.14 with HTTP; Sun, 21 Jan 2007 09:21:56 -0800 (PST) Message-ID: Date: Sun, 21 Jan 2007 19:21:56 +0200 From: easyproglife To: ivy-user@incubator.apache.org Subject: Re: IvyDE (1.2) does not support non-standard attributes in ivy.xml files when Eclipse runs from JRE 1.5? In-Reply-To: <635a05060612170503i149009c2g4e4fe27d64808f5@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_155469_24167369.1169400116083" References: <635a05060612170439o1100d282wfa0cbd4ee1e0f6d@mail.gmail.com> <001d01c721da$5d825c40$11a8a8c0@personeta.com> <635a05060612170503i149009c2g4e4fe27d64808f5@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_155469_24167369.1169400116083 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Unfortunately, IvyDE has a bug: the validation is hard coded "true" instead of using ivyconf.xml value. See org.jayasoft.ivyde.eclipse.cpcontainer.IvyClasspathContainer.java:188 As you can see, the 6th parameter is hard coded true. Patch: replace the "true" to "_ivy.doValidate()". It Works! Xavier, I don't know how to send the patch. There is no IvyDE SVN and no JIRA category. Can you instruct me how to send the patch? Anyway, since this is really a little change (as I described above) it is easy to do it yourself. By the way, I have found another bug (probably already in Jira, I haven't checked): Ivy doesn't use Ant conventions for "yes/on/true" and "no/off/false". I don't remember where in Ant documentation it is stated that yes/on/true are all equal and that no/off/false are also all equal. On 12/17/06, Xavier Hanin wrote: > > On 12/17/06, ophir bleiberg wrote: > > > > The problem only occurs when working with IvyDE through Eclipse. > > > This can be due to the lack of an XML parser supporting schema validation > in > other cases. > > How do I disable schema validation in IvyDE? > > > You can only disable validation altogether in Ivy, in the conf element of > your ivyconf.xml: > http://www.jayasoft.org/ivy/doc/configuration/conf > > Xavier > > -----Original Message----- > > From: Xavier Hanin [mailto:xavier.hanin@gmail.com] > > Sent: Sunday, December 17, 2006 2:39 PM > > To: ivy-user@incubator.apache.org > > Subject: Re: IvyDE (1.2) does not support non-standard attributes in > > ivy.xml > > files when Eclipse runs from JRE 1.5? > > > > The problem seems to be due to schema validation. When using extra > > attributes you should disable validation. Did you disable xml validation > > in > > Ivy? > > > > Xavier > > > > On 12/17/06, Ophir Bleiberg wrote: > > > > > > Hi, > > > It appears that when the default PC JRE (not JAVA_HOME, but > > > rather the 'java' executable in the path) is 1.5, then IvyDE 1.2 fails > > > to resolve ivy.xml files with additional non-standard attributes (we > > > use 'kind' and 'version', for example). > > > Everything works fine on PCs whose 'java -version' is 1.4. > > > On those with 1.5, resolving fails, and the following is > > > printed to the log: > > > !ENTRY org.jayasoft.ivyde.eclipse 4 4 2006-12-14 14:41:30.640 > > > !MESSAGE Impossible to resolve dependencies of [ personeta | > > > CollectCall | NONE ]: > > > unresolved dependency: [ personeta | CollectCallBillingCDR | > > > 4.0.1.0-build0 ]: java.text.ParseException: [xml parsing: > > > > > > > > H:\personeta\ApplicationData\TappS-Dev\ivy-repository\integration\personeta\ > > CollectCallBillingCDR\4.0.1.0-build0\ivys\ivy.xml:2:160: > > > cvc-complex-type.3.2.2: Attribute 'version' is not allowed to appear > > > in element 'info'. in > > > H:\personeta\ApplicationData\TappS-Dev\ivy-repository\integration\pers > > > oneta\CollectCallBillingCDR\4.0.1.0-build0\ivys\ivy.xml > > > ] > > > > > > See IvyConsole for further details > > > > > > > > > Is this a known issue? Is there a target version for fixing > > > this problem? > > > > > > Thanks, > > > Ophir > > > > > > "Beware of the man who works hard to learn something, learns it, > > > and finds himself no wiser than before. He is full of murderous > > > resentment of people who are ignorant without having come by their > > > ignorance the hard way." > > > > > > > > > > > > > > > ------=_Part_155469_24167369.1169400116083--