[jira] Resolved: (IVY-762) Type tag in poms not supported

["Maarten Coene (JIRA)" <ji...@apache.org>]

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

Maarten Coene resolved IVY-762.
-------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0-RC1

I've committed a fix using the solution suggested by Xavier which I hope will fix this issue.
I've added a simple JUnit test to test it.
Could you give it a try and reopen this issue if the problem still occurs?

> Type tag in poms not supported
> ------------------------------
>
>                 Key: IVY-762
>                 URL: https://issues.apache.org/jira/browse/IVY-762
>             Project: Ivy
>          Issue Type: Bug
>          Components: Maven Compatibility
>    Affects Versions: 2.0.0-beta-2
>            Reporter: Harald Braumann
>            Assignee: Maarten Coene
>             Fix For: 2.0-RC1
>
>
> Ivy does not support the <type> tag in poms and always uses jar as default. If there is a dependency on an artifact living in a maven2 repository, and that artifact has e.g. the  following dependency 
> <dependency>
>   <groupId>foo</groupId>
>   <artifactId>bar</artifactId>
>   <version>1.0</version>
>   <type>dll</type>
> </dependency
> Ivy resolves this transitive dependency as ``foo#bar;1.0!bar.jar'' instead of ``foo#bar;1.0!bar.dll''. This severly limits the use of maven2 repositories.
> As pointed out by Gilles Scokart on the mailing list, new types can be defined by maven plug-ins.
> In many cases, however, the type just corresponds to the file extension. A simple mapping of type = extension could be used as a first step to support the <type> tag. 

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