jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (JCR-162) bad project.xml
Date Tue, 05 Jul 2005 20:03:18 GMT
     [ http://issues.apache.org/jira/browse/JCR-162?page=all ]
Jukka Zitting resolved JCR-162:

    Resolution: Fixed

Fixed in revision 209310.

It's strange that my Maven installation reported no problems about this. Could this be some
weird corner case in the XML parser?

Anyhow, I actually solved the problem by removing the entire comment section that referenced
to the previous version of the JCR API.

Many thanks, Fabrizio, for reporting this!

> bad project.xml
> ---------------
>          Key: JCR-162
>          URL: http://issues.apache.org/jira/browse/JCR-162
>      Project: Jackrabbit
>         Type: Bug
>   Components: API
>     Reporter: fabrizio giustina
>     Assignee: Jukka Zitting
>     Priority: Trivial
>  Attachments: api-projectxml.diff
> project.xml in the "api" module actually contains an error (nested comment) and can't
be read by maven.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message