June 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-14792) Marketplace install button tooltips all say Juno, not the actual required Eclipse version

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-14792: ---------------------------------- Summary: Marketplace install button tooltips all say Juno, not the actual required Eclipse version Key: JBIDE-14792 URL: https://issues.jboss.org/browse/JBIDE-14792 Project: Tools (JBoss Tools) Issue Type: Bug Components: marketplace, upstream Affects Versions: 4.1.0.Beta1 Reporter: Rastislav Wagner Assignee: Nick Boldt Fix For: 4.1.0.Beta1 Install button description is wrong also for JBDS7 -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14787) Marketplace description says that 4.1.0 is targeting Juno

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14787?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-14787: ------------------------------- Comment: was deleted (was: Link? Screenshot? Geez.) > Marketplace description says that 4.1.0 is targeting Juno > --------------------------------------------------------- > > Key: JBIDE-14787 > URL: https://issues.jboss.org/browse/JBIDE-14787 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: marketplace, upstream > Affects Versions: 4.1.0.Beta1 > Reporter: Rastislav Wagner > Assignee: Nick Boldt > Fix For: 4.1.0.Beta1 > > > Install button description is wrong also for JBDS7 -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14787) Marketplace description says that 4.1.0 is targeting Juno

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14787?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-14787: ------------------------------- Component/s: upstream > Marketplace description says that 4.1.0 is targeting Juno > --------------------------------------------------------- > > Key: JBIDE-14787 > URL: https://issues.jboss.org/browse/JBIDE-14787 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: marketplace, upstream > Affects Versions: 4.1.0.Beta1 > Reporter: Rastislav Wagner > Assignee: Nick Boldt > Fix For: 4.1.0.Beta1 > > > Install button description is wrong also for JBDS7 -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14787) Marketplace description says that 4.1.0 is targeting Juno

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14787?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-14787: ------------------------------------ Install button (tooltip) issue is upstream. Reported here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=410196 > Marketplace description says that 4.1.0 is targeting Juno > --------------------------------------------------------- > > Key: JBIDE-14787 > URL: https://issues.jboss.org/browse/JBIDE-14787 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: marketplace, upstream > Affects Versions: 4.1.0.Beta1 > Reporter: Rastislav Wagner > Assignee: Nick Boldt > Fix For: 4.1.0.Beta1 > > > Install button description is wrong also for JBDS7 -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14787) Marketplace description says that 4.1.0 is targeting Juno

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14787?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-14787: ------------------------------------ Link? Screenshot? Geez. > Marketplace description says that 4.1.0 is targeting Juno > --------------------------------------------------------- > > Key: JBIDE-14787 > URL: https://issues.jboss.org/browse/JBIDE-14787 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: marketplace > Affects Versions: 4.1.0.Beta1 > Reporter: Rastislav Wagner > Assignee: Nick Boldt > Fix For: 4.1.0.Beta1 > > > Install button description is wrong also for JBDS7 -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14787) Marketplace description says that 4.1.0 is targeting Juno

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14787?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-14787: ------------------------------------ Description fixed here: http://marketplace.eclipse.org/content/jboss-tools-kepler :: s/Juno/Kepler/g > Marketplace description says that 4.1.0 is targeting Juno > --------------------------------------------------------- > > Key: JBIDE-14787 > URL: https://issues.jboss.org/browse/JBIDE-14787 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: marketplace > Affects Versions: 4.1.0.Beta1 > Reporter: Rastislav Wagner > Assignee: Nick Boldt > Fix For: 4.1.0.Beta1 > > > Install button description is wrong also for JBDS7 -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2389) cannot uninstall JBDS Product Feature - eclipse left in unusable state due to missing eclipse.ini directives

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2389?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-2389: ---------------------------------- I have tried the following, with no success. 1. adding a com.jboss.jbds.product/p2.inf file: {code} instructions.uninstall= \ org.eclipse.equinox.p2.touchpoint.eclipse.removeProgramArg(programArg:-product); \ org.eclipse.equinox.p2.touchpoint.eclipse.removeProgramArg(programArg:com.jboss.jbds.product.product); \ org.eclipse.equinox.p2.touchpoint.eclipse.removeProgramArg(programArg:-showsplash); \ org.eclipse.equinox.p2.touchpoint.eclipse.removeProgramArg(programArg:platform${#58}/base/plugins/com.jboss.jbds.product); \ org.eclipse.equinox.p2.touchpoint.eclipse.addProgramArg(programArg:-application); \ org.eclipse.equinox.p2.touchpoint.eclipse.addProgramArg(programArg:org.eclipse.ui.ide.workbench); \ org.eclipse.equinox.p2.touchpoint.eclipse.addProgramArg(programArg:-showsplash); \ org.eclipse.equinox.p2.touchpoint.eclipse.addProgramArg(programArg:org.eclipse.platform); {code} Will continue to try other options, eg., using site/com.jboss.jbds.p2.inf instead or in addition. > cannot uninstall JBDS Product Feature - eclipse left in unusable state due to missing eclipse.ini directives > ------------------------------------------------------------------------------------------------------------ > > Key: JBDS-2389 > URL: https://issues.jboss.org/browse/JBDS-2389 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: installer, updatesite > Affects Versions: 6.0.0.CR1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 7.0.0.Beta2 > > > Steps to repro: > Unpack bare Juno JEE. > Install JBDS BYOE feature ("Core Features"). Restart > Install JBDS Branded Product Feature. Restart. > Uninstall JBDS Branded Product Feature (or revert configuration to previous). Restart. Eclipse is now broken: > {code} > java.lang.RuntimeException: Application "" could not be found in the registry. > {code} > Addtional info: > {quote} > Bare Juno JEE eclipse.ini: > {code} > $➔ cat eclipse/eclipse.ini > -startup > plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar > --launcher.library > plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.200.v20120522-1813 > -product > org.eclipse.epp.package.jee.product > --launcher.defaultAction > openFile > -showsplash > org.eclipse.platform > --launcher.XXMaxPermSize > 256m > --launcher.defaultAction > openFile > -vmargs > -Dosgi.requiredJavaVersion=1.5 > -Dhelp.lucene.tokenizer=standard > -XX:MaxPermSize=256m > -Xms40m > -Xmx512m > {code} > or, for Eclipse Platform Binary: > {code} > -startup > plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar > --launcher.library > plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.200.v20120522-1813 > -showsplash > org.eclipse.platform > --launcher.XXMaxPermSize > 256m > --launcher.defaultAction > openFile > -vmargs > -Xms40m > -Xmx384m > {code} > After installing JBDS BYOE: > {code} > $➔ cat eclipse/eclipse.ini > -startup > plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar > --launcher.library > plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.200.v20120522-1813 > -showsplash > org.eclipse.platform > --launcher.XXMaxPermSize > 256m > --launcher.defaultAction > openFile > -vmargs > -Xms512m > -Xmx1024m > -Djboss.discovery.directory.url=https://devstudio.jboss.com/updates/6.0-staging/devstudio-directory.xml > {code} > After installing JBDS branded product, eclipse.ini becomes jbdevstudio.ini: > {code} > $➔ cat eclipse/jbdevstudio.ini > -startup > plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar > --launcher.library > plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.200.v20120522-1813 > --launcher.XXMaxPermSize > 256m > --launcher.defaultAction > openFile > -product > com.jboss.jbds.product.product > -showsplash > platform:/base/plugins/com.jboss.jbds.product > --launcher.XXMaxPermSize > 256m > --launcher.defaultAction > openFile > -vmargs > -Djboss.discovery.directory.url=https://devstudio.jboss.com/updates/6.0-staging/devstudio-directory.xml > -Xms512m > -Xmx1024m > -Dosgi.instance.area.default=(a)user.home/workspace > {code} > After UNINSTALLING JBDS branded product (to drop back to Eclipse + JBDS BYOE), can no longer start Eclipse. Here is the resulting eclipse.ini file: > {code} > $➔ cat eclipse/eclipse.ini > -startup > plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar > --launcher.library > plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.200.v20120522-1813 > -product > com.jboss.jbds.product.product > -showsplash > platform:/base/plugins/com.jboss.jbds.product > --launcher.XXMaxPermSize > 256m > --launcher.defaultAction > openFile > -vmargs > -Djboss.discovery.directory.url=https://devstudio.jboss.com/updates/6.0-staging/devstudio-directory.xml > -Xms512m > -Xmx1024m > {code} > {quote} > So, I think we need an instructions.unconfigure in com.jboss.jbds.p2.inf to remove these lines > {code} > -product > com.jboss.jbds.product.product > -showsplash > platform:/base/plugins/com.jboss.jbds.product > {code} > and replace them with the following when JBDS is uninstalled: > {code} > -application > org.eclipse.ui.ide.workbench > -showsplash > org.eclipse.platform > {code} > Also need to know what happens if there are two -product directives... can we just > add (and later remove, when uninstalling) our product to the list, or must we replace > any existing -product entries with ours? -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14537) BrowserSim 4.1.0.Beta1 - JUnit failure WebKitTests.testWebKitSetDefaultUserAgent

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14537?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-14537: ------------------------------------ >From Eng Ops: {quote}Packages installed on internal machines used for testing need to come from verified internal resources. It looks like webkitgtk.x86_64 is available on RHEL6 machines, at least, from internal repositories linked to RHN. Does this package have what you need?{quote} > BrowserSim 4.1.0.Beta1 - JUnit failure WebKitTests.testWebKitSetDefaultUserAgent > -------------------------------------------------------------------------------- > > Key: JBIDE-14537 > URL: https://issues.jboss.org/browse/JBIDE-14537 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Affects Versions: 4.1.0.Beta1 > Reporter: Yahor Radtsevich > Assignee: Nick Boldt > Fix For: 4.1.0.Beta2 > > > https://hudson.jboss.org/hudson/view/JBossTools/view/JBossTools_4.1.keple... > org.jboss.tools.vpe.browsersim.browser.test.WebKitTests.testWebKitSetDefaultUserAgent > {code} > org.eclipse.swt.SWTError: No more handles > at org.eclipse.swt.SWT.error(SWT.java:4418) > at org.eclipse.swt.SWT.error(SWT.java:4307) > at org.eclipse.swt.SWT.error(SWT.java:4278) > at org.eclipse.swt.browser.Browser.<init>(Browser.java:103) > at org.jboss.tools.vpe.browsersim.browser.BrowserSimBrowser.<init>(BrowserSimBrowser.java:9) > at org.jboss.tools.vpe.browsersim.browser.AbstractWebKitBrowser.<init>(AbstractWebKitBrowser.java:24) > at org.jboss.tools.vpe.browsersim.browser.internal.WebKitBrowser_gtk_linux_x86_64.<init>(WebKitBrowser_gtk_linux_x86_64.java:38) > at org.jboss.tools.vpe.browsersim.browser.WebKitBrowserFactory.createBrowser(WebKitBrowserFactory.java:36) > at org.jboss.tools.vpe.browsersim.browser.test.WebKitTests.testWebKitSetDefaultUserAgent(WebKitTests.java:39) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at junit.framework.TestCase.runTest(TestCase.java:176) > at junit.framework.TestCase.runBare(TestCase.java:141) > at junit.framework.TestResult$1.protect(TestResult.java:122) > at junit.framework.TestResult.runProtected(TestResult.java:142) > at junit.framework.TestResult.run(TestResult.java:125) > at junit.framework.TestCase.run(TestCase.java:129) > at junit.framework.TestSuite.runTest(TestSuite.java:255) > at junit.framework.TestSuite.run(TestSuite.java:250) > at junit.framework.TestSuite.runTest(TestSuite.java:255) > at junit.framework.TestSuite.run(TestSuite.java:250) > at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84) > at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:123) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:104) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:164) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110) > at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:175) > at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:123) > at org.eclipse.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:85) > at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication$1.run(AbstractUITestApplication.java:35) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3692) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3341) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1108) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:992) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:137) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:600) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:555) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124) > at org.eclipse.tycho.surefire.osgibooter.UITestApplication.runApplication(UITestApplication.java:31) > at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication.run(AbstractUITestApplication.java:114) > at org.eclipse.tycho.surefire.osgibooter.UITestApplication.start(UITestApplication.java:37) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591) > at org.eclipse.equinox.launcher.Main.run(Main.java:1450) > at org.eclipse.equinox.launcher.Main.main(Main.java:1426) > {code} -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14370) Add 32bit swt libraries to eclipse64 module as a result of the build

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14370?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-14370: ----------------------------------- Suggested implementation: https://github.com/mickaelistria/jbosstools-vpe/commit/ee5088d4c82a0f0e98... (on branch "JBIDE-14370") > Add 32bit swt libraries to eclipse64 module as a result of the build > -------------------------------------------------------------------- > > Key: JBIDE-14370 > URL: https://issues.jboss.org/browse/JBIDE-14370 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: browsersim > Reporter: Konstantin Marmalyukov > Assignee: Mickael Istria > Priority: Critical > Fix For: 4.1.0.Beta2 > > > We need to have latest 32-bit SWT libraries in resources folder of eclipse64 browsersim module to make user able to run browserSim from x64 eclipse. -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13987) Improve project wizards in JBoss Central : Proxy Wizards

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13987?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-13987: ------------------------------------- Are you trying JBDS or JBT? > Improve project wizards in JBoss Central : Proxy Wizards > -------------------------------------------------------- > > Key: JBIDE-13987 > URL: https://issues.jboss.org/browse/JBIDE-13987 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Affects Versions: 4.1.0.Alpha1 > Reporter: Fred Bricon > Assignee: Max Rydahl Andersen > Labels: new_and_noteworthy, respin-b > Fix For: 4.1.0.Beta1 > > Attachments: www.tar.gz > > > The "Start from scratch" section (formerly known as Project section) in JBoss Central needs to support the following requirements : > - wizard list (label/order/description) must be updateable remotely > - show wizards (including the proper icon) even if their contributing plugins are missing > - when clicking on the wizard link in JBoss Central, if the wizard is available then open it, else, install the required plugins > The general idea here is to use some kind of proxy wizard. A proxy wizard model should have the following attributes : > - id : the proxy wizard id > - label : the proxy wizard label shown in JBoss Central > - wizardId : the real wizard id used by Central to open the wizard dialog > - iconPath : the path to the wizard icon (independent of required connector) > - description : the description shown in Central when hovering over the wizard link > - requiredConnectorIds : the connector ids to install if the real wizard is not available > - priority : order in which the wizard is displayed in JBoss Central > The proxy wizards will be declared in the jboss-discovery.jar plugin.xml (to minimize build / maintenance overhead). The jar will also include the required icons. > The jar will be fetched remotely by the discovery mechanism but a cached version must be kept for offline usage. -- 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

12 years, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues June 2013