Hello, Thanks for the answer. I was just proposing this as a simplification for comprehension and mostly for coherence. But I completely understand the question of backward compatibility, I am the first one to blame a tool that drastically changes version to version... Nevertheless, I am pretty sure that EMF can handle a little complexity and that will be a little more challenging after all... I will let you know if I come up with something interesting and if you think it can help IvyDE development.
Mathieu 2009/8/19 Xavier Hanin <xavier.ha...@gmail.com> > On Wed, Aug 19, 2009 at 11:05, Mathieu Anquetin > <mathieu.anque...@gmail.com>wrote: > > > 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 > parent? > > Xavier > -- > Xavier Hanin - 4SH France - http://www.4sh.fr/ > BordeauxJUG creator & leader - http://www.bordeauxjug.org/ > Apache Ivy Creator - http://ant.apache.org/ivy/ >
