+1 We have effectively several problems with entities in maven plugins due to problems in Jelly/Dom4J.
It can be a good think if we can do this before maven 1.0 RC3. Arnaud > -----Message d'origine----- > De : [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] > Envoy� : mercredi 12 mai 2004 23:38 > � : Jakarta Commons Users List > Objet : Re: [jelly] move to dom4j-1.5-beta-2 ? > > > +1. > > Once we move to dom4j1.5 beta 2, I'll try changing Maven's > dependencies to > work with a newer Jelly and see how we go. > -- > dIon Gillard, Multitask Consulting > > > > Paul Libbrecht <[EMAIL PROTECTED]> wrote on 13/05/2004 05:09:25 AM: > > > > > Dear Jellyers, > > > > Most Jelly users know that Jelly is highly depending on dom4j, it's > > XML-data-model (well, at least when in-memory). Jelly (and > maven) have > > been suffering an amount of things due to issues in dom4j, in > > particular with respect to XML-output and entity resolution. > > These two things seem to be fixed in jelly 1.5 beta2 which makes me > > suggest we move to this and hope people using jelly will do so > > (including maven, hint, hint) and comment. > > > > thanks for feedback. > > > > paul > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: > [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
