[jbosstools-issues] [JBoss JIRA] (JBDS-2797) .ini upgrade issue for 7.0.1 users
[
https://issues.jboss.org/browse/JBDS-2797?page=com.atlassian.jira.plugin....
]
Mickael Istria commented on JBDS-2797:
--------------------------------------
We could release an installer for JBDS 7.0.1... would that solve this
problem?
It wouldn't be enough. Problem seems to happen when the update is performed. Releasing
an installer wouldn't prevent people from updating.
It seems to me that the "laucher" part is not specific to JBDS. Can someone
using Mac OS try the following:
# get Kepler SR0
# see content of launcher in eclipse.ini
# Run "Check for update" (ensure it installs Kepler SR1)
# Restart and check value of "launcher" in eclipse.ini.
Those values must be different. If they're not, it means that update mechanism is the
culprit, if not, it means that it's specific to JBDS.
For the discovery site, I tend to think it's a JBDS bug, which might be independent of
the OS.
.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