On 26-Mar-04, at 12:50 Uhr, Maarten Coene wrote:
I don't think HTML related code has been changed, so your problems will probably still exist. If you could post a bug report (and a patch if you have one), I can work on it to get is resolved in the next release.
Good, will try, in the mail I had one patch. Should I simply place the patch as is (it was on dom4j-141-beta or so, the head wasn't compiling) ?
You can place the patch as is and I'll see if it can still be used...
I didn't change anything to maven, so I guess dom4j-beta8 has been used ... Do you have more details about the entity processing problems ?
(which version of dom4j are you having maven use when you build the site ?) I seem to see somewhat of a problem as they are (or were a month ago) still relying on dom4j-beta-8 because subsequent versions broke entity processing.
I'm trying to collect something into a test... but I haven't really managed yet. I don't think it was really worth testing deep with beta-8.
The general use-case is to share a piece of XML content through several project.xml using such entities (which are typically in different directories)... but I really need a use case, first at the level of maven, then at the level of jelly, then at the level of dom4j !
I fixed a bug where relative URI's were not resolved properly if the XML was parsed using SAXReader.read(File) . Maybe this fix has solved the problem in maven/jelly ??
thanks, Maarten
------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ dom4j-dev mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dom4j-dev
