You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by "Hans Dockter (JIRA)" <ji...@apache.org> on 2008/09/11 17:29:47 UTC
[jira] Created: (IVY-902) Maven Snapshot resolution does not work
with dual resolver
Maven Snapshot resolution does not work with dual resolver
----------------------------------------------------------
Key: IVY-902
URL: https://issues.apache.org/jira/browse/IVY-902
Project: Ivy
Issue Type: Bug
Components: Maven Compatibility
Reporter: Hans Dockter
Priority: Blocker
Fix For: 2.0-RC1
Here is an example for an unsucessful retrieval of a snapshot dependency when using a dual resolver. The same example works fine, if only the IBiblio resolver is used.
{code:xml}
<ivysettings>
<settings defaultResolver="main" validate="false"/>
<resolvers>
<dual name="main">
<ibiblio name="ivy" m2compatible="true" root="http://snapshots.jboss.org/maven2"/>
<url name="artifact" m2compatible="true">
<artifact pattern="http://snapshots.jboss.org/maven2/[module]/[revision]/[artifact]-[revision].[ext]"/>
</url>
</dual>
</resolvers>
</ivysettings>
{code}
{code:xml}
<ivy-module version="2.0">
<info organisation="apache" module="hello-ivy"/>
<dependencies>
<dependency org="jboss.jbossws-common" name="jbossws-common" rev="1.0.5-SNAPSHOT"/>
</dependencies>
</ivy-module>
{code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (IVY-902) Maven Snapshot resolution does not work
with dual resolver
Posted by "Hans Dockter (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12634595#action_12634595 ]
Hans Dockter commented on IVY-902:
----------------------------------
I was aware that only the IBibilio resolver is capable of metadata handling. But in this case I thought it would work as the actual pom resolving is still done by the IBibilio resolver. Anyway, the work around is ridiculously simple and obvious. But for some reason I haven't figured this out. Thanks.
Right now I'm almost done with an Ivy2Pom converter (which is more powerful than the one currently shipped with Ivy). When the code is working I will discuss this in the Ivy dev list.
I'm curious to learn about the difficulties for generic metadata support. Again, I will raise this issue in the dev list.
> Maven Snapshot resolution does not work with dual resolver
> ----------------------------------------------------------
>
> Key: IVY-902
> URL: https://issues.apache.org/jira/browse/IVY-902
> Project: Ivy
> Issue Type: Bug
> Components: Maven Compatibility
> Reporter: Hans Dockter
> Assignee: Xavier Hanin
> Priority: Blocker
>
> Here is an example for an unsucessful retrieval of a snapshot dependency when using a dual resolver. The same example works fine, if only the IBiblio resolver is used.
> {code:xml}
> <ivysettings>
> <settings defaultResolver="main" validate="false"/>
> <resolvers>
> <dual name="main">
> <ibiblio name="ivy" m2compatible="true" root="http://snapshots.jboss.org/maven2"/>
> <url name="artifact" m2compatible="true">
> <artifact pattern="http://snapshots.jboss.org/maven2/[module]/[revision]/[artifact]-[revision].[ext]"/>
> </url>
> </dual>
> </resolvers>
> </ivysettings>
> {code}
> {code:xml}
> <ivy-module version="2.0">
> <info organisation="apache" module="hello-ivy"/>
> <dependencies>
> <dependency org="jboss.jbossws-common" name="jbossws-common" rev="1.0.5-SNAPSHOT"/>
> </dependencies>
> </ivy-module>
> {code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (IVY-902) Maven Snapshot resolution does not work
with dual resolver
Posted by "Xavier Hanin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Xavier Hanin resolved IVY-902.
------------------------------
Resolution: Invalid
Fix Version/s: (was: 2.0-RC1)
Assignee: Xavier Hanin
The problem is not the dual resolver, it's the url resolver used for artifacts. SNAPSHOT dependencies are currently supported only by ibiblio resolver (which should really be renamed to maven resolver IMO). So if you do sg like this:
{code}
<ivysettings>
<settings defaultResolver="main" validate="false"/>
<resolvers>
<dual name="main">
<ibiblio name="ivy" m2compatible="true" root="http://snapshots.jboss.org/maven2"/>
<ibiblio name="artifact" m2compatible="true" root="http://snapshots.jboss.org/maven2"/>
</dual>
</resolvers>
</ivysettings>
{code}
it works as expected. Hence I mark this issue as resolved invalid. And if you do not cover all your use cases with that, feel free to discuss it on the mailing list, we'll see if SNAPSHOT support is possible in other resolvers (but it would require maven-metadata.xml support too, which is not easy in generic resolvers).
> Maven Snapshot resolution does not work with dual resolver
> ----------------------------------------------------------
>
> Key: IVY-902
> URL: https://issues.apache.org/jira/browse/IVY-902
> Project: Ivy
> Issue Type: Bug
> Components: Maven Compatibility
> Reporter: Hans Dockter
> Assignee: Xavier Hanin
> Priority: Blocker
>
> Here is an example for an unsucessful retrieval of a snapshot dependency when using a dual resolver. The same example works fine, if only the IBiblio resolver is used.
> {code:xml}
> <ivysettings>
> <settings defaultResolver="main" validate="false"/>
> <resolvers>
> <dual name="main">
> <ibiblio name="ivy" m2compatible="true" root="http://snapshots.jboss.org/maven2"/>
> <url name="artifact" m2compatible="true">
> <artifact pattern="http://snapshots.jboss.org/maven2/[module]/[revision]/[artifact]-[revision].[ext]"/>
> </url>
> </dual>
> </resolvers>
> </ivysettings>
> {code}
> {code:xml}
> <ivy-module version="2.0">
> <info organisation="apache" module="hello-ivy"/>
> <dependencies>
> <dependency org="jboss.jbossws-common" name="jbossws-common" rev="1.0.5-SNAPSHOT"/>
> </dependencies>
> </ivy-module>
> {code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.