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

Gintas Grigelionis commented on IVY-1576:
-----------------------------------------

Greg, could you please open a PR on GitHub?

> Ivy retrieve Maven Jars with Classifiers
> ----------------------------------------
>
>                 Key: IVY-1576
>                 URL: https://issues.apache.org/jira/browse/IVY-1576
>             Project: Ivy
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.4.0
>         Environment: All Environments
>            Reporter: Greg Perry
>            Priority: Major
>         Attachments: PomModuleDescriptorParser.java
>
>
> Steps to reproduce :
> using ivy 2.4.0
> {noformat}
> java -jar ivy.jar -dependency "net.java.jinput" "jinput" "2.0.7" -retrieve  
> "jinput.ivy/[originalname](-[classifier]).[ext]"
> {noformat}
> returns the following jars
> jinput-2.0.7-javadoc-javadoc.jar
> jinput-2.0.7-sources-sources.jar
> jinput-2.0.7.jar
> jinput-platform-2.0.7-natives-osx-natives-osx.jar
> jutils-1.0.0.jar
> using either *maven* or *gradle* both come back with 2 additional  "native" 
> jars
> jinput-2.0.7.jar
> *jinput-platform-2.0.7-natives-linux.jar*
> jinput-platform-2.0.7-natives-osx.jar
> *jinput-platform-2.0.7-natives-windows.jar*
> jutils-1.0.0.jar
> This happens for a variety of popular projects javacv, dl4j, etc ..
> pom is here - 
> http://central.maven.org/maven2/net/java/jinput/jinput/2.0.5/jinput-2.0.5.pom
> I can imagine that the additional artifacts can explicitly be put into an 
> ivy.xml, but this burdens the client with the complexity of having to 
> document all missing artifacts.  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to