January 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20331) install grinder fails if blocked by Firefox

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20331?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-20331: ------------------------------- Attachment: build-history3.png > install grinder fails if blocked by Firefox > ------------------------------------------- > > Key: JBIDE-20331 > URL: https://issues.jboss.org/browse/JBIDE-20331 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Beta2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.x, 4.4.0.Alpha1 > > Attachments: build-history.png, build-history2.png, build-history3.png, ff-profile-manager.png, install-grinder-bad-firefox.jpeg, install-grinder-fail.txt, install-grinder-firefox-problem-testInstall(org.jboss.tools.tests.installation.InstallTest).jpeg, new-firefox-block-UI_dev112.png, new-firefox-block-UI_dev59.png, virt1-ftl.png, virt2-ftl.png > > > {code:title=http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-grinder.install-tests.matrix_master/PROJECT=jbosstools,eclipseBundleVersion=mars.R,jdk=jdk1.8,label_exp=%28RHEL6||RHEL7||beaker||jboss-prod%29&&%28x86||x86_64%29/3157/consoleFull} > 08:02:18 java.lang.RuntimeException: Unable to aquire PluginConverter service during generation for: /mnt/hudson_workspace/workspace/jbosstools-install-grinder.install-tests.matrix_master/d6768101/eclipse/plugins/org.eclipse.oomph.base_1.1.0.v20150609-0914.jar{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21404) versionwatch thinks that that 1.1.0 < 1.0.2000

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21404?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-21404: ---------------------------------- Assignee: Nick Boldt > versionwatch thinks that that 1.1.0 < 1.0.2000 > ---------------------------------------------- > > Key: JBIDE-21404 > URL: https://issues.jboss.org/browse/JBIDE-21404 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: versionwatch > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha1 > > > Appears to be a bug in versionwatch such that it thinks that 1.1.0 < 1.0.2000. > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... > {quote} > ERROR: Version 1.1.0.v20151130-0157 must be higher than 1.0.2000.v20150810-1719 > {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21391) upstream IU version decreases

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21391?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-21391: ------------------------------------ For the platform IUs: https://bugs.eclipse.org/bugs/show_bug.cgi?id=476918#c6 For the ecf plugin, seems there's a bug in versionwatch such that it thinks that 1.1.0 < 1.0.2000: https://issues.jboss.org/browse/JBIDE-21404 > upstream IU version decreases > ----------------------------- > > Key: JBIDE-21391 > URL: https://issues.jboss.org/browse/JBIDE-21391 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, target-platform > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha1 > > > As of Neon M4, three IUs have versions which decreased relative to their Mars.1 versions. > {code} > org.eclipse.equinox.p2.rcp.feature 1.2.101.v20150826-1318 Version must be higher than 1.2.101.v20150826-1318 > org.eclipse.equinox.p2.user.ui 2.2.101.v20150826-1318 Version must be higher than 2.2.101.v20150826-1318 > org.eclipse.ecf.provider.filetransfer.httpclient4 1.0.2000.v20150810-1719 Version must be higher than 1.0.2000.v20150810-1719 > {code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21404) versionwatch thinks that that 1.1.0 < 1.0.2000

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-21404: ---------------------------------- Summary: versionwatch thinks that that 1.1.0 < 1.0.2000 Key: JBIDE-21404 URL: https://issues.jboss.org/browse/JBIDE-21404 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: versionwatch Affects Versions: 4.4.0.Alpha1 Reporter: Nick Boldt Appears to be a bug in versionwatch such that it thinks that 1.1.0 < 1.0.2000. http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... {quote} ERROR: Version 1.1.0.v20151130-0157 must be higher than 1.0.2000.v20150810-1719 {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21365) Beta 4.3.1 N&N for OpenShift should state that while the CDK is treated as a server, runtime detection is not possible

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21365?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-21365. --------------------------------- Verified here: http://tools.jboss.org/documentation/whatsnew/jbosstools/4.3.1.Beta1.html... Except this typo: {quote}It’s also worth nothing that several features will not work with the raw Red Hat CDK{quote} Fixed in github, should appear online shortly. > Beta 4.3.1 N&N for OpenShift should state that while the CDK is treated as a server, runtime detection is not possible > ---------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21365 > URL: https://issues.jboss.org/browse/JBIDE-21365 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Reporter: Len DiMaggio > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.3.1.Beta1 > > > This may be obvious to some/most users, but it may confuse other users - it would be better to make it explicit that runtime detection is not possible for runtime detection to detect the raw CDK. > Since it's a raw cdk it is proper to fail to detect - here's no real way to detect cdk vs any other random vagrantfile. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21255) Core/General New and Noteworthy for 4.3.1.Beta1

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21255?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-21255. --------------------------------- Verified. > Core/General New and Noteworthy for 4.3.1.Beta1 > ----------------------------------------------- > > Key: JBIDE-21255 > URL: https://issues.jboss.org/browse/JBIDE-21255 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: common/jst/core > Reporter: Alexey Kazakov > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.3.1.Beta1 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If Core/General is not listed here check if there are issues that should be added and add them. > Document the ones relevant for Core/General by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pull request. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20734) Show ports, environment variables and links in the UI

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20734?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-20734. --------------------------------- Thanks, Xavier. With WildFly, I can see an item under ports. With OpenShift pods, I can see Volumes. I'm still not sure what Links means as I didn't see any links in any running containers. Closing. > Show ports, environment variables and links in the UI > ----------------------------------------------------- > > Key: JBIDE-20734 > URL: https://issues.jboss.org/browse/JBIDE-20734 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: docker, upstream > Affects Versions: 4.3.0.Final > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Labels: new_and_noteworthy > Fix For: 4.3.1.Beta1 > > Attachments: docker-explorer.png > > > See https://bugs.eclipse.org/bugs/show_bug.cgi?id=471666 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20738) JMX Navigator Refresh Command is running in main UI Thread

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20738?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-20738. --------------------------------- ok, I can't reproduce this, thus closing. > JMX Navigator Refresh Command is running in main UI Thread > ---------------------------------------------------------- > > Key: JBIDE-20738 > URL: https://issues.jboss.org/browse/JBIDE-20738 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx > Affects Versions: 4.3.0.CR1 > Reporter: Denis Golovin > Assignee: Rob Stryker > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > Refresh in JMX Navigator freezes UI because executed in main UI thread: > {code}Thread [main] (Suspended (breakpoint at line 435 in org.jboss.tools.jmx.jvmmonitor.internal.core.ActiveJvm)) > owns: org.jboss.tools.jmx.local.internal.JvmConnectionWrapper (id=162) > org.jboss.tools.jmx.jvmmonitor.internal.core.ActiveJvm.initialize(javax.management.remote.JMXServiceURL) line: 435 > org.jboss.tools.jmx.jvmmonitor.internal.core.ActiveJvm.initialize(java.lang.String, int) line: 465 > org.jboss.tools.jmx.jvmmonitor.internal.core.ActiveJvm.initialize() line: 445 > org.jboss.tools.jmx.jvmmonitor.internal.core.ActiveJvm.connect(int, boolean) line: 233 > org.jboss.tools.jmx.jvmmonitor.internal.core.ActiveJvm.connect(int) line: 213 > org.jboss.tools.jmx.local.internal.JvmConnectionWrapper.connect() line: 121 > org.jboss.tools.jmx.ui.internal.actions.RefreshAction.refreshObjectNode(java.lang.Object) line: 107 > org.jboss.tools.jmx.ui.internal.actions.RefreshAction.run() line: 153 > org.jboss.tools.jmx.ui.internal.actions.RefreshAction(org.eclipse.jface.action.Action).runWithEvent(org.eclipse.swt.widgets.Event) line: 473 > org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(org.eclipse.swt.widgets.Event, boolean) line: 595 > org.eclipse.jface.action.ActionContributionItem.access$2(org.eclipse.jface.action.ActionContributionItem, org.eclipse.swt.widgets.Event, boolean) line: 511 > org.eclipse.jface.action.ActionContributionItem$5.handleEvent(org.eclipse.swt.widgets.Event) line: 420 > org.eclipse.swt.widgets.EventTable.sendEvent(org.eclipse.swt.widgets.Event) line: 84 > org.eclipse.swt.widgets.Display.sendEvent(org.eclipse.swt.widgets.EventTable, org.eclipse.swt.widgets.Event) line: 4481 > org.eclipse.swt.widgets.MenuItem(org.eclipse.swt.widgets.Widget).sendEvent(org.eclipse.swt.widgets.Event) line: 1327 > org.eclipse.swt.widgets.Display.runDeferredEvents() line: 3819 > org.eclipse.swt.widgets.Display.readAndDispatch() line: 3430 > org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run() line: 1127 > org.eclipse.core.databinding.observable.Realm.runWithDefault(org.eclipse.core.databinding.observable.Realm, java.lang.Runnable) line: 337 > org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(org.eclipse.e4.ui.model.application.MApplicationElement, org.eclipse.e4.core.contexts.IEclipseContext) line: 1018 > org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(org.eclipse.e4.ui.model.application.MApplicationElement) line: 156 > org.eclipse.ui.internal.Workbench$5.run() line: 654 > org.eclipse.core.databinding.observable.Realm.runWithDefault(org.eclipse.core.databinding.observable.Realm, java.lang.Runnable) line: 337 > org.eclipse.ui.internal.Workbench.createAndRunWorkbench(org.eclipse.swt.widgets.Display, org.eclipse.ui.application.WorkbenchAdvisor) line: 598 > org.eclipse.ui.PlatformUI.createAndRunWorkbench(org.eclipse.swt.widgets.Display, org.eclipse.ui.application.WorkbenchAdvisor) line: 150 > org.eclipse.ui.internal.ide.application.IDEApplication.start(org.eclipse.equinox.app.IApplicationContext) line: 139 > org.eclipse.equinox.internal.app.EclipseAppHandle.run(java.lang.Object) line: 196 > org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(java.lang.Object) line: 134 > org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(java.lang.Object) line: 104 > org.eclipse.core.runtime.adaptor.EclipseStarter.run(java.lang.Object) line: 380 > org.eclipse.core.runtime.adaptor.EclipseStarter.run(java.lang.String[], java.lang.Runnable) line: 235 > sun.reflect.NativeMethodAccessorImpl.invoke0(java.lang.reflect.Method, java.lang.Object, java.lang.Object[]) line: not available [native method] > sun.reflect.NativeMethodAccessorImpl.invoke(java.lang.Object, java.lang.Object[]) line: 62 > sun.reflect.DelegatingMethodAccessorImpl.invoke(java.lang.Object, java.lang.Object[]) line: 43 > java.lang.reflect.Method.invoke(java.lang.Object, java.lang.Object...) line: 497 > org.eclipse.equinox.launcher.Main.invokeFramework(java.lang.String[], java.net.URL[]) line: 669 > org.eclipse.equinox.launcher.Main.basicRun(java.lang.String[]) line: 608 > org.eclipse.equinox.launcher.Main.run(java.lang.String[]) line: 1515 > org.eclipse.equinox.launcher.Main.main(java.lang.String[]) line: 1488 > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21376) Application wizard: should allow to create an app from an image (currently only from template)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21376?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21376: ------------------------------------- Description: The application wizard in the Eclipse tooling currently only allows to create application from templates. The web console additionally allows creating from images and git source. One can see the difference when comparing the listing of options in Eclipse vs the listing in the web console (which also includes images): {quote} Running OpenShift using our openshift-vagrant box, I can see different proposals between the web console and the Eclipse tooling when adding an application in a project. For example, {{jboss-eap64-openshift:1.1}} is not proposed in the Eclipse tooling. See attached screenshots. {quote} was: Running OpenShift using our openshift-vagrant box, I can see different proposals between the web console and the Eclipse tooling when adding an application in a project. For example, {{jboss-eap64-openshift:1.1}} is not proposed in the Eclipse tooling. See attached screenshots. > Application wizard: should allow to create an app from an image (currently only from template) > ---------------------------------------------------------------------------------------------- > > Key: JBIDE-21376 > URL: https://issues.jboss.org/browse/JBIDE-21376 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Xavier Coulon > Labels: application_wizard, openshift_v3 > Fix For: 4.4.0.Alpha1 > > Attachments: Screenshot 2015-12-21 16.44.02.png, Screenshot 2015-12-21 16.44.24.png, Screenshot 2015-12-21 18.06.40.png > > > The application wizard in the Eclipse tooling currently only allows to create application from templates. The web console additionally allows creating from images and git source. > One can see the difference when comparing the listing of options in Eclipse vs the listing in the web console (which also includes images): > {quote} > Running OpenShift using our openshift-vagrant box, I can see different proposals between the web console and the Eclipse tooling when adding an application in a project. For example, {{jboss-eap64-openshift:1.1}} is not proposed in the Eclipse tooling. > See attached screenshots. > {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21376) Application wizard: should allow to create an app from an image (currently only from template)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21376?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21376: ------------------------------------- Labels: application_wizard openshift_v3 (was: ) > Application wizard: should allow to create an app from an image (currently only from template) > ---------------------------------------------------------------------------------------------- > > Key: JBIDE-21376 > URL: https://issues.jboss.org/browse/JBIDE-21376 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Xavier Coulon > Labels: application_wizard, openshift_v3 > Fix For: 4.4.0.Alpha1 > > Attachments: Screenshot 2015-12-21 16.44.02.png, Screenshot 2015-12-21 16.44.24.png, Screenshot 2015-12-21 18.06.40.png > > > Running OpenShift using our openshift-vagrant box, I can see different proposals between the web console and the Eclipse tooling when adding an application in a project. For example, {{jboss-eap64-openshift:1.1}} is not proposed in the Eclipse tooling. > See attached screenshots. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 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 January 2016