hi morgan

attached is a patch which allows the ant tag to build. (you'll probably need to go through all the tags and change the other project.xml files in a similar way.)

Attachment: jelly-tags.patch
Description: Binary data


On Monday, January 20, 2003, at 06:55 PM, Morgan Delagrange wrote:

--- robert burrell donkin
<[EMAIL PROTECTED]> wrote:
On Monday, January 20, 2003, at 05:33 PM, Morgan
Delagrange wrote:

--- James Strachan <[EMAIL PROTECTED]>
wrote:
From: "Morgan Delagrange" <[EMAIL PROTECTED]>
--- James Strachan <[EMAIL PROTECTED]>
wrote:
I'm gonna sit on the fence a little as I agree
with
both of you. Before a
1.0 release I'd like to

* provide a simple build to build and test all
the
libraries (hopefully
using Maven reactor though anything would do).
This
can help in refactoring,
testing that we don't break things.
Everything appears to be correct in the reactor.
I
verified via debug statements that the parse
fails
when MavenUtils.getProject(File,
MavenJellyContext,
boolean) attempts to parse the projectDescriptor
with
Betwixt via the BeanReader.parse(File) method.
That
method seems to be inherited from Digester, and
looks
fine:

    public Object parse(File file)
      throws IOException, SAXException {
        configure();
        InputSource input =
          new InputSource(new
FileInputStream(file));
        input.setSystemId("file://" +
          file.getAbsolutePath());
        getXMLReader().parse(input);
        return (root);
    }

Wierd.
Is this one of those problems of the current
working
directory being
different (when built using the reactor) to what
it
is when just building
one library at a time?

James
That's the apparent difference, although
Digester's
invocation of the InputSource.setSystemId(String)
method should have made this a non-issue.
if you can tell me a simple way to reproduce the
problem, i'd be willing
to take a look and see if i can come up with
anything.

- robert
I don't have a simple test case for it.  If you go to
jakarta-commons-sandbox/jelly/jelly-tags/ant and run
"maven java:compile", there is no problem.  However if
you run "maven tags-build" from
jakarta-commons-sandbox/jelly, Maven will fail to open
the commonsDependencies.ent file referenced in the ant
build script.

- Morgan

=====
Morgan Delagrange
http://jakarta.apache.org/taglibs
http://jakarta.apache.org/commons
http://axion.tigris.org
http://jakarta.apache.org/watchdog

__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED].
org>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED].
org>


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to