|
||||||||
|
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 |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
OK - I thought the solution to this would be to update the plugin so that the -all option was not called on sgvtool for newversion - but it turned out this did not fix the problem.
In the end the issue was related to just the DYLIB_CURRENT_VERSION - which was being set to 201402181110 and there is no option to alter the sgvtool to not do this.
In the end we have altered our target for the core framework to use a xcconfig file and set DYLIB_CURRENT_VERSION to 1 in this file and made sure it is no longer in the project file for the core target. By doing this sgvtool does find the value for DYLIB_CURRENT_VERSION and therefore doesn't update it.