March 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3745) Installer (Setup-bundled-0.0.2-20160330-20) fials - after login, blank screen is displayed, no install.log is written

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3745?page=com.atlassian.jira.plugin.... ] CDW Engine reassigned JBDS-3745: -------------------------------- > Installer (Setup-bundled-0.0.2-20160330-20) fials - after login, blank screen is displayed, no install.log is written > --------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3745 > URL: https://issues.jboss.org/browse/JBDS-3745 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Environment: Windows 10 > Reporter: Len DiMaggio > Assignee: Denis Golovin > Priority: Blocker > Attachments: Setup-bundled-0.0.2-20160330-20.png > > > See attached screenshot - this is with the Setup-bundled-0.0.2-20160330-20 installer - no install.log file is written. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3745) Installer (Setup-bundled-0.0.2-20160330-20) fials - after login, blank screen is displayed, no install.log is written

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3745?page=com.atlassian.jira.plugin.... ] Len DiMaggio updated JBDS-3745: ------------------------------- Attachment: Setup-bundled-0.0.2-20160330-20.png > Installer (Setup-bundled-0.0.2-20160330-20) fials - after login, blank screen is displayed, no install.log is written > --------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3745 > URL: https://issues.jboss.org/browse/JBDS-3745 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Environment: Windows 10 > Reporter: Len DiMaggio > Assignee: Denis Golovin > Priority: Blocker > Attachments: Setup-bundled-0.0.2-20160330-20.png > > > See attached screenshot - this is with the Setup-bundled-0.0.2-20160330-20 installer - no install.log file is written. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21984) Wrong Source Path when creating OS3 Server Adapter for multiple applications

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21984?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-21984: ------------------------------------------ The patch takes the following approach: # If you start the wizard from explorer: ## the service that is selected is used, the workspace project is inferred from it by comparing the git uri in the buildConfig (of the selected service) with the git remotes of the workspace projects # if you start the wizard from "Servers" view or "New wizards"/main menu: ## the workspace project that's selected will be used, the service is inferred from it by comparing the git uri in the buildConfigs of the available services with the git remote of the (selected) workspace project > Wrong Source Path when creating OS3 Server Adapter for multiple applications > ---------------------------------------------------------------------------- > > Key: JBIDE-21984 > URL: https://issues.jboss.org/browse/JBIDE-21984 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Alexey Kazakov > Assignee: Andre Dietisheim > Priority: Blocker > Labels: openshift_v3, server_adapter_wizard > Fix For: 4.3.1.CR1 > > Attachments: launch_config.png, Screenshot 2016-03-31 14.34.47.png, server-adapter.png > > > 1. > !server-adapter.png|thumbnail! > 2. Even selecting the correct source manually doesn't help. The eclipse project is still incorrect in the launch config. > !launch_config.png|thumbnail! > Maybe it's because the nodejs eclipse project is not a wtp project and the server adapter picks up the only available wtp module - eap-app. > The only way to create a proper server adapter for the nodejs-example is to delete the eap eclipse project from the workspace. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3745) Installer (Setup-bundled-0.0.2-20160330-20) fials - after login, blank screen is displayed, no install.log is written

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3745?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3745: ----------------------------- > Installer (Setup-bundled-0.0.2-20160330-20) fials - after login, blank screen is displayed, no install.log is written > --------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3745 > URL: https://issues.jboss.org/browse/JBDS-3745 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Environment: Windows 10 > Reporter: Len DiMaggio > Assignee: Denis Golovin > Priority: Blocker > Attachments: Setup-bundled-0.0.2-20160330-20.png > > > See attached screenshot - this is with the Setup-bundled-0.0.2-20160330-20 installer - no install.log file is written. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3745) Installer (Setup-bundled-0.0.2-20160330-20) fials - after login, blank screen is displayed, no install.log is written

by Len DiMaggio (JIRA)

Len DiMaggio created JBDS-3745: ---------------------------------- Summary: Installer (Setup-bundled-0.0.2-20160330-20) fials - after login, blank screen is displayed, no install.log is written Key: JBDS-3745 URL: https://issues.jboss.org/browse/JBDS-3745 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: installer Affects Versions: 9.1.0.CR1 Environment: Windows 10 Reporter: Len DiMaggio Assignee: Denis Golovin Priority: Blocker See attached screenshot - this is with the Setup-bundled-0.0.2-20160330-20 installer - no install.log file is written. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21984) Wrong Source Path when creating OS3 Server Adapter for multiple applications

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21984?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-21984: ------------------------------------------ [~xcoulon] thx for testing! > Wrong Source Path when creating OS3 Server Adapter for multiple applications > ---------------------------------------------------------------------------- > > Key: JBIDE-21984 > URL: https://issues.jboss.org/browse/JBIDE-21984 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Alexey Kazakov > Assignee: Andre Dietisheim > Priority: Blocker > Labels: openshift_v3, server_adapter_wizard > Fix For: 4.3.1.CR1 > > Attachments: launch_config.png, Screenshot 2016-03-31 14.34.47.png, server-adapter.png > > > 1. > !server-adapter.png|thumbnail! > 2. Even selecting the correct source manually doesn't help. The eclipse project is still incorrect in the launch config. > !launch_config.png|thumbnail! > Maybe it's because the nodejs eclipse project is not a wtp project and the server adapter picks up the only available wtp module - eap-app. > The only way to create a proper server adapter for the nodejs-example is to delete the eap eclipse project from the workspace. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3602) Error Reporting doesnt work since we do not set eclipse.buildid

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBDS-3602?page=com.atlassian.jira.plugin.... ] Rastislav Wagner closed JBDS-3602. ---------------------------------- verified in JBDS 9.1.0.CR1-v20160326-0059-B443 > Error Reporting doesnt work since we do not set eclipse.buildid > --------------------------------------------------------------- > > Key: JBDS-3602 > URL: https://issues.jboss.org/browse/JBDS-3602 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: aeri > Affects Versions: 9.1.0.CR1 > Environment: JBDS 9.1.0.CR1-v20160222-0232-B335 > JBT Nightly (2016-02-22) > both contains the same version of aeri plugins > Reporter: Rastislav Wagner > Assignee: Denis Golovin > Priority: Blocker > Fix For: 9.1.0.CR1 > > > So I tied to evoke error reporting dialog with the following scenario: > 1. import Java EE Web Project from central > 2. right click in Project Explorer -> refactor -> rename > 3. change name, hit OK which will result in errors from org.hibernate stuff > In case of JBDS no error reporting dialog is shown, works in JBT > I also tried org.eclipse stuff: > 1. open Properties view > 2. create JPA Project (File -> New -> Other... JPA Project) > 3. open persistence.xml which will result in NPE from org.eclipse stuff > And again in no error reporting dialog in case of JBDS but works in JBT -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22042) Cannot install JBT: Missing requirement: Smart Import support for THyM 0.0.1.201509301541

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22042?page=com.atlassian.jira.plugi... ] Pavol Srna updated JBIDE-22042: ------------------------------- Steps to Reproduce: 1) Install All from http://download.jboss.org/jbosstools/mars/staging/updates/core/4.3.1.CR1/ > Cannot install JBT: Missing requirement: Smart Import support for THyM 0.0.1.201509301541 > ------------------------------------------------------------------------------------------ > > Key: JBIDE-22042 > URL: https://issues.jboss.org/browse/JBIDE-22042 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: updatesite > Affects Versions: 4.3.1.CR1 > Reporter: Pavol Srna > Assignee: Nick Boldt > Priority: Blocker > Labels: respin-a > Fix For: 4.3.1.CR1 > > Attachments: Screen Shot 2016-03-31 at 13.26.03.png > > > {code} > Cannot complete the install because one or more required items could not be found. > Software being installed: JBoss Easymport for Aerogear 1.3.1.CR1-v20160203-2301-B70 (org.jboss.tools.aerogear.easymport.feature.feature.group 1.3.1.CR1-v20160203-2301-B70) > Missing requirement: Smart Import support for THyM 0.0.1.201509301541 (org.eclipse.thym.ui.importer 0.0.1.201509301541) requires 'bundle org.eclipse.e4.ui.importer 0.0.0' but it could not be found > Cannot satisfy dependency: > From: JBoss Easymport for Aerogear 1.3.1.CR1-v20160203-2301-B70 (org.jboss.tools.aerogear.easymport.feature.feature.group 1.3.1.CR1-v20160203-2301-B70) > To: org.eclipse.thym.ui.importer [0.0.1.201509301541] > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22041) Exception is thrown when I do not want to open cheatsheet

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22041?page=com.atlassian.jira.plugi... ] Rastislav Wagner updated JBIDE-22041: ------------------------------------- Summary: Exception is thrown when I do not want to open cheatsheet (was: Exception is thrown when dont want to open cheatsheet) > Exception is thrown when I do not want to open cheatsheet > --------------------------------------------------------- > > Key: JBIDE-22041 > URL: https://issues.jboss.org/browse/JBIDE-22041 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.3.1.CR1 > Reporter: Rastislav Wagner > > {code} > org.eclipse.swt.SWTException: Failed to execute runnable (org.eclipse.core.runtime.OperationCanceledException) > at org.eclipse.swt.SWT.error(SWT.java:4491) > at org.eclipse.swt.SWT.error(SWT.java:4406) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3794) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3433) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:694) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:606) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139) > 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:380) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235) > 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:497) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608) > at org.eclipse.equinox.launcher.Main.run(Main.java:1515) > at org.eclipse.equinox.launcher.Main.main(Main.java:1488) > Caused by: org.eclipse.core.runtime.OperationCanceledException > at org.jboss.tools.project.examples.cheatsheet.internal.util.CheatSheetUtil.promptToShowCheatsheets(CheatSheetUtil.java:434) > at org.jboss.tools.project.examples.cheatsheet.internal.util.CheatSheetUtil.access$1(CheatSheetUtil.java:394) > at org.jboss.tools.project.examples.cheatsheet.internal.util.CheatSheetUtil$1.run(CheatSheetUtil.java:378) > at org.eclipse.ui.internal.UILockListener.doPendingWork(UILockListener.java:162) > at org.eclipse.ui.internal.UISynchronizer$3.run(UISynchronizer.java:154) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) > ... 24 more > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22044) JBT 4.3.1.CR1 build has old aerogear bits

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22044?page=com.atlassian.jira.plugi... ] Pavol Srna reassigned JBIDE-22044: ---------------------------------- Assignee: Nick Boldt > JBT 4.3.1.CR1 build has old aerogear bits > ------------------------------------------ > > Key: JBIDE-22044 > URL: https://issues.jboss.org/browse/JBIDE-22044 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.1.CR1 > Reporter: Pavol Srna > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.3.1.CR1 > > > Looking at the JBT updatesite [1] aerogear.thym has been built on v20160203-2301-B70. > But there are newer commits in 4.3.x branch. It seems we aggregated old bits. > [1] http://download.jboss.org/jbosstools/mars/staging/updates/core/4.3.1.CR1/ -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 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 March 2016