[jira] [Resolved] (CLOUDSTACK-520) Dependency jar names mismatch with install-non-oss.sh

["Rohit Yadav (JIRA)" <ji...@apache.org>]

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

Rohit Yadav resolved CLOUDSTACK-520.
------------------------------------

    Resolution: Fixed

While one can read that wiki suggests to rename them, fix applied on master and 4.1 to autorename nonoss deps.
                
> Dependency jar names mismatch with install-non-oss.sh
> -----------------------------------------------------
>
>                 Key: CLOUDSTACK-520
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-520
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Install and Setup
>    Affects Versions: 4.1.0
>         Environment: CentOS 6.3 x86_64
>            Reporter: gavin lee
>            Assignee: Rohit Yadav
>              Labels: build-failure, nonoss
>             Fix For: 4.1.0
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> 1> Following "How to build on master branch" : https://cwiki.apache.org/confluence/display/CLOUDSTACK/How+to+build+on+master+branch
> 2> get dependency jars for nonoss build
> 3> Exec install-non-oss.sh
> Expectation result:
> The dependency jars will be copied to local maven dependency repo
> Actual result:
> Some dependency jars were failed to copy
> Root cause:
>  jar name mismatch: 
> vim25.jar to vmware-vim25.jar
> apputils.jar to vmware-apputils.jar
> vim.jar to vmware-vim.jar

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira