ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xavier Hanin (JIRA)" <j...@apache.org>
Subject [jira] Commented: (IVY-762) Type tag in poms not supported
Date Mon, 24 Mar 2008 19:55:26 GMT

    [ https://issues.apache.org/jira/browse/IVY-762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12581656#action_12581656
] 

Xavier Hanin commented on IVY-762:
----------------------------------

I think we could use the artifact element in dependency to implement this. 

> 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
>
> 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.


Mime
View raw message