You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Heritier Arnaud <ah...@axway.com> on 2004/05/13 09:15:19 UTC
RE: [jelly] move to dom4j-1.5-beta-2 ?
+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 : dion_gillard@multitask.com.au
> [mailto:dion_gillard@multitask.com.au]
> 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 <pa...@activemath.org> 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: commons-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail:
> commons-user-help@jakarta.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-user-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [jelly] move to dom4j-1.5-beta-2 ?
Posted by Paul Libbrecht <pa...@activemath.org>.
On 14-May-04, at 16:01 Uhr, dion_gillard@multitask.com.au wrote:
> If that's an exception about the repository connection, that's a typo
> in one of the project.xmls. Which one did u use?
Oh no, it's an exception in parsing the project object!
(it is due to an eaten xml-parsing exception in the xml-reader feeding
to Betwixt, sorry I haven't patched the code to see where the error
is).
paul
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-user-help@jakarta.apache.org
Re: [jelly] move to dom4j-1.5-beta-2 ?
Posted by di...@multitask.com.au.
If that's an exception about the repository connection, that's a typo in
one of the project.xmls. Which one did u use?
--
dIon Gillard, Multitask Consulting
Paul Libbrecht <pa...@activemath.org> wrote on 14/05/2004 11:21:59 PM:
> Nope, the last changes didn't fix anything... at least as far as I can
> see.
> (that is, with dom4j-1.5-beta-2, the latest CVS version of Maven trying
> to build the latest Jelly)
>
> Can it be I was completely mistaking but MavenUtilities now chokes on a
> Betwixt building (BeanReader something) of the project bean and eats
> the exception... quite bad.
>
> paul
>
>
> On 14-May-04, at 10:52 Uhr, dion_gillard@multitask.com.au wrote:
>
> > There was a very recent bug fix in Maven to make sure systemId's were
> > associated with project.xml.
> >
> > Maybe this would help.
> > --
> > dIon Gillard, Multitask Consulting
> >
> >
> >
> > Paul Libbrecht <pa...@activemath.org> wrote on 14/05/2004 05:54:55 PM:
> >
> >>
> >> On 13-May-04, at 21:44 Uhr, robert burrell donkin wrote:
> >>> suitable for a general library but might be fine as a configuration
> >>> for use with jelly.
> >>
> >> Sorry to be picky but that was addressed solely for the purposes of
> >> Maven. The latter uses, I think, Jelly to parse such things as
> >> maven.xml and Digeser to parse project.xml.
> >>
> >> Things should be looked at around maven thus.
> >> A good candidate issue was the build of the jelly taglibs which
should
> >> (but don't as it doesn't work) be importing a common entity for
> >> dependencies, this happening from inside a parent-project.
> >> (e.g. from Jelly home, ./jelly-tags/swing/project.xml is declared
> >> child
> >> of ./jelly-tags/taglib-project.xml, itself should import (in an
entity
> >> fashion) ./commonDeps.ent, this last import doesn't work).
> >>
> >> paul
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
> >> For additional commands, e-mail: commons-user-help@jakarta.apache.org
> >>
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: commons-user-help@jakarta.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-user-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-user-help@jakarta.apache.org
Re: [jelly] move to dom4j-1.5-beta-2 ?
Posted by Paul Libbrecht <pa...@activemath.org>.
Nope, the last changes didn't fix anything... at least as far as I can
see.
(that is, with dom4j-1.5-beta-2, the latest CVS version of Maven trying
to build the latest Jelly)
Can it be I was completely mistaking but MavenUtilities now chokes on a
Betwixt building (BeanReader something) of the project bean and eats
the exception... quite bad.
paul
On 14-May-04, at 10:52 Uhr, dion_gillard@multitask.com.au wrote:
> There was a very recent bug fix in Maven to make sure systemId's were
> associated with project.xml.
>
> Maybe this would help.
> --
> dIon Gillard, Multitask Consulting
>
>
>
> Paul Libbrecht <pa...@activemath.org> wrote on 14/05/2004 05:54:55 PM:
>
>>
>> On 13-May-04, at 21:44 Uhr, robert burrell donkin wrote:
>>> suitable for a general library but might be fine as a configuration
>>> for use with jelly.
>>
>> Sorry to be picky but that was addressed solely for the purposes of
>> Maven. The latter uses, I think, Jelly to parse such things as
>> maven.xml and Digeser to parse project.xml.
>>
>> Things should be looked at around maven thus.
>> A good candidate issue was the build of the jelly taglibs which should
>> (but don't as it doesn't work) be importing a common entity for
>> dependencies, this happening from inside a parent-project.
>> (e.g. from Jelly home, ./jelly-tags/swing/project.xml is declared
>> child
>> of ./jelly-tags/taglib-project.xml, itself should import (in an entity
>> fashion) ./commonDeps.ent, this last import doesn't work).
>>
>> paul
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: commons-user-help@jakarta.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-user-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-user-help@jakarta.apache.org
Re: [jelly] move to dom4j-1.5-beta-2 ?
Posted by di...@multitask.com.au.
There was a very recent bug fix in Maven to make sure systemId's were
associated with project.xml.
Maybe this would help.
--
dIon Gillard, Multitask Consulting
Paul Libbrecht <pa...@activemath.org> wrote on 14/05/2004 05:54:55 PM:
>
> On 13-May-04, at 21:44 Uhr, robert burrell donkin wrote:
> > suitable for a general library but might be fine as a configuration
> > for use with jelly.
>
> Sorry to be picky but that was addressed solely for the purposes of
> Maven. The latter uses, I think, Jelly to parse such things as
> maven.xml and Digeser to parse project.xml.
>
> Things should be looked at around maven thus.
> A good candidate issue was the build of the jelly taglibs which should
> (but don't as it doesn't work) be importing a common entity for
> dependencies, this happening from inside a parent-project.
> (e.g. from Jelly home, ./jelly-tags/swing/project.xml is declared child
> of ./jelly-tags/taglib-project.xml, itself should import (in an entity
> fashion) ./commonDeps.ent, this last import doesn't work).
>
> paul
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-user-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-user-help@jakarta.apache.org
Re: [jelly] move to dom4j-1.5-beta-2 ?
Posted by Paul Libbrecht <pa...@activemath.org>.
On 13-May-04, at 21:44 Uhr, robert burrell donkin wrote:
> suitable for a general library but might be fine as a configuration
> for use with jelly.
Sorry to be picky but that was addressed solely for the purposes of
Maven. The latter uses, I think, Jelly to parse such things as
maven.xml and Digeser to parse project.xml.
Things should be looked at around maven thus.
A good candidate issue was the build of the jelly taglibs which should
(but don't as it doesn't work) be importing a common entity for
dependencies, this happening from inside a parent-project.
(e.g. from Jelly home, ./jelly-tags/swing/project.xml is declared child
of ./jelly-tags/taglib-project.xml, itself should import (in an entity
fashion) ./commonDeps.ent, this last import doesn't work).
paul
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-user-help@jakarta.apache.org
RE: [jelly] move to dom4j-1.5-beta-2 ?
Posted by Arnaud Heritier <ar...@laposte.net>.
I'll try to find if these problems are related.
Thanks
#Arnaud
> -----Message d'origine-----
> De : robert burrell donkin [mailto:robertburrelldonkin@blueyonder.co.uk]
> Envoyé : jeudi 13 mai 2004 21:44
> À : Jakarta Commons Users List
> Objet : Re: [jelly] move to dom4j-1.5-beta-2 ?
>
> (if these are the same issues that paul raised a while ago)
>
> digester has the typical problems that SAX-based applications have with
> entities. (there's quite a bit of variation in practice between the
> specification, the SAX events fed by parsers and what most users
> reasonably expect.)
>
> if so, one way to fix these issues is to provide a custom entity
> handler. paul wanted some digester changes that were not really
> suitable for a general library but might be fine as a configuration for
> use with jelly.
>
> - robert
>
> On 13 May 2004, at 15:46, Paul Libbrecht wrote:
>
> > Cool, oh cool! Will do soon...
> > Note that these entity problems in Maven may be due to something else
> > than dom4j and Sax parsing at the level of Jelly. Last I reported
> > errors which seemed to be more due to digester (but I couldn't
> > finalize my tests, sorry). In all cases, we would heavily wish at
> > least failing maven test-cases.
> >
> > thanks
> >
> > paul
> >
> >
> > On 13-May-04, at 09:15 Uhr, Heritier Arnaud wrote:
> >
> >> 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.
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: commons-user-help@jakarta.apache.org
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-user-help@jakarta.apache.org
Re: [jelly] move to dom4j-1.5-beta-2 ?
Posted by robert burrell donkin <ro...@blueyonder.co.uk>.
(if these are the same issues that paul raised a while ago)
digester has the typical problems that SAX-based applications have with
entities. (there's quite a bit of variation in practice between the
specification, the SAX events fed by parsers and what most users
reasonably expect.)
if so, one way to fix these issues is to provide a custom entity
handler. paul wanted some digester changes that were not really
suitable for a general library but might be fine as a configuration for
use with jelly.
- robert
On 13 May 2004, at 15:46, Paul Libbrecht wrote:
> Cool, oh cool! Will do soon...
> Note that these entity problems in Maven may be due to something else
> than dom4j and Sax parsing at the level of Jelly. Last I reported
> errors which seemed to be more due to digester (but I couldn't
> finalize my tests, sorry). In all cases, we would heavily wish at
> least failing maven test-cases.
>
> thanks
>
> paul
>
>
> On 13-May-04, at 09:15 Uhr, Heritier Arnaud wrote:
>
>> 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.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-user-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-user-help@jakarta.apache.org
Re: [jelly] move to dom4j-1.5-beta-2 ?
Posted by Paul Libbrecht <pa...@ags.uni-sb.de>.
Cool, oh cool! Will do soon...
Note that these entity problems in Maven may be due to something else
than dom4j and Sax parsing at the level of Jelly. Last I reported
errors which seemed to be more due to digester (but I couldn't finalize
my tests, sorry). In all cases, we would heavily wish at least failing
maven test-cases.
thanks
paul
On 13-May-04, at 09:15 Uhr, Heritier Arnaud wrote:
> 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.
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-user-help@jakarta.apache.org
RE: [jelly] move to dom4j-1.5-beta-2 ?
Posted by di...@multitask.com.au.
"Heritier Arnaud" <ah...@axway.com> wrote on 13/05/2004 05:15:19 PM:
> +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
I don't think that's possible.
Last time I tried replacing the jelly jars in Maven, Maven was broken.
Please feel free to try again though.
--
dIon Gillard, Multitask Consulting
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org