February 2017 - jbosstools-issues

[JBoss JIRA] (JBDS-4260) CDK versions differ between platforms (1.3.0)

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-4260?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-4260. ----------------------------- > CDK versions differ between platforms (1.3.0) > --------------------------------------------- > > Key: JBDS-4260 > URL: https://issues.jboss.org/browse/JBDS-4260 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.3.0.AM2 > Reporter: Jan Richter > Assignee: Jan Richter > Fix For: 10.3.0.GA > > > On windows the installer is using CDK 2.4 from 25th January, on mac (and linux) it's still using 2.3 GA. Plus on windows it is still labeled as 2.3 GA. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-4261) Create branding/design for APIs that are being pulled into DCP

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBDS-4261?page=com.atlassian.jira.plugin.... ] Paul Robinson commented on JBDS-4261: ------------------------------------- Please move to DEVELOPER and we'll handle this. I don't have permissions to do that on this project. > Create branding/design for APIs that are being pulled into DCP > -------------------------------------------------------------- > > Key: JBDS-4261 > URL: https://issues.jboss.org/browse/JBDS-4261 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: documentation > Reporter: Heinz Windzio > Fix For: LATER > > > Ryszard has now completed the back end work needed to connect the following docs to the DCP: > https://developers.redhat.com/apidocs/datagrid/7.0.0/ > https://developers.redhat.com/apidocs/datavirt/6.3.0/modeshape/ > https://developers.redhat.com/apidocs/datavirt/6.3.0/teiid/ > https://developers.redhat.com/apidocs/eap/7.0.0/ > You can see that it has the 'legacy' jboss styling at the top. I'm not sure if there is a consistent styling for the APIs that we need to adhere to, but logging this JIRA for someone to look into it and create it if needed. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-4261) Create branding/design for APIs that are being pulled into DCP

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBDS-4261?page=com.atlassian.jira.plugin.... ] Paul Robinson edited comment on JBDS-4261 at 2/13/17 5:28 AM: -------------------------------------------------------------- Please move to DEVELOPER and we'll handle this. I don't have permissions to do that on this project. Maybe [~akazakov] can help? was (Author: paul.robinson): Please move to DEVELOPER and we'll handle this. I don't have permissions to do that on this project. > Create branding/design for APIs that are being pulled into DCP > -------------------------------------------------------------- > > Key: JBDS-4261 > URL: https://issues.jboss.org/browse/JBDS-4261 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: documentation > Reporter: Heinz Windzio > Fix For: LATER > > > Ryszard has now completed the back end work needed to connect the following docs to the DCP: > https://developers.redhat.com/apidocs/datagrid/7.0.0/ > https://developers.redhat.com/apidocs/datavirt/6.3.0/modeshape/ > https://developers.redhat.com/apidocs/datavirt/6.3.0/teiid/ > https://developers.redhat.com/apidocs/eap/7.0.0/ > You can see that it has the 'legacy' jboss styling at the top. I'm not sure if there is a consistent styling for the APIs that we need to adhere to, but logging this JIRA for someone to look into it and create it if needed. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23884) [jolokia] some read requests fail

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23884?page=com.atlassian.jira.plugi... ] Jan Richter closed JBIDE-23884. ------------------------------- Verified in the latest 4.4.3 nightly. > [jolokia] some read requests fail > --------------------------------- > > Key: JBIDE-23884 > URL: https://issues.jboss.org/browse/JBIDE-23884 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, server > Affects Versions: 4.4.3.Final > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.4.3.Final > > Attachments: JBIDE-23884.png > > > Some attribute read requests fail when issued one at a time rather than in a bulk list. > {code} > org.jboss.tools.jmx.core.JMXException: Error executing JMX request. > at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.run(JolokiaConnectionWrapper.java:342) > at org.jboss.tools.jmx.core.MBeanAttributeInfoWrapper.getValue(MBeanAttributeInfoWrapper.java:47) > at org.jboss.tools.jmx.ui.internal.editors.AttributeDetails.update(AttributeDetails.java:216) > at org.jboss.tools.jmx.ui.internal.editors.AttributeDetails.selectionChanged(AttributeDetails.java:184) > at org.eclipse.ui.forms.DetailsPart$1.run(DetailsPart.java:269) > at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) > at org.eclipse.ui.forms.DetailsPart.showPage(DetailsPart.java:255) > at org.eclipse.ui.forms.DetailsPart.update(DetailsPart.java:228) > at org.eclipse.ui.forms.DetailsPart.selectionChanged(DetailsPart.java:213) > at org.eclipse.ui.forms.ManagedForm.fireSelectionChanged(ManagedForm.java:125) > at org.jboss.tools.jmx.ui.internal.editors.AttributesSection$1.selectionChanged(AttributesSection.java:57) > at org.eclipse.jface.viewers.Viewer$1.run(Viewer.java:158) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50) > at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:173) > at org.eclipse.jface.viewers.Viewer.fireSelectionChanged(Viewer.java:155) > at org.eclipse.jface.viewers.StructuredViewer.updateSelection(StructuredViewer.java:2191) > at org.eclipse.jface.viewers.StructuredViewer.handleSelect(StructuredViewer.java:1229) > at org.eclipse.jface.viewers.StructuredViewer$4.widgetSelected(StructuredViewer.java:1258) > at org.eclipse.jface.util.OpenStrategy.fireSelectionEvent(OpenStrategy.java:242) > at org.eclipse.jface.util.OpenStrategy.access$4(OpenStrategy.java:236) > at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:405) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5219) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1340) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4553) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4143) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1121) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1022) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:150) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:687) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:604) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610) > at org.eclipse.equinox.launcher.Main.run(Main.java:1519) > at org.eclipse.equinox.launcher.Main.main(Main.java:1492) > Caused by: java.lang.ClassCastException: org.jolokia.client.request.J4pReadResponse cannot be cast to java.util.List > at org.jboss.tools.jmx.jolokia.internal.connection.JolokiaMBeanServerConnection.getAttributes(JolokiaMBeanServerConnection.java:224) > at org.jboss.tools.jmx.jolokia.internal.connection.JolokiaMBeanServerConnection.getAttribute(JolokiaMBeanServerConnection.java:203) > at org.jboss.tools.jmx.core.MBeanAttributeInfoWrapper$1.run(MBeanAttributeInfoWrapper.java:50) > at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.run(JolokiaConnectionWrapper.java:338) > ... 48 more > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23814) Server Adaptor for JBoss EAP 7 on OpenShift fails with sync error

by Siamak Sadeghianfar (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23814?page=com.atlassian.jira.plugi... ] Siamak Sadeghianfar commented on JBIDE-23814: --------------------------------------------- Looks like it is the same issue as JBIDE-23822. I'll verify and report back. > Server Adaptor for JBoss EAP 7 on OpenShift fails with sync error > ----------------------------------------------------------------- > > Key: JBIDE-23814 > URL: https://issues.jboss.org/browse/JBIDE-23814 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Environment: Red Hat JBoss Developer Studio > Version: 10.2.0.GA > Build id: GA-v20161125-1418-B55 > Build date: 20161125-1418 > JBoss Openshift UI Plugin > Version: 3.3.1.v20161125-0956 > OpenShift > openshift v3.3.1.3 > Reporter: Siamak Sadeghianfar > Assignee: Andre Dietisheim > Priority: Critical > Labels: openshift_v3, server_adapter > Fix For: 4.4.3.Final > > Attachments: jbds-error.png, jboss-eap70-openshift.png > > > When adding a Server Adapter for an JBoss EAP 7 based deployments on OpenShift, operation fails with this error: > {{Could not sync /private/tmp/workspace-demo/.metadata/.plugins/org.jboss.ide.eclipse.as.core/inventory-dev-ssadeghi@inventory/deploy to all pods running the service inventory > OpenShiftBinaryCapability process exited: error: auth info "ssadeghi-redhat.com" does not exist}} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23813) Package Explorer: context menu can cause exception when selected project has svn metadata but erroneously configured/missing SVN provider

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23813?page=com.atlassian.jira.plugi... ] Jan Richter closed JBIDE-23813. ------------------------------- Closing as out of date. > Package Explorer: context menu can cause exception when selected project has svn metadata but erroneously configured/missing SVN provider > ----------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23813 > URL: https://issues.jboss.org/browse/JBIDE-23813 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.AM1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: openshift_v2 > Fix For: 4.4.3.Final > > > created from aeri. The following stack trace is reported: > {code} > Bundle: org.eclipse.team.core 3.7.100.v20150203-1452 > Message: Could not instantiate provider org.tigris.subversion.subclipse.core.svnnature for project pef.client. > Exception: > org.eclipse.team.core.TeamException: Could not instantiate provider org.tigris.subversion.subclipse.core.svnnature for project pef.client. > at org.eclipse.team.core.RepositoryProvider.mapNewProvider(RepositoryProvider.java:165) > at org.eclipse.team.core.RepositoryProvider.mapExistingProvider(RepositoryProvider.java:235) > at org.eclipse.team.core.RepositoryProvider.getProvider(RepositoryProvider.java:507) > at org.jboss.tools.openshift.egit.core.EGitUtils.isShared(EGitUtils.java:132) > at org.jboss.tools.openshift.express.internal.ui.propertytester.ProjectPropertyTester.isIfSharedIsEGit(ProjectPropertyTester.java:48) > at org.jboss.tools.openshift.express.internal.ui.propertytester.ProjectPropertyTester.test(ProjectPropertyTester.java:33) > at org.eclipse.core.internal.expressions.Property.test(Property.java:58) > at org.eclipse.core.internal.expressions.TestExpression.evaluate(TestExpression.java:100) > at org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53) > at org.eclipse.core.internal.expressions.AndExpression.evaluate(AndExpression.java:31) > at org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53) > at org.eclipse.core.internal.expressions.AdaptExpression.evaluate(AdaptExpression.java:106) > at org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53) > at org.eclipse.core.internal.expressions.IterateExpression.evaluate(IterateExpression.java:199) > at org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53) > at org.eclipse.core.internal.expressions.AndExpression.evaluate(AndExpression.java:31) > at org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53) > at org.eclipse.core.internal.expressions.WithExpression.evaluate(WithExpression.java:75) > at org.eclipse.e4.ui.internal.workbench.ContributionsAnalyzer.isVisible(ContributionsAnalyzer.java:256) > at org.eclipse.e4.ui.workbench.renderers.swt.ContributionRecord.computeVisibility(ContributionRecord.java:166) > at org.eclipse.e4.ui.workbench.renderers.swt.ContributionRecord.updateVisibility(ContributionRecord.java:96) > at org.eclipse.e4.ui.workbench.renderers.swt.MenuManagerRendererFilter.updateElementVisibility(MenuManagerRendererFilter.java:188) > at org.eclipse.e4.ui.workbench.renderers.swt.MenuManagerRendererFilter.updateElementVisibility(MenuManagerRendererFilter.java:199) > at org.eclipse.e4.ui.workbench.renderers.swt.MenuManagerShowProcessor.showMenu(MenuManagerShowProcessor.java:230) > at org.eclipse.e4.ui.workbench.renderers.swt.MenuManagerShowProcessor.menuAboutToHide(MenuManagerShowProcessor.java:110) > at org.eclipse.jface.internal.MenuManagerEventHelper.showEventPostHelper(MenuManagerEventHelper.java:92) > at org.eclipse.jface.action.MenuManager.handleAboutToShow(MenuManager.java:467) > at org.eclipse.jface.action.MenuManager.access$1(MenuManager.java:461) > at org.eclipse.jface.action.MenuManager$2.menuShown(MenuManager.java:493) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:255) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23820) Work on Fedora scripts for slaves on CentralCI

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23820?page=com.atlassian.jira.plugi... ] Josef Kopriva commented on JBIDE-23820: --------------------------------------- Created Merge Request for Oliver repo: https://gitlab.mw.lab.eng.bos.redhat.com/jbossqe-jenkins/mwqa-cloud-slave... My branch is also working, but I will rebase it, after [~ogondza] will approve merge request for his repo. > Work on Fedora scripts for slaves on CentralCI > ---------------------------------------------- > > Key: JBIDE-23820 > URL: https://issues.jboss.org/browse/JBIDE-23820 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests > Reporter: Josef Kopriva > Assignee: Josef Kopriva > Fix For: 4.4.3.Final > > > Create and finish scripts for Fedora slaves on CentralCI -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTIS-613) Create a test for FUSETOOLS-1694 (Errors in Editor -> Problems view)

by Dominik Jelinek (JIRA)

[ https://issues.jboss.org/browse/JBTIS-613?page=com.atlassian.jira.plugin.... ] Dominik Jelinek reassigned JBTIS-613: ------------------------------------- Assignee: Dominik Jelinek (was: Tomáš Sedmík) > Create a test for FUSETOOLS-1694 (Errors in Editor -> Problems view) > -------------------------------------------------------------------- > > Key: JBTIS-613 > URL: https://issues.jboss.org/browse/JBTIS-613 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: Fuse IDE, QE > Affects Versions: 4.3.0.Final > Reporter: Tomáš Sedmík > Assignee: Dominik Jelinek > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTIS-1040) Update the logic for checking all available quickstarts in RH Central

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1040?page=com.atlassian.jira.plugin... ] Andrej Podhradsky edited comment on JBTIS-1040 at 2/13/17 3:37 AM: ------------------------------------------------------------------- Hi [~pleacu], my steps are 1. Install Devstudio 10.2.0.GA 2. Add the following vm args to devstudio.ini {code} -Djboss.discovery.directory.url=https://devstudio.redhat.com/10.0/staging/updates/integration-stack/discovery/10.1.0.CR2/devstudio-directory.xml -Djboss.discovery.site.integration-stack.url=https://devstudio.redhat.com/10.0/staging/updates/integration-stack/discovery/10.1.0.CR2/ {code} 3. Start the Devstudio and open Red Hat Central 4. Type 'fuse' into the text field in the middle of the RH Central (nothing is found) 5. Switch to the tab 'Software/Update' 6. Check 'Enable Early Access' 7. Switch back to the tab 'Getting Started' (now you can see the fuse quickstart) The issue here is that the fuse quickstart should be available in the step 4. was (Author: apodhrad): Hi [~pleacu], my steps are 1. Install Devstudio 10.2.0.GA 2. Add the following vm args to devstudio.ini {code} -Djboss.discovery.directory.url=https://devstudio.redhat.com/10.0/staging/updates/integration-stack/discovery/10.1.0.CR2/devstudio-directory.xml -Djboss.discovery.site.integration-stack.url=https://devstudio.redhat.com/10.0/staging/updates/integration-stack/discovery/10.1.0.CR2/ {code} 3. Start the Devstudio and opne Red Hat Central 4. Type 'fuse' into the text field in the middle of the RH Central (nothing is found) 5. Switch to the tab 'Software/Update' 6. Check 'Enable Early Access' 7. Switch back to the tab 'Getting Started' (now you can see the fuse quickstart) > Update the logic for checking all available quickstarts in RH Central > --------------------------------------------------------------------- > > Key: JBTIS-1040 > URL: https://issues.jboss.org/browse/JBTIS-1040 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: distribution > Affects Versions: 10.1.0.CR1 > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Attachments: rh3.png, rhc1.png, rhc2.png > > > There is again a problem with the Fuse quickstart. Currently, the quickstart is available only if we enable Early Access in RH Central. At the first sight it looks like the behavior is hard coded. > Please update the logic for checking all available quickstarts so that it will detect Fuse quickstart without just checking if the Early Access is enabled or not. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTIS-1040) Update the logic for checking all available quickstarts in RH Central

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1040?page=com.atlassian.jira.plugin... ] Andrej Podhradsky commented on JBTIS-1040: ------------------------------------------ Hi [~pleacu], my steps are 1. Install Devstudio 10.2.0.GA 2. Add the following vm args to devstudio.ini {code} -Djboss.discovery.directory.url=https://devstudio.redhat.com/10.0/staging/updates/integration-stack/discovery/10.1.0.CR2/devstudio-directory.xml -Djboss.discovery.site.integration-stack.url=https://devstudio.redhat.com/10.0/staging/updates/integration-stack/discovery/10.1.0.CR2/ {code} 3. Start the Devstudio and opne Red Hat Central 4. Type 'fuse' into the text field in the middle of the RH Central (nothing is found) 5. Switch to the tab 'Software/Update' 6. Check 'Enable Early Access' 7. Switch back to the tab 'Getting Started' (now you can see the fuse quickstart) > Update the logic for checking all available quickstarts in RH Central > --------------------------------------------------------------------- > > Key: JBTIS-1040 > URL: https://issues.jboss.org/browse/JBTIS-1040 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: distribution > Affects Versions: 10.1.0.CR1 > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Attachments: rh3.png, rhc1.png, rhc2.png > > > There is again a problem with the Fuse quickstart. Currently, the quickstart is available only if we enable Early Access in RH Central. At the first sight it looks like the behavior is hard coded. > Please update the logic for checking all available quickstarts so that it will detect Fuse quickstart without just checking if the Early Access is enabled or not. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

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 February 2017