[
https://issues.apache.org/jira/browse/IVY-1565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16123415#comment-16123415
]
Arnaud Jeansen commented on IVY-1565:
-------------------------------------
[~twogee] :-)
Frankly, I was on the fence as to the best place to report the issue. It could
be argued both ways so I ended up creating the ticket here, as I imagined that
other repository managers like Nexus or Archiva may have the same features /
issue.
Anyway, there is no harm in also asking Artifactory to upgrade the dependency,
so I did it with https://www.jfrog.com/jira/browse/RTFACT-14766 :-)
I must say it is a pleasure to report tickets here, thanks to both of you for
the speed and professionalism. (y)
Feel free to close the ticket as rejected. I understand your position and I
already have a local workaround...
> Enable XmlModuleDescriptorParser to skip the ivy-module version check
> ---------------------------------------------------------------------
>
> Key: IVY-1565
> URL: https://issues.apache.org/jira/browse/IVY-1565
> Project: Ivy
> Issue Type: Improvement
> Reporter: Arnaud Jeansen
> Priority: Minor
>
> I have a very specific use case where I rewrite ivy files to pom files on the
> fly on a binary repository manager (artifactory).
> Basically, when an ivy-$version.xml file is published, I launch the
> equivalent of the Ant makePom task and save a pom file in the same directory
> as the ivy file.
> I am relying on an interesting feature from Artifactory called "user
> plugins", where groovy scripts are executed on some specific events (e.g.
> upload of a file)
> A sample implementation even exists at
> https://github.com/JFrogDev/artifactory-user-plugins/tree/master/descriptors/ivy2pom
> However, my problem is that the binary repository manager has ivy-2.2 as its
> library. So any attempt to transform later ivy module descriptors (versions
> 2.3 and 2.4) fail with:
> {noformat}
> java.text.ParseException: [invalid version 2.4 in
> file:/tmp/foo-5.15.9-2436013575810429206.ivy]
> {noformat}
> Is there any interest in providing a way to skip the version check in
> XmlModuleDescriptorParser$Parser#ivyModuleStarted or enable callers to modify
> ALLOWED_VERSIONS and authorize later versions?
> I have looked for a workaround for quite some time but:
> * ALLOWED_VERSIONS is final, so there is no way to switch to a new List with
> the versions I want
> * ALLOWED_VERSIONS is an AbstractList, so _add_ and _addAll_ are unimplemented
> * Subclassing and overriding ivyModuleStarted fails because it works with a
> lot of private fields directly
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
