[
https://jira.jboss.org/jira/browse/JBDS-1073?page=com.atlassian.jira.plug...
]
Nick Boldt commented on JBDS-1073:
----------------------------------
Having built JBDS locally and installed it from the generated
jbdevstudio-eap-linux-gtk-3.0.0.v201001211255N-CR2.jar, I get this:
$ java -jar jbdevstudio-eap-linux-gtk-3.0.0.v201001211255N-CR2.jar
PackageListener, install.log=/tmp/jbdevstudio-install-5761952458125695795.log
Jan 21, 2010 3:49:20 PM com.sun.corba.se.impl.ior.IORImpl getProfile
WARNING: "IOP00511201: (INV_OBJREF) IOR must have at least one IIOP profile"
org.omg.CORBA.INV_OBJREF: vmcid: SUN minor code: 1201 completed: No
at
com.sun.corba.se.impl.logging.IORSystemException.iorMustHaveIiopProfile(IORSystemException.java:473)
at
com.sun.corba.se.impl.logging.IORSystemException.iorMustHaveIiopProfile(IORSystemException.java:495)
at com.sun.corba.se.impl.ior.IORImpl.getProfile(IORImpl.java:334)
at
com.sun.corba.se.impl.encoding.CDRInputStream_1_0.read_Object(CDRInputStream_1_0.java:787)
at
com.sun.corba.se.impl.encoding.CDRInputStream_1_0.read_Object(CDRInputStream_1_0.java:761)
at com.sun.corba.se.impl.encoding.CDRInputStream.read_Object(CDRInputStream.java:231)
at
com.sun.corba.se.impl.resolver.INSURLOperationImpl.getIORFromString(INSURLOperationImpl.java:120)
at
com.sun.corba.se.impl.resolver.INSURLOperationImpl.operate(INSURLOperationImpl.java:130)
at com.sun.corba.se.impl.orb.ORBImpl.string_to_object(ORBImpl.java:836)
at org.GNOME.Accessibility.AccessUtil.getRegistryObject(AccessUtil.java:143)
at org.GNOME.Accessibility.JavaBridge.registerApplication(JavaBridge.java:1099)
at org.GNOME.Accessibility.JavaBridge.<init>(JavaBridge.java:364)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:532)
at java.lang.Class.newInstance0(Class.java:372)
at java.lang.Class.newInstance(Class.java:325)
at java.awt.Toolkit.loadAssistiveTechnologies(Toolkit.java:786)
at java.awt.Toolkit.getDefaultToolkit(Toolkit.java:875)
at com.jgoodies.looks.LookUtils.isLowResolution(LookUtils.java:480)
at com.jgoodies.looks.LookUtils.<clinit>(LookUtils.java:249)
at
com.jgoodies.looks.plastic.PlasticLookAndFeel.<clinit>(PlasticLookAndFeel.java:135)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:264)
at javax.swing.SwingUtilities.loadSystemClass(SwingUtilities.java:1869)
at javax.swing.UIManager.setLookAndFeel(UIManager.java:571)
at com.izforge.izpack.installer.GUIInstaller.loadLookAndFeel(GUIInstaller.java:422)
at com.izforge.izpack.installer.GUIInstaller.<init>(GUIInstaller.java:116)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:532)
at java.lang.Class.newInstance0(Class.java:372)
at java.lang.Class.newInstance(Class.java:325)
at com.izforge.izpack.installer.Installer.main(Installer.java:62)
calltarget:
main:
[echo] Run p2 metadata generator
[p2] Generating metadata for
/home/nboldt/jbdevstudio-3.0.0.v201001211255N-CR2/eclipse.
[p2] Generation completed with success [0 seconds].
[delete] Deleting: /tmp/artifacts.xml
[delete] Deleting: /tmp/content.xml
creating Logfile: 'IzPack_Logfile_at_1264106958259.txt' in: '/tmp'
This installation contains:
org.springframework.ide.eclipse.feature_2.3.0.200912170948-RELEASE
(and all the other features/plugins)
However, on running JBDS against an existing workspace (oops) then switching to a new,
empty workspace, I attempted to do:
New > Project > Spring > Spring Project > Next > Project name:
"foospring" > Finish
But all three times I tried it, JBDS simply crashed with nothing in the .log except a note
about key binding conflicts around CTRL+SHIFT+M
(org.jboss.ide.eclipse.as.wtp.ui.fullPublishCommand vs.
org.jboss.tools.jmx.ui.navigate.open.mbean).
Oh, and I also hit the GTK bug documented here, forcing me to use the keyboard to work
through the wizard:
http://wiki.eclipse.org/IRC_FAQ#Eclipse_buttons_in_dialogs_and_other_plac...
Switch from SpringIDE 2.2 to 2.3 in JBDS
-----------------------------------------
Key: JBDS-1073
URL:
https://jira.jboss.org/jira/browse/JBDS-1073
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: Build
Affects Versions: 3.0.0.CR1
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 3.0.0.CR2
The new spring ide runnable zip is here:
http://repository.jboss.com/eclipse/spring-ide/spring-ide-2.3.0.200912170...
To run a local build, change o.j.i.e.releng/requirements/springide/build.properties to
include the following two lines instead:
>
build.uri=http://repository.jboss.com/eclipse/spring-ide/
> build.archive=spring-ide-2.3.0.200912170948.zip
Note that the following plugins/features are excluded from the build:
> exclude.plugins=org.jboss.tools.birt*.jar,\
> org.jboss.tools.eclipse.as.tptp*.jar,\
> org.springframework.ide.eclipse.ajdt*.jar,\
> org.springframework.*source*/**,\
> org.springframework.ide.eclipse.*.mylyn*.jar,\
> org.springframework.ide.eclipse.mylyn*.jar,\
> org.springframework.security*.jar,\
> org.springframework.ide.eclipse.security*.jar
> exclude.features=org.jboss.tools.birt.feature*/**,\
> org.jboss.tools.tptp.feature*/**,\
> org.springframework.ide.eclipse.ajdt.feature*/**,\
> org.springframework.*feature.source*/**,\
> org.springframework.ide.eclipse.mylyn.feature*/**,\
> org.springframework.ide.eclipse.security.feature*/**
(This is set in /devstudio/trunk/devstudio-installer/build.properties.)
I've just started a local build, but anyone who wants to spin it themselves can do so
to with the above patch/change. If a simple "does it install? does it run? are any
weird errors thrown in console?" test passes, I'll commit this to trunk.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira