You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ivy-commits@incubator.apache.org by "Jeffrey Blatttman (JIRA)" <ji...@apache.org> on 2007/05/12 00:59:15 UTC

[jira] Created: (IVY-501) unable to resolve snapshot versions

unable to resolve snapshot versions
-----------------------------------

                 Key: IVY-501
                 URL: https://issues.apache.org/jira/browse/IVY-501
             Project: Ivy
          Issue Type: Bug
         Environment: jdk 1.5
            Reporter: Jeffrey Blatttman
            Priority: Blocker


ivy cannot resolve maven2 "snapshot" versioning. i am actually unclear whether there is some way to configure this to work, but the expectations is that if one sets m2compatible="true" for the resolver, that the m2 snapshot versioning should just work without any other tweaks.

i'd be glad to make this a lower priority than blocker if someone can explain the manual configuration to make it work (i couldn't figure it out from the docs). 

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


[jira] Commented: (IVY-501) unable to resolve snapshot versions

Posted by "Jeffrey Blatttman (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/IVY-501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12495214 ] 

Jeffrey Blatttman commented on IVY-501:
---------------------------------------

p.s. i made this a blocker as snapshots are an integral part of maven2 dependencies. and since m2 is ruling the world right now, we are forced to work with their repos.

> unable to resolve snapshot versions
> -----------------------------------
>
>                 Key: IVY-501
>                 URL: https://issues.apache.org/jira/browse/IVY-501
>             Project: Ivy
>          Issue Type: Bug
>         Environment: jdk 1.5
>            Reporter: Jeffrey Blatttman
>            Priority: Blocker
>
> ivy cannot resolve maven2 "snapshot" versioning. i am actually unclear whether there is some way to configure this to work, but the expectations is that if one sets m2compatible="true" for the resolver, that the m2 snapshot versioning should just work without any other tweaks.
> i'd be glad to make this a lower priority than blocker if someone can explain the manual configuration to make it work (i couldn't figure it out from the docs). 

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


[jira] Commented: (IVY-501) unable to resolve snapshot versions

Posted by "Xavier Hanin (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/IVY-501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12495297 ] 

Xavier Hanin commented on IVY-501:
----------------------------------

For some exaplanations about maven 2 SNAPSHOT versions, see this thread:
http://www.nabble.com/understanding-SNAPSHOT-versions-tf3731422s177.html

I propose that by default we deal with the two kind of versioning, and when we'll upgrade Ivy to read maven metadata files (required for maven proxy compatibility for example, for which there's already an issue opened), we will optimize this as well.

> unable to resolve snapshot versions
> -----------------------------------
>
>                 Key: IVY-501
>                 URL: https://issues.apache.org/jira/browse/IVY-501
>             Project: Ivy
>          Issue Type: Bug
>         Environment: jdk 1.5
>            Reporter: Jeffrey Blatttman
>            Priority: Blocker
>
> ivy cannot resolve maven2 "snapshot" versioning. i am actually unclear whether there is some way to configure this to work, but the expectations is that if one sets m2compatible="true" for the resolver, that the m2 snapshot versioning should just work without any other tweaks.
> i'd be glad to make this a lower priority than blocker if someone can explain the manual configuration to make it work (i couldn't figure it out from the docs). 

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


[jira] Updated: (IVY-501) unable to resolve snapshot versions

Posted by "Gilles Scokart (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/IVY-501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gilles Scokart updated IVY-501:
-------------------------------

    Fix Version/s: 2.0

> unable to resolve snapshot versions
> -----------------------------------
>
>                 Key: IVY-501
>                 URL: https://issues.apache.org/jira/browse/IVY-501
>             Project: Ivy
>          Issue Type: Bug
>         Environment: jdk 1.5
>            Reporter: Jeffrey Blattman
>            Priority: Blocker
>             Fix For: 2.0
>
>
> ivy cannot resolve maven2 "snapshot" versioning. i am actually unclear whether there is some way to configure this to work, but the expectations is that if one sets m2compatible="true" for the resolver, that the m2 snapshot versioning should just work without any other tweaks.
> i'd be glad to make this a lower priority than blocker if someone can explain the manual configuration to make it work (i couldn't figure it out from the docs). 

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


[jira] Commented: (IVY-501) unable to resolve snapshot versions

Posted by "Xavier Hanin (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/IVY-501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12495250 ] 

Xavier Hanin commented on IVY-501:
----------------------------------

I think there a two things to do as a workaround:
- set the changing pattern on your resolver to changingPattern=".*SNAPSHOT"
This will tell Ivy that all revisions ending with SNAPSHOT are considered as changing revisions, thus Ivy will check if they have changed each time you call resolve
- add a VersionMatcher inspired by the SubVersionMatcher, except that it considers revisions ending with 'SNAPSHOT' instead of a '+'
This will tell Ivy to look for revisions with a suffix after the SNAPSHOT. For this step I'm not really sure if this is necessary or not, since I do not understand properly how SNAPSHOT versions work in maven: sometimes they have just the SNAPSHOT keyword, sometimes they have a timestamp I think.

I will ask on the maven list if they can point me to a documentation explaining exactly how it works.

> unable to resolve snapshot versions
> -----------------------------------
>
>                 Key: IVY-501
>                 URL: https://issues.apache.org/jira/browse/IVY-501
>             Project: Ivy
>          Issue Type: Bug
>         Environment: jdk 1.5
>            Reporter: Jeffrey Blatttman
>            Priority: Blocker
>
> ivy cannot resolve maven2 "snapshot" versioning. i am actually unclear whether there is some way to configure this to work, but the expectations is that if one sets m2compatible="true" for the resolver, that the m2 snapshot versioning should just work without any other tweaks.
> i'd be glad to make this a lower priority than blocker if someone can explain the manual configuration to make it work (i couldn't figure it out from the docs). 

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