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

[Mickael Istria (JIRA)]

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

Mickael Istria commented on JBDS-2797:
--------------------------------------

The laucher/JDK issue is specific to Mac and was fixed for Kepler SR1: https://bugs.eclipse.org/bugs/show_bug.cgi?id=411361
It looks like the update mechanism doesn't update the launcher path in the .ini file. I'm not sure what would be the correct behaviour regarding launcher during update.
Anyway, if it is a bug, it is on Eclipse side.

About the discovery path, it looks a bug to me. Needs to verify what is the value in a "vanilla" JBDS to see whether it affects all 7.0.1 or just the installation scenario described on forum.
                
> .ini upgrade issue for 7.0.1 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: Nick Boldt
>            Priority: Critical
>
> 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