Yes, if the parser knows the URL of the parsed bit, it can resolve
relative entities...
paul
Phil Steitz wrote:
IIRC, the problem results from the fact that the entity is referenced
via a relative path. Moving to a URL or File reference would require
either an absolute path or that the resour
IIRC, the problem results from the fact that the entity is referenced
via a relative path. Moving to a URL or File reference would require
either an absolute path or that the resource be loaded from a remote
URL, which would make offline builds fail. Could be there is a simple
trick to make this
You wouldn't need to read Xerces in any line... you just need to use an
org.xml.sax.InputSource which has a properly set system-id.
new InputSource(URL) or new InputSource(File) does make it for you.
Generally such resolution error happen to be when an
InputSource(InputStream) is used for which
Hi Phil,
Yes, I'll try to find a solution to use maven 1.1 to build the commons.
I'll certainly need to readd xerces to the core :-( to allow you to use
XML entities.
cheers
arnaud
On 2/28/06, Phil Steitz <[EMAIL PROTECTED]> wrote:
>
> Both of these requirements - maven 1.0.2 and xdoc 1.9.
Yep, an updated xdoc plugin is required. I struck this with digester and
commons-logging. The best solution is to add this dependency to the
project's project.xml:
maven
maven-xdoc-plugin
1.9.2
http://maven.apache.org/maven-1.x/reference/plugins/xdoc/
plugin
Both of these requirements - maven 1.0.2 and xdoc 1.9.2 - are included
in the "getting and installing maven" section here
http://jakarta.apache.org/commons/building.html
Thanks in advance, Arnaud for any help removing the 1.0.2 restriction.
Phil
--
Verified.
I updated JEXL's documentation so that this doesn't get lost for at least
this project.
On 2/28/06, Arnaud HERITIER <[EMAIL PROTECTED]> wrote:
>
> I hink that you need :
> maven 1.0.2 + xdoc 1.9.2
>
> Arnaud
>
> On 2/28/06, Dion Gillard <[EMAIL PROTECTED]> wrote:
> >
> > Arnaud,
> >
> >
I hink that you need :
maven 1.0.2 + xdoc 1.9.2
Arnaud
On 2/28/06, Dion Gillard <[EMAIL PROTECTED]> wrote:
>
> Arnaud,
>
> if it's a custom xdoc plugin on top of 1.0.2 - which version should I use?
>
> On 2/28/06, Arnaud HERITIER <[EMAIL PROTECTED]> wrote:
> > Dion,
> >
> > I think that you nee
Arnaud,
if it's a custom xdoc plugin on top of 1.0.2 - which version should I use?
On 2/28/06, Arnaud HERITIER <[EMAIL PROTECTED]> wrote:
> Dion,
>
> I think that you need to upgrade the xdoc plugin. The one bundled in maven
> 1.0.2 is too old. I'm trying to have maven 1.1 fully compatible with
Ok, so should I use 1.0.2 or 1.1 with commons-site?
On 2/28/06, Arnaud HERITIER <[EMAIL PROTECTED]> wrote:
> Dion,
>
> I think that you need to upgrade the xdoc plugin. The one bundled in maven
> 1.0.2 is too old. I'm trying to have maven 1.1 fully compatible with commons
> site
>
> Arnaud
Dion,
I think that you need to upgrade the xdoc plugin. The one bundled in maven
1.0.2 is too old. I'm trying to have maven 1.1 fully compatible with commons
site
Arnaud
On 2/28/06, Dion Gillard <[EMAIL PROTECTED]> wrote:
>
> Maven 1.0.2 fails for a different reason:
>
> xdoc:jelly-trans
Maven 1.0.2 fails for a different reason:
xdoc:jelly-transform:
[echo] Generating
C:/source/jakarta/jakarta-commons/jexl/target/docs/changelog-report.html
from C:\source\jakarta\ja
karta-commons\jexl\target\generated-xdocs\changelog-report.xml
Could not find the class: org.apache.commons.jelly
Brett or someone more knowledgeable can explain in detail why, but you
need to either use maven 1.0.2 or get a more tolerant parser to be
loaded.
Phil
On 2/27/06, Dion Gillard <[EMAIL PROTECTED]> wrote:
> Ok, that's what I had, but I still get the following error:
>
> BUILD FAILED
> File.. C:
Ok, that's what I had, but I still get the following error:
BUILD FAILED
File.. C:\Documents and Settings\Dion
Gillard\.maven\cache\maven-xdoc-plugin-1.9.2\plugin.jelly
Element... x:parse
Line.. 471
Column -1
Error on line 18 of document : Relative URI
"../../commons-build/menus/menus
Dion Gillard wrote:
I've tried to build the site for JEXL, but obviously have the
commons-build directory checked out in the wrong location.
Is it documented anywhere what the directory structure must be?
You can find it here:
http://jakarta.apache.org/commons/building.html#Checking%20out%20th
15 matches
Mail list logo