March 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3675) NullPointerException during install (no explanation)

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3675?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-3675: --------------------------------- Priority: Critical (was: Blocker) > NullPointerException during install (no explanation) > ---------------------------------------------------- > > Key: JBDS-3675 > URL: https://issues.jboss.org/browse/JBDS-3675 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.Beta2 > Environment: Windows 10 Pro 64bit, Oracle JDK 8_74, installer with EAP > Reporter: Hendy Irawan > Assignee: Denis Golovin > Priority: Critical > Fix For: 10.0.0.Alpha1 > > Attachments: jboss1.PNG, jboss2.PNG, jbossdev-install-error.PNG > > > Unfortunately no stacktrace whatsoever :( -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3675) NullPointerException during install (no explanation)

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3675?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-3675: --------------------------------- Fix Version/s: 10.0.0.Alpha1 (was: 9.1.0.CR1) > NullPointerException during install (no explanation) > ---------------------------------------------------- > > Key: JBDS-3675 > URL: https://issues.jboss.org/browse/JBDS-3675 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.Beta2 > Environment: Windows 10 Pro 64bit, Oracle JDK 8_74, installer with EAP > Reporter: Hendy Irawan > Assignee: Denis Golovin > Priority: Critical > Fix For: 10.0.0.Alpha1 > > Attachments: jboss1.PNG, jboss2.PNG, jbossdev-install-error.PNG > > > Unfortunately no stacktrace whatsoever :( -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3650) username used for cdk could not be used with vagrant up on cdk

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3650?page=com.atlassian.jira.plugin.... ] Alexey Kazakov commented on JBDS-3650: -------------------------------------- Just tried the following workflow: 1. Registered a new user on developers.redhat.com 2. Started downloading RHEL from developers.redhat.com 3. Signed proposed T&Cs 4. Canceled the downloading 5. Used the user name and password in the installer. Successfully installed and started the CDK server. As soon as the installer is moved to developers.redhat.com and new workflow is implemented #2 won't be needed since all T&C will be required to download the installer. The case when the installer shared by developers and not downloaded from developers.redhat.com is covered in another issue. See JBDS-3627 I'm resolving this issue to clean our JIRA. > username used for cdk could not be used with vagrant up on cdk > -------------------------------------------------------------- > > Key: JBDS-3650 > URL: https://issues.jboss.org/browse/JBDS-3650 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer, upstream > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > Priority: Blocker > Labels: havoc > Fix For: 9.1.0.CR1 > > > in demo by [~dgolovin] he mentions the username used for running the installer could not be used with vagrant registration. > Why is that ? just unique for denis usernames or general problem ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3650) username used for cdk could not be used with vagrant up on cdk

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3650?page=com.atlassian.jira.plugin.... ] Alexey Kazakov closed JBDS-3650. -------------------------------- Resolution: Done > username used for cdk could not be used with vagrant up on cdk > -------------------------------------------------------------- > > Key: JBDS-3650 > URL: https://issues.jboss.org/browse/JBDS-3650 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer, upstream > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > Priority: Blocker > Labels: havoc > Fix For: 9.1.0.CR1 > > > in demo by [~dgolovin] he mentions the username used for running the installer could not be used with vagrant registration. > Why is that ? just unique for denis usernames or general problem ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3725) Update CDK to 2.0.0.GA

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3725?page=com.atlassian.jira.plugin.... ] Alexey Kazakov closed JBDS-3725. -------------------------------- Fix Version/s: 9.1.0.CR1 (was: 9.1.0.GA) Resolution: Duplicate Issue Duplicates JBDS-3638 > Update CDK to 2.0.0.GA > ---------------------- > > Key: JBDS-3725 > URL: https://issues.jboss.org/browse/JBDS-3725 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: installer > Reporter: Alexey Kazakov > Assignee: Nick Boldt > Priority: Blocker > Labels: havoc > Fix For: 9.1.0.CR1 > > > We should make sure the installer consumes the proper CDK bits. > 1. It should be the latest nightly build until the CDK GA release is available. > 2. 2.0.0.GA build as soon as it's available. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3638) Update to official CDK v2 release

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3638?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-3638: --------------------------------- Fix Version/s: 9.1.0.GA (was: 9.1.0.CR1) > Update to official CDK v2 release > --------------------------------- > > Key: JBDS-3638 > URL: https://issues.jboss.org/browse/JBDS-3638 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: installer > Reporter: Ken Finnigan > Assignee: Denis Golovin > Priority: Blocker > Labels: havoc > Fix For: 9.1.0.GA > > > Modify https://github.com/redhat-developer-tooling/developer-platform-install/bl... to point to the CDK v2 box when a new release is available in Customer Portal. > Also change to use commented out downloadAuth() call for CDK box to provide appropriate authentication: https://github.com/redhat-developer-tooling/developer-platform-install/bl... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

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

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21984?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-21984: ----------------------------------- Steps to Reproduce: 1. Create a OS3 project 2. Create a basic javaee application 3. Create a server adapter using OS Explorer->project->eap-app->Server Adapter... 4. Create a nodejs application 5. Open a New Server Adapter wizard using OS Explorer->project->nodejs-example->Server Adapter... 6. The Source Path filed points to the wrong javaee! It's hidden by default in the "Advanced" section and very hard to notice. So it creates broken server adapter. 7. Even if manually select the correct source the OS server adapter will contain the wrong eap-app module. It should not have any wtp module it all because nodejs-example is not a wtp project. was: 1. Create a OS3 project 2. Create a basic javaee application 3. Create a server adapter using OS Explorer->project->eap-app->Server Adapter... 4. Create a nodejs application 5. Open a New Server Adapter wizard using OS Explorer->project->nodejs-example->Server Adapter... 6. The Source Path filed points to the wrong javaee! It's hidden by default in the "Advanced" section and very hard to notice. So it creates broken server adapter by default. > 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 > Fix For: 4.3.1.CR1 > > Attachments: launch_config.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)

10 years

1
0
0 / 0

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

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21984?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-21984: ----------------------------------- Description: !server-adapter.png|thumbnail! Even selecting the correct source manually doesn't help. The eclipse project is still incorrect in the launch config. See !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. was: !server-adapter.png|thumbnail! Even selecting the correct source manually doesn't help. The eclipse project is still incorrect in the launch config. See !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. > 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 > Fix For: 4.3.1.CR1 > > Attachments: launch_config.png, server-adapter.png > > > !server-adapter.png|thumbnail! > Even selecting the correct source manually doesn't help. The eclipse project is still incorrect in the launch config. > See > !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)

10 years

1
0
0 / 0

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

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21984?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-21984: ----------------------------------- Description: 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. was: !server-adapter.png|thumbnail! Even selecting the correct source manually doesn't help. The eclipse project is still incorrect in the launch config. See !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. > 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 > Fix For: 4.3.1.CR1 > > Attachments: launch_config.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)

10 years

1
0
0 / 0

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

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21984?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-21984: ----------------------------------- Description: !server-adapter.png|thumbnail! Even selecting the correct source manually doesn't help. The eclipse project is still incorrect in the launch config. See !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. was: !server-adapter.png|thumbnail! Even selecting the correct source manually doesn't help. The eclipse project is still incorrect in the launch config. See !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. > 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 > Fix For: 4.3.1.CR1 > > Attachments: launch_config.png, server-adapter.png > > > !server-adapter.png|thumbnail! > Even selecting the correct source manually doesn't help. The eclipse project is still incorrect in the launch config. > See !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)

10 years

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