ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Xavier Hanin <>
Subject Re: Ivy "exclude"s
Date Wed, 19 Aug 2009 17:18:31 GMT
On Wed, Aug 19, 2009 at 11:05, Mathieu Anquetin

> Hello,
> I am currently working on ivy.xml (in particular its schema) to provide an
> ECORE model of it. My goal is to provide a graphical editor for ivy files
> and improve validation thanks to MDD and hand it to IvyDE if it sounds
> intrersting.
> But, I am confronted to a weird issue. There are currently two different
> "exclude" tags. I understand they have not the same purpose, but they are
> exactly the same in their description except the name/artifact attribute.
> So, this is my question : Could it be possible to retain just one attribute
> name, thus modifying the XSD and parsing ? Should I post an issue and
> provide a patch for the XML parsing ?

Hello Mathieu,
I think one of the exclude tag is for artifact exclusion inside a dependency
tag, while the other is for module wide excludes. Changing the xsd of
ivy.xml is not something that can be done easily: many people rely on Ivy
stability, and Ivy provides backward compatibility in ivy.xml format since
very early versions (0.9 I think). Is ECORE too limited to handle an xsd
where the same tag can appear with different constraints depending on its

Xavier Hanin - 4SH France -
BordeauxJUG creator & leader -
Apache Ivy Creator -

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message