ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Simon Brunning (JIRA)" <j...@apache.org>
Subject [jira] Reopened: (IVY-936) Can't use latest.release for pom dependencies
Date Wed, 08 Oct 2008 14:13:44 GMT

     [ https://issues.apache.org/jira/browse/IVY-936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Simon Brunning reopened IVY-936:
--------------------------------


As an example we are resolving spring-webmvc ver 2.5.5 from http://repo1.maven.org/maven2/

i.e. http://repo1.maven.org/maven2/org/springframework/spring-webmvc/2.5.5

As you can see there is a sources.jar at this location which is not being brought down using
the trunk version specified in the last comment. The attachment is a copy of the files from
the Ivy Cache after a clean resolve.

> Can't use latest.release for pom dependencies
> ---------------------------------------------
>
>                 Key: IVY-936
>                 URL: https://issues.apache.org/jira/browse/IVY-936
>             Project: Ivy
>          Issue Type: Bug
>          Components: Maven Compatibility
>    Affects Versions: 2.0-RC1
>            Reporter: Simon Brunning
>            Assignee: Maarten Coene
>             Fix For: trunk
>
>         Attachments: spring-webmvc-example-resolution-from-ivy-cache.zip
>
>
> When using the ibibio resolver, the generated ivy.xml doesn't include source and javadoc
artifacts declaration.
> AFAIU the Maven doc, the pom.xml doesn't declare them. They declare themself by being
available or not.
> IvyDE does this check itself, so it works fine in Eclipse. So some code should be ported
from IvyDE to Ivy. Then we will be able to get the source also with an ant task.

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


Mime
View raw message