[
https://issues.jboss.org/browse/JBDS-1648?page=com.atlassian.jira.plugin....
]
Nick Boldt edited comment on JBDS-1648 at 11/1/11 3:56 PM:
-----------------------------------------------------------
Sadly, that didn't work. I tried to have two features with the following platform
filters:
{code}
<feature id="com.jboss.jbds.mylyn.x86_64.feature"
label="Mylyn (Selected) [x86_64]"
version="1.0.0.v20111101-1417-Final" provider-name="JBoss by Red Hat"
os="linux" arch="x86_64">
<feature id="com.jboss.jbds.mylyn.x86.feature"
label="Mylyn (Selected) [x86]"
version="1.0.0.v20111101-1417-Final" provider-name="JBoss by Red Hat"
os="linux,macosx,win32" arch="x86">
{code}
And while the filter prevented me from installing com.jboss.jbds.mylyn.x86_64.feature on
Win7_64, I was still able to install com.jboss.jbds.mylyn.x86.feature because the
jbdevstudio win32 installer runs in 32-bit mode, and therefore the arch == x86:
{code}eclipse.commands=-os
win32
-ws
win32
-arch
x86
{code}
Tried some other hacks and workarounds:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=300577
https://bugs.eclipse.org/bugs/show_bug.cgi?id=333444
So, I need some other way to have JBDS know that it's running on Vista or 7 64-bit
despite the fact that the application (jbdevstudio.exe) is running in 32-bit mode.
http://www.grimadmin.com/article.php/batchfile-easy-way-to-detect-os-version
Or maybe look at patching SWT?
https://bugs.eclipse.org/bugs/show_bug.cgi?id=333630#c5
https://bugs.eclipse.org/bugs/attachment.cgi?id=193993&action=diff
http://dev.eclipse.org/viewcvs/viewvc.cgi/org.eclipse.swt/Eclipse%20SWT/w...
http://git.eclipse.org/c/platform/eclipse.platform.swt.git/tree/bundles/o...
was (Author: nickboldt):
Sadly, that didn't work. I tried to have two features with the following platform
filters:
{code}
<feature id="com.jboss.jbds.mylyn.x86_64.feature"
label="Mylyn (Selected) [x86_64]"
version="1.0.0.v20111101-1417-Final" provider-name="JBoss by Red Hat"
os="linux" arch="x86_64">
<feature id="com.jboss.jbds.mylyn.x86.feature"
label="Mylyn (Selected) [x86]"
version="1.0.0.v20111101-1417-Final" provider-name="JBoss by Red Hat"
os="linux,macosx,win32" arch="x86">
{code}
And while the filter prevented me from installing com.jboss.jbds.mylyn.x86_64.feature on
Win7_64, I was still able to install com.jboss.jbds.mylyn.x86.feature because the
jbdevstudio win32 installer runs in 32-bit mode, and therefore the arch == x86:
{code}eclipse.commands=-os
win32
-ws
win32
-arch
x86
{code}
So, I need some other way to have JBDS know that it's running on Vista or 7 64-bit
despite the fact that the application (jbdevstudio.exe) is running in 32-bit mode.
http://www.grimadmin.com/article.php/batchfile-easy-way-to-detect-os-version
Or maybe look at patching SWT?
https://bugs.eclipse.org/bugs/show_bug.cgi?id=333630#c5
https://bugs.eclipse.org/bugs/attachment.cgi?id=193993&action=diff
http://git.eclipse.org/c/platform/eclipse.platform.swt.git/tree/bundles/o...
JBoss Dev Studio 4.0 crash
--------------------------
Key: JBDS-1648
URL:
https://issues.jboss.org/browse/JBDS-1648
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: 3rdPartyCertification, 3rdPartyDependencies, Upstream
Affects Versions: 4.0.0.GA
Environment: Win 7 x64 Pro SP1
Reporter: Matt V
Assignee: Max Rydahl Andersen
Fix For: 4.1.1.GA
Attachments: hs_err_pid2468.log, hs_err_pid4368.log,
JBDS-1648.install.notes.JBDS411.txt, JBDS-1648.install.notes.JBDS5M4.txt,
jbds411-installed-win64-jdk6-32-snapshot.png
I had installed the 4.0GA version of Jboss Dev Studio, created a sample project. Later I
restarted the Studio after attempting to install a few plugins (I believe Subclipse).
Every time afterwards, it would launch the studio , the UI would launch with code
windows, and then the studio would crash to desktop in less than a second afterwards.
I do have dump eclipse files that can be attached to this issues.
Note: I am able to open the same workspace without any issues using the STS eclipse IDE.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira