[jbosstools-issues] [JBoss JIRA] (JBDS-2797) .ini upgrade issue for 7.0.1 OSX users

[Martin Malina (JIRA)]

    [ https://issues.jboss.org/browse/JBDS-2797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12823587#comment-12823587 ] 

Martin Malina commented on JBDS-2797:
-------------------------------------

[~maxandersen] so you're saying that in the past we let tycho build the Info.plist file and then replaced it with ours which is a hack. So now you prefer to leave it as is and use just jbdevstudio.ini for custom stuff. OK, but in that case we should still remove the custom Info.plist from git if it's not used.
                
> .ini upgrade issue for 7.0.1 OSX users
> --------------------------------------
>
>                 Key: JBDS-2797
>                 URL: https://issues.jboss.org/browse/JBDS-2797
>             Project: Developer Studio (JBoss Developer Studio)
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: build, installer
>    Affects Versions: 7.0.1.GA
>            Reporter: Max Rydahl Andersen
>            Assignee: Denis Golovin
>            Priority: Critical
>             Fix For: 7.1.0.Beta1
>
>
> User noticed issues with 7.0.0 to 7.0.1 updates at https://community.jboss.org/message/841477#841477 that needs investigation.
> The post is about osx but I don't think this is limited to this OS, just that OSX has a different java behavior.
> Worrisome issues are:
> development url used in GA update:
> -Djboss.discovery.directory.url=https://devstudio.jboss.com/updates/7.0-development/devstudio-directory.xml
> startup/launcher directories are hardcoded in the .ini file:
> -startup
> ../../../plugins/org.eclipse.equinox.launcher_1.3.0.v20130327-1440.jar
> --launcher.library
> ../../../plugins/org.eclipse.equinox.launcher.cocoa.macosx.x86_64_1.1.200.v20130807-1835
> Have these been forgotten/set wrong in the update or is this some specific update path that is failing ?

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