> i have tried your test case because im experimenting similar issues with
> entity references (relative paths not resolved in a multiproject
> context). if i modify slighty your test case it doesnot fail anymore.
> the trick is to pass the absolute path to the maven pom tag. in
> your case :
>
> <m:pom projectDescriptor='${basedir}/otherProject.xml' var='otherPom'/>
Thanks Gilles, that does seem to work and I attached your comment to the bug
report I filed. However, I am still stymied because in our real workspace
the projects are at different levels within the directory hierarchy. In
project.xml, the relative reference to the location of the DTD seems always
to be evaluated against the basedir of the currently *executing* project,
not the location of the project.xml that contains the reference. Therefore
if I have:
/templates/entities.dtd
/projectA
/foo/bar/projectB
And projectB's pom references the dtd as:
<!DOCTYPE project SYSTEM "file:../../entities.dtd">
Then, I can run maven against projectB fine from its own root directory.
However, if projectA uses the m:pom tag to read in projectB's pom, I will
get an error because the location of the DTD is now evaluated with respect
to projectA's basedir.
So for now, XML entities is not a practical solution for us. Maybe the OASIS
XMLCatalog facility that now exists in Ant would provide a first-step
solution if it were to be incorporated into Maven.
--------------------------------------
David Zeleznik
Principal Architect
ILOG - Changing the rules of business
mailto:[EMAIL PROTECTED]
http://www.ilog.com
--------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
