January 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-4238) CDK installer: should install into Application for MacOS

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBDS-4238?page=com.atlassian.jira.plugin.... ] Andre Dietisheim updated JBDS-4238: ----------------------------------- Description: the cdk installer for MacOS installs DevStudio and the CDK into <Home>/DevelopmentSuite. Home is afaik not visible by default in Finder. Furthermore applications are by default installed into Applications in MacOS. In order to behave like a first class MacOS-citizen we should install DevSuite and CDK independently into Applications (or maybe CDK into Document as it isnt the application in the strict sense, it's only a Virtualbox image, a Vagrantfile etc.) (was: the cdk installer for MacOS installs DevStudio and the CDK into ${Home}/DevelopmentSuite. Home is afaik not visible by default in Finder. Furthermore applications are by default installed into Applications in MacOS. In order to behave like a first class MacOS-citizen we should install DevSuite and CDK independently into Applications (or maybe CDK into Document as it isnt the application in the strict sense, it's only a Virtualbox image, a Vagrantfile etc.)) > CDK installer: should install into Application for MacOS > -------------------------------------------------------- > > Key: JBDS-4238 > URL: https://issues.jboss.org/browse/JBDS-4238 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 10.2.0.AM1 > Reporter: Andre Dietisheim > > the cdk installer for MacOS installs DevStudio and the CDK into <Home>/DevelopmentSuite. Home is afaik not visible by default in Finder. Furthermore applications are by default installed into Applications in MacOS. In order to behave like a first class MacOS-citizen we should install DevSuite and CDK independently into Applications (or maybe CDK into Document as it isnt the application in the strict sense, it's only a Virtualbox image, a Vagrantfile etc.) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4238) CDK installer: should install into Application for MacOS

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBDS-4238?page=com.atlassian.jira.plugin.... ] Aurélien Pupier updated JBDS-4238: ---------------------------------- Summary: CDK installer: should install into Application for MacOS (was: CDK installer: should install into Application) > CDK installer: should install into Application for MacOS > -------------------------------------------------------- > > Key: JBDS-4238 > URL: https://issues.jboss.org/browse/JBDS-4238 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 10.2.0.AM1 > Reporter: Andre Dietisheim > > the cdk installer for MacOS installs DevStudio and the CDK into ${Home}/DevelopmentSuite. Home is afaik not visible by default in Finder. Furthermore applications are by default installed into Applications in MacOS. In order to behave like a first class MacOS-citizen we should install DevSuite and CDK independently into Applications (or maybe CDK into Document as it isnt the application in the strict sense, it's only a Virtualbox image, a Vagrantfile etc.) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4238) CDK installer: should install into Application

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBDS-4238: -------------------------------------- Summary: CDK installer: should install into Application Key: JBDS-4238 URL: https://issues.jboss.org/browse/JBDS-4238 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Enhancement Components: platform-installer Affects Versions: 10.2.0.AM1 Reporter: Andre Dietisheim the cdk installer for MacOS installs DevStudio and the CDK into ${Home}/DevelopmentSuite. Home is afaik not visible by default in Finder. Furthermore applications are by default installed into Applications in MacOS. In order to behave like a first class MacOS-citizen we should install DevSuite and CDK independently into Applications (or maybe CDK into Document as it isnt the application in the strict sense, it's only a Virtualbox image, a Vagrantfile etc.) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23704) Application wizard: Application based on builder images do not have prefilled configuration when opened from Central

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23704?page=com.atlassian.jira.plugi... ] Radim Hopp updated JBIDE-23704: ------------------------------- Environment: Devstudio 10.3.0.AM1. Reproducible against internal OS3 instance and agains OS inside CDK 2.3 > Application wizard: Application based on builder images do not have prefilled configuration when opened from Central > -------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23704 > URL: https://issues.jboss.org/browse/JBIDE-23704 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.AM1 > Environment: Devstudio 10.3.0.AM1. > Reproducible against internal OS3 instance and agains OS inside CDK 2.3 > Reporter: Radim Hopp > > This test started to fail: https://github.com/jbosstools/jbosstools-integration-tests/blob/master/te... and I was able to reproduce it by hand. > It looks very simmilar to JBIDE-22704 except App name is preconfigured, but Git repo URL is not (and thus I cannot continue to next pages of this wizard). > This works when new openshift app wizard is opened via File -> New -> Other... -> OpenShift -> OpenShift Application or by right-clicking on OpenShift connection or OpenShift project in OpenShift explorer. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23704) Application wizard: Application based on builder images do not have prefilled configuration when opened from Central

by Radim Hopp (JIRA)

Radim Hopp created JBIDE-23704: ---------------------------------- Summary: Application wizard: Application based on builder images do not have prefilled configuration when opened from Central Key: JBIDE-23704 URL: https://issues.jboss.org/browse/JBIDE-23704 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.4.3.AM1 Reporter: Radim Hopp This test started to fail: https://github.com/jbosstools/jbosstools-integration-tests/blob/master/te... and I was able to reproduce it by hand. It looks very simmilar to JBIDE-22704 except App name is preconfigured, but Git repo URL is not (and thus I cannot continue to next pages of this wizard). This works when new openshift app wizard is opened via File -> New -> Other... -> OpenShift -> OpenShift Application or by right-clicking on OpenShift connection or OpenShift project in OpenShift explorer. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4175) NPE/broken functionality/cannot start after install from Red Hat Central into rh-eclipse46-devstudio

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBDS-4175?page=com.atlassian.jira.plugin.... ] Lukáš Valach commented on JBDS-4175: ------------------------------------ I confirm that JRebel 7.0.2 works fine with 10.3-0.20170109.1027.el7. There are no errors in the log. > NPE/broken functionality/cannot start after install from Red Hat Central into rh-eclipse46-devstudio > ---------------------------------------------------------------------------------------------------- > > Key: JBDS-4175 > URL: https://issues.jboss.org/browse/JBDS-4175 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: central-update, rpm > Environment: RHEL 7.2 with RHSCL repositories available: > * RHSCL 2.3 RC (http://download-node-02.eng.bos.redhat.com/rel-eng/RHSCL-2.3-RHEL-7-RC-1....) > * update for RHBZ#1392095 (http://nest.test.redhat.com/mnt/qa/scratch/vkadlcik/eclipse/repos/rhscl23...) > Reporter: Václav Kadlčík > Assignee: Nick Boldt > Fix For: 10.3.0.AM2 > > Attachments: JBDS-4175_logs_first_half.tar.gz, devstudio-is-major-feature-groups-to-test.png, rh-eclipse46-devstudio10.2.log.20161115-0953.txt, rh-eclipse46-devstudio10.2.log.20161118-1112_strict.txt, spring-ide-fail-aop.png, spring-ide-fail-list.png, spring-ide-fail-npe.png, spring-ide-fail-project-explorer-broken-package-explorer-OK.png, spring-ide-fail.png, spring-ide-view-fail.png, springide382.png, sw_to_install.txt, workspace.log, wst.xsd.core_diff.png > > > I installed rh-eclipse46-devstudio-10.2-0.20161111.0219.el7.x86_64.rpm and followed Nick's scenario [1]. In Red Hat Central, I clicked "Select All" (it found 36 items), then "Install/Update", did all the confirmations, including a restart. After the restart, Eclipse died on java.lang.NullPointerException. I'm attaching the workspace log (aside from the NPE, it's full of "Could not resolve module"). > I reproduced the problem several times on two different machines. The update for RHBZ#1392095 (rh-eclipse46-eclipse-4.6.1-2.4.el7) isn't necessary, it just makes the reproduction much faster. > Not sure how related it is, but rh-eclipse46 disallows updating packages installed from RPM [2]. But in the list of software to be installed/updated, I saw, among others, EGit and Mylyn, which are definitely included in rh-eclipse46-base. In any case, I'm attaching the list, too. > [1] https://bugzilla.redhat.com/show_bug.cgi?id=1392095#c6 > [2] https://bugzilla.redhat.com/show_bug.cgi?id=1173024 > (copied from comment below to make it sticky) > Results of installing first half of the items in Central: > ||Item||Result||Description or Errors|| > |Android_Development_Tools|(/)|| > |JBoss_Hybrid_Mobile_Tools|(/)|| > |AngularJS_for_Web_Tools|(x)|IllegalStateException: BundleContext, NullPointerException| > |JBoss_Arquillian_Tools|(/)|| > |JBoss_Forge_Tools|(/)|| > |JBoss_OpenShift_2_Tools|(x)|BundleException| > |JBoss_OpenShift_3_Tools|(x)|BundleException| > |JBoss_Portlet_Tools|(x)|BundleException, NullPointerException, eclipse didn't start| > |JBoss_Seam_Tools|(x)|BundleException, NullPointerException, eclipse didn't start| > |JBoss_Tools_LiveReload|(x)|BundleException| > |JST_Server|(x)|BundleException| > |Spring_IDE|(x)|BundleException, NullPointerException, eclipse didn't start| > |Atlassian_Connector|(x)|BundleException, loader constraint violation| > |Eclipse_EGit_Mylyn_Support|(x)|BundleException| > |Subclipse_SVNKit|(/)|First attempt failed due to SocketTimeoutException but second passed| > |Subclipse_SVNKit_Mylyn_Support|(x)|BundleException| > |Eclipse_Checkstyle|(x)|NullPointerException| > All logs [^JBDS-4175_logs_first_half.tar.gz]. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23681) Hibernate New and Noteworthy for 4.4.3.AM1

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23681?page=com.atlassian.jira.plugi... ] Koen Aers closed JBIDE-23681. ----------------------------- Resolution: Rejected > Hibernate New and Noteworthy for 4.4.3.AM1 > --------------------------------------------------- > > Key: JBIDE-23681 > URL: https://issues.jboss.org/browse/JBIDE-23681 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: hibernate > Reporter: Jeff MAURY > Assignee: Koen Aers > Priority: Critical > > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Hibernate JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for Hibernate, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Hibernate by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form 'JBIDE-56789 #comment Create N&N for Hibernate4.4.3.AM1 #close', and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for Hibernate for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23684) Forge New and Noteworthy for 4.4.3.AM1

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23684?page=com.atlassian.jira.plugi... ] George Gastaldi closed JBIDE-23684. ----------------------------------- Resolution: Rejected > Forge New and Noteworthy for 4.4.3.AM1 > --------------------------------------------------- > > Key: JBIDE-23684 > URL: https://issues.jboss.org/browse/JBIDE-23684 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: forge > Reporter: Jeff MAURY > Assignee: George Gastaldi > Priority: Critical > > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Forge JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for Forge, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Forge by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form 'JBIDE-56789 #comment Create N&N for Forge4.4.3.AM1 #close', and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for Forge for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22805) Add Scale... menus on Pod resources

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22805?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-22805: ------------------------------- Labels: new_and_noteworthy (was: ) > Add Scale... menus on Pod resources > ----------------------------------- > > Key: JBIDE-22805 > URL: https://issues.jboss.org/browse/JBIDE-22805 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.1.AM1 > Reporter: Fred Bricon > Assignee: Viacheslav Kabanovich > Labels: new_and_noteworthy > Fix For: 4.4.3.AM1 > > > I'm regularly confused/frustrated to not find the Scale... menus on the running pods. Each time I need to slap myself in the face to remind me I need to go to the Service level. > I think it'd be more intuitive if the scale menus were present on the running pods (not on the build ones). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23700) Batch New and Noteworthy for 4.4.3.AM1

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23700?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-23700. ------------------------------ Resolution: Rejected > Batch New and Noteworthy for 4.4.3.AM1 > --------------------------------------------------- > > Key: JBIDE-23700 > URL: https://issues.jboss.org/browse/JBIDE-23700 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: batch > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Critical > > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Batch JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for Batch, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Batch by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form 'JBIDE-56789 #comment Create N&N for Batch4.4.3.AM1 #close', and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for Batch for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 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 2017