Yeah we will need to do a 2.2.23 release of this to move forward with
the hibernate release :(
On 03/11/2010 10:07 AM, Steve Ebersole wrote:
> Hardy asked where the dtds are kept in our source. I was pointing him
> to them.
>
> The change here was just to use the local dtd resolution strategy i
Ok it was *downloading* them from the net because I missed this usage of
createSAXSource to apply the resolver. That's different than
validating though which is what was throwing me.
The change here really was just to apply the local resolver.
Perhaps there is a way to enforce that inside cre
No, i don't think so, and also it is not because of that docbook.dtd cant be
access.
basically, that XIncludeHelper.locateInclusions method will be called many
times when you build docs, every time it tries to get that dtd from web.
so in Gail's case, it was running but busy on resolve dtd :D
an
You mean like these:
http://fisheye.jboss.org/browse/Maven/plugins/jdocbook/maven-jdocbook-plugin/trunk/src/main/resources/docbook/xml/4.5/ent
?
;)
On 03/11/2010 09:49 AM, Hardy Ferentschik wrote:
> I remember the days when my Struts application wouldn't start up,
> because on startup it validate
I remember the days when my Struts application wouldn't start up, because
on startup it validated the
xml and always downloaded the dtd via the web. If the website was down,
the app would not start up.
I guess something similar happened here.
Using a local resolver seem to be a good idea, but
IMO, this is the point, XIncludeHelper.locateInclusions use
FileUtil.createSAXSource to create a Source object, after you enabled this
loading feature, it will tries to resolve the dtd from remote
here is what i changed.
http://fisheye.jboss.org/browse/Maven/plugins/jdocbook/maven-jdocbook-plugi
That's not true afaik:
reader.setFeature( Constants.DTD_LOADING_FEATURE, true );
reader.setFeature( Constants.DTD_VALIDATION_FEATURE, false );
Loading *needs* to happen.
Anyway that code was the same before I updated and after I updated.
This is in FileUtils#createSAXSource. So where is it that
Okay, I have builded trunk locally, it works well
---
Best Regards,
Strong Liu
On Mar 11, 2010, at 10:49 PM, Strong Liu wrote:
> I have fixed this issue https://jira.jboss.org/jira/browse/MPJDOCBOOK-52, and
> released a 2.2.3-SNAPSHOT
>
> i'd think this is becau
I have fixed this issue https://jira.jboss.org/jira/browse/MPJDOCBOOK-52, and
released a 2.2.3-SNAPSHOT
i'd think this is because Steve enabled the dtd validation in this 2.2.3 release
i will try to build hibernate trunk later (for the sync) with this snapshot
release
Steve, would you consider
looks there is some problem in the new 2.2.2 jdocbook plugin , I tried change
it to 2.2.1 and it works
On Mar 11, 2010, at 12:12 PM, Gail Badner wrote:
> The build seems to hang while building the doc, so this is not going to
> happen tonight.
>
> Here is the build log when it stops:
>
> [
10 matches
Mail list logo
