[GRADLE-935] Ivy.xml file created with 1.0 ivy-module version rather than 2.0 Created: 10/May/10  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: 0.8, 0.9
Fix Version/s: None

Type: Bug
Reporter: Michael Parmeley Assignee: Unassigned
Resolution: Won't Fix Votes: 2

Attachments: PNG File Screen shot 2010-06-08 at 9.26.12 AM.png    


When running the uploadArchives task the ivy.xml file is created with a 1.0 ivy module version, it is created as:

<ivy-module version="1.0">

Should be:

<ivy-module version="2.0">

Comment by Hans Dockter [ 07/Jun/10 ]

The ivy modules generated with ivy 2.1.0 use 1.0 for the ivy-module version. Why should it be 2.0?

Comment by Michael Parmeley [ 08/Jun/10 ]

This page shows that the version attribute for ivy-module should be 2.0 for Ivy 2.1.0 (see attached screenshot):


Comment by Hans Dockter [ 24/Jun/10 ]

I see your point. The strange thing is that ivy internally still uses 1.0 when producing ivy.xml files. See https://svn.apache.org/repos/asf/ant/ivy/core/tags/2.1.0/src/java/org/apache/ivy/plugins/parser/xml/XmlModuleDescriptorWriter.java and the write method. The ivy-module version is hard coded. Therefore I postpone this issue to 1.0. I have filed an Ivy Jira: https://issues.apache.org/jira/browse/IVY-1199

Comment by Hans Dockter [ 28/Jun/10 ]

IVY-1199 is fixed. So as soon as we switch to the yet to be released Ivy-2.2.0 this will be solved.

Comment by Benjamin Muschko [ 15/Nov/16 ]

As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.

We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.

Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:

  • Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
  • Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

Comment by Benjamin Muschko [ 10/Feb/17 ]

Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved.

Generated at Wed Jun 30 11:42:41 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.