ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maarten Coene (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (IVY-936) Can't use latest.release for pom dependencies
Date Tue, 21 Oct 2008 22:00:48 GMT

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

Maarten Coene resolved IVY-936.
-------------------------------

    Resolution: Fixed

No further news from Simon, so I'll mark this as fixed because it works for me.

This problem may occur for instance if the the default ibiblio patterns are overwritten and
the classifier token isn't specified.
But without seeing the settings.xml file it is hard to see what's going wrong.

> 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