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

[Max Rydahl Andersen (JIRA)]

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

Max Rydahl Andersen commented on JBDS-2797:
-------------------------------------------

yes, which means both are things we missed and should make sure doesn't happen at JBDS 7.1 release AND we need to update both development and product discovery.xml from now on for 7.0.x users.

7.1 needs to use a different one.

btw. this actually makes central fail now - Update page cannot find anything.

This is an example of why I think it is *wrong* for us to rely on .ini to contain product overrides and have -development paths hardcoded in them - stuff like this gets forgotten ;(
                
> .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