Ivy Publish Task Fails When XML Comments Exist Next to Dependency Declarations
------------------------------------------------------------------------------

                 Key: IVY-888
                 URL: https://issues.apache.org/jira/browse/IVY-888
             Project: Ivy
          Issue Type: Bug
          Components: Ant
    Affects Versions: 2.0.0-beta-2
         Environment: Java 5.0, Eclipse 3.3.2, Ant 1.7.0
            Reporter: Julian Klein
            Priority: Minor


When I have a dependency declared on the same line as a XML comment I receive 
the following error when attempting to call ivy:publish:

"RuntimeException: bad ivy file in cache"

Upon reviewing the generated "resolved descriptor" the line that causes this 
error looks like the following (see spring-aop line):

                <!-- Middleware - Spring Application Framework -->
                <dependency org="org.springframework" name="spring-core" 
rev="2.0.+" conf="runtime->default"/><!-- Core Module -->
                <dependency org="org.springframework" name="spring-jms" 
rev="2.0.+" conf="runtime->default;compile->*"/><!-- JMS Module -->
                <dependency org="org.springframework" name="spring-aop" 
rev="2.0.+" conf="runtime->default"<!-- AOP Module -->>

the source ivy.xml file that generated this erroneous output contains a line as 
follows:

                <!-- Middleware - Spring Application Framework -->
                <dependency org="org.springframework" name="spring-core" 
rev="2.0.+" conf="runtime->default"/><!-- Core Module -->
                <dependency org="org.springframework" name="spring-jms" 
rev="2.0.+" conf="runtime->default;compile->*"/><!-- JMS Module -->
                <dependency org="org.springframework" name="spring-aop" 
rev="2.0.+" conf="runtime->default"><!-- AOP Module -->

Now I am not sure if it is because of the XML comments or the greater than 
brackets inside the conf attributes.  Moving the comments to different lines 
resolves the issue.  Without the ivy publish task being used, everything else 
works fine (resolve/retrieve).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to