You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by "Harald Braumann (JIRA)" <ji...@apache.org> on 2008/03/09 17:05:46 UTC
[jira] Created: (IVY-762) Type tag in poms not supported
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.
[jira] Assigned: (IVY-762) Type tag in poms not supported
Posted by "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 reassigned IVY-762:
---------------------------------
Assignee: Maarten Coene
> 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
>
> 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.
[jira] Commented: (IVY-762) Type tag in poms not supported
Posted by "Xavier Hanin (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Resolved: (IVY-762) Type tag in poms not supported
Posted by "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.
[jira] Commented: (IVY-762) Type tag in poms not supported
Posted by "Maarten Coene (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12580152#action_12580152 ]
Maarten Coene commented on IVY-762:
-----------------------------------
An additional problem is that Ivy doesn't has support for the type attribute on <dependency> elements in Ivy files neither. As you can see on http://ant.apache.org/ivy/history/latest-milestone/ivyfile/dependency.html, it's not possible to specify the desired type of the dependency.
> 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.