[jira] [Comment Edited] (IVY-1081) Another wrong error message when publishing

["David Chisholm (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/IVY-1081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14557802#comment-14557802 ] 

David Chisholm edited comment on IVY-1081 at 5/25/15 4:23 AM:
--------------------------------------------------------------

I ran into the same problem, but I think the issue is the slash path separator and not the variable reference.  I had a variable whose value was "build/foo.jar".  When I replaced the variable with this value in the publish task, I got the same error.  It wasn't until I removed the slash separator that the error cleared.  I changed the variable to "foo.jar", and then the variable worked fine too.

versions: jdk 1.8 / ant 1.8 / ivy 2.4

*UPDATE*

We're both using the task incorrectly.  Our problem is that we're not using any patterns in the name.  You have to use an ivy pattern and not the actual/absolute jar file name.

However, I agree that the error message is misleading.  Ivy should catch this exception and tack on some additional help information about using this task.


was (Author: dachiz):
I ran into the same problem, but I think the issue is the slash path separator and not the variable reference.  I had a variable whose value was "build/foo.jar".  When I replaced the variable with this value in the publish task, I got the same error.  It wasn't until I removed the slash separator that the error cleared.  I changed the variable to "foo.jar", and then the variable worked fine too.

versions: jdk 1.8 / ant 1.8 / ivy 2.4

> Another wrong error message when publishing
> -------------------------------------------
>
>                 Key: IVY-1081
>                 URL: https://issues.apache.org/jira/browse/IVY-1081
>             Project: Ivy
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.1.0-RC1
>            Reporter: hem006
>
>   <target name="publish">
> ...
>     <copy file="${jar.dir}/${artifact.name}.jar" todir="." />
>     <ivy:publish artifactspattern="${jar.dir}/${artifact.name}" resolver="shared" pubrevision="${ivy.new.revision}" />
> ...
>   </target>
> leads to the following output
> ...\build.xml:26: impossible to publish artifacts for mycompany.com#MyComponent;working@MY-PC: java.lang.IllegalStateException: bad ivy file for mycompany.com#MyComponent;working@MY-PC: [...]/MyComponent: java.text.ParseException: [[Fatal Error] :1:1: Content is not allowed in prolog. in file:[...]/MyComponent/
> ]
> Note that it is the ivy:publish task that fails, whereas the ant copy works as intended. Now, the error message sends you hunting in the ivy file - maybe there is some malformed xml...? However, the problem turns out to be related to the ${jar.dir} variable reference in the 'artifactspattern' parameter. The same variable caused no trouble in the line before (${jar.dir} exists, and the artifact is present both in ${jar.dir} and in the working directory), so what is wrong?
> Remove the variable reference, and everything works fine. Nothing is wrong with the ivy file, and it is difficult to see what a typical xml parser exception has to do with the problem.
> This is the second bug I've experienced - and reported - in a couple of days, relating to Ivy providing wrong feedback in case of an error. Maybe it is time for a review of the code, related to error handling?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)