You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ivy-user@ant.apache.org by easyproglife <ea...@gmail.com> on 2007/01/21 18:21:56 UTC
Re: IvyDE (1.2) does not support non-standard attributes in ivy.xml files when Eclipse runs from JRE 1.5?
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 <xa...@gmail.com> wrote:
>
> On 12/17/06, ophir bleiberg <op...@personeta.com> 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 <op...@personeta.com> 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."
> > >
> > >
> > >
> >
> >
>
>
Re: IvyDE (1.2) does not support non-standard attributes in ivy.xml files when Eclipse runs from JRE 1.5?
Posted by Xavier Hanin <xa...@gmail.com>.
On 1/21/07, easyproglife <ea...@gmail.com> wrote:
>
> 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?
The problem is that we still don't have moved IvyDE to the ASF incubator.
I've sent a software grant some time ago (several weeks if I remember well),
but I don't know if the software grant has been processed. I'll investigate
to know if I can move IvyDE sources to the Ivy svn repository (and see how
to import IvyDE JIRA issues).
For this patch it's really simple, so just ping me again when IvyDE sources
will be migrated.
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.
I wouldn't consider that as a bug, but an improvement, because Ivy never
stated that it uses Ant conventions for boolean values. But it would be
better, so feel free to open a JIRA issue (in the Ivy project, since this is
not IvyDE specific).
Xavier
On 12/17/06, Xavier Hanin <xa...@gmail.com> wrote:
> >
> > On 12/17/06, ophir bleiberg <op...@personeta.com> 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 <op...@personeta.com> 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.2fails
> > > > 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."
> > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>