October 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-25140) Server adapter: Cannot start CDK 3.2.Alpha1

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25140?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-25140: ------------------------------------------ [~odockal] ok, thx for confirming. Resolved this and linked it as being included in JBIDE-25055. > Server adapter: Cannot start CDK 3.2.Alpha1 > ------------------------------------------- > > Key: JBIDE-25140 > URL: https://issues.jboss.org/browse/JBIDE-25140 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, openshift > Affects Versions: 4.5.1.AM3 > Environment: Fedora 26 > Reporter: Ondrej Dockal > Assignee: Rob Stryker > Priority: Blocker > Labels: cdk_server_adapter, openshift_v3 > Fix For: 4.5.1.AM3 > > Attachments: CDK3SACannotStart.png > > > Starting of CDK 3 Server adapter with underlying CDK 3.2 fails to start with for no obvious reason because output of cdk starting seems alright in console. please, see > !CDK3SACannotStart.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25140) Server adapter: Cannot start CDK 3.2.Alpha1

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25140?page=com.atlassian.jira.plugi... ] Andre Dietisheim resolved JBIDE-25140. -------------------------------------- Resolution: Done > Server adapter: Cannot start CDK 3.2.Alpha1 > ------------------------------------------- > > Key: JBIDE-25140 > URL: https://issues.jboss.org/browse/JBIDE-25140 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, openshift > Affects Versions: 4.5.1.AM3 > Environment: Fedora 26 > Reporter: Ondrej Dockal > Assignee: Rob Stryker > Priority: Blocker > Labels: cdk_server_adapter, openshift_v3 > Fix For: 4.5.1.AM3 > > Attachments: CDK3SACannotStart.png > > > Starting of CDK 3 Server adapter with underlying CDK 3.2 fails to start with for no obvious reason because output of cdk starting seems alright in console. please, see > !CDK3SACannotStart.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25149) Improve code as suggested in review of PR for JBIDE-25055

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-25149: ---------------------------------------- Summary: Improve code as suggested in review of PR for JBIDE-25055 Key: JBIDE-25149 URL: https://issues.jboss.org/browse/JBIDE-25149 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdk, openshift Affects Versions: 4.5.1.AM3 Reporter: Andre Dietisheim Assignee: Rob Stryker Fix For: 4.5.x In the [PR|https://github.com/jbosstools/jbosstools-openshift/pull/1578] for JBIDE-25055 we spotted a few improvements for the code. Please perform these. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25118) improve errata waiver check script - add waivers for desktop-file-sanity, patches, IP v6

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25118?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-25118: ------------------------------------ I've added patches to the list of ignored, never-waived items. https://github.com/jbosstools/jbosstools-build-ci/commits/master And you're right, a dnf cache clean worked -- was able to install dali and verify the last two symlink waivers. \o/ Are we done here? Or can you think of more error types / parsing rules to add? > improve errata waiver check script - add waivers for desktop-file-sanity, patches, IP v6 > ---------------------------------------------------------------------------------------- > > Key: JBIDE-25118 > URL: https://issues.jboss.org/browse/JBIDE-25118 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, rpm > Reporter: Nick Boldt > Assignee: Nick Boldt > Labels: release > Fix For: 4.5.1.Final > > Attachments: errata-waiver.results-can't-find-dali.txt > > > {quote} > It sounds like we could add these check types to my script: > > * desktop-file-sanity (always waive?) > * IP v6 (always waive using existing waiver details, eg., https://errata.devel.redhat.com/rpmdiff/show/182126?result_id=5028358 > Yep, yep. > > * patches (waive if %autopatch) > And if the only other complaints are "patch not applied" (I'm not sure if this check may throw different kinds of error){quote} > So, the next time we have an errata with the above types of issues, I can update this script [1] to add those use cases. > [1] https://github.com/jbosstools/jbosstools-build-ci/blob/master/util/errata... > cc: [~mat.booth] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4488) Very slow initial startup for Eclipse

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4488?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4488: ----------------------------- Fix Version/s: 11.x (was: 11.1.0.AM3) > Very slow initial startup for Eclipse > ------------------------------------- > > Key: JBDS-4488 > URL: https://issues.jboss.org/browse/JBDS-4488 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, rpm > Affects Versions: 11.0.0.AM2 > Environment: * rh-eclipse47 (http://download.eng.bos.redhat.com/rel-eng/DevTools-1.0-RHEL-7-Beta-1.0/c...) > * devstudio (https://devstudio.jboss.com/11/snapshots/builds/devstudio.rpm_master/2017...) > Reporter: Martin Coufal > Assignee: Nick Boldt > Priority: Minor > Fix For: 11.x > > > Launching Eclipse after installation of any plugins from Devstudio (Red Hat Central) takes VERY long time (around 180s). This is regression bug, for more details, see [1]. > Note: Also, launching rh-eclipse47 with Devstudio takes about 90s. > [1]: https://bugzilla.redhat.com/show_bug.cgi?id=1392095 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4531) Can jbosstools/devstudio depend on a single version of Guava?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4531?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4531: ----------------------------- Fix Version/s: 11.x (was: 11.1.0.AM3) > Can jbosstools/devstudio depend on a single version of Guava? > ------------------------------------------------------------- > > Key: JBDS-4531 > URL: https://issues.jboss.org/browse/JBDS-4531 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Sub-task > Components: build, rpm, target-platform, updatesite > Affects Versions: 11.1.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 11.x > > > Currently the devstudio RPM depends on Guava 15, 18 and 21 (all three are in the devstudio TP). Can we depend on just the latest, which is going to be 23 in Fedora. See https://bugzilla.redhat.com/show_bug.cgi?id=1481219 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4555) Unknown category error in Red Hat Central - Integration Stack connectors don't show Supported status

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4555?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4555: ----------------------------- Summary: Unknown category error in Red Hat Central - Integration Stack connectors don't show Supported status (was: Unknown category error in Red Hat Central) > Unknown category error in Red Hat Central - Integration Stack connectors don't show Supported status > ---------------------------------------------------------------------------------------------------- > > Key: JBDS-4555 > URL: https://issues.jboss.org/browse/JBDS-4555 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: central > Affects Versions: 11.1.0.AM2 > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 11.1.0.GA > > Attachments: categories.png > > > I installed devstudio 11.1.0.AM2 B1060 and went to central's Updates/Software tab and immediately got these errors: > Unknown category 'com.jboss.jbds.discovery.certification.supported' referenced by connector 'jboss.integration-stack.bundle.switchyard' declared in com.jboss.jbds.central.discovery.integration_stack_11.0.0.GA_v20170811_1249_B41.jar_3405701925693823433.jar > Unknown category 'com.jboss.jbds.discovery.certification.supported' referenced by connector 'jboss.integration-stack.bundle.soa' declared in com.jboss.jbds.central.discovery.integration_stack_11.0.0.GA_v20170811_1249_B41.jar_3405701925693823433.jar > Unknown category 'com.jboss.jbds.discovery.certification.supported' referenced by connector 'jboss.integration-stack.bundle.bpr' declared in com.jboss.jbds.central.discovery.integration_stack_11.0.0.GA_v20170811_1249_B41.jar_3405701925693823433.jar -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4321) Unable to start Devstudio without -clean after install of any stuff from RH Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4321?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4321: ----------------------------- Fix Version/s: 11.x (was: 11.1.0.AM3) > Unable to start Devstudio without -clean after install of any stuff from RH Central > ----------------------------------------------------------------------------------- > > Key: JBDS-4321 > URL: https://issues.jboss.org/browse/JBDS-4321 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, rpm > Affects Versions: 10.4.0.AM2 > Environment: RHEL7, RHSCL 2.4 Beta 1.1, Devstudio 10.4-0.20170320.0955.el7 > Reporter: Lukáš Valach > Assignee: Nick Boldt > Fix For: 11.x > > Attachments: Start_without_clean.png, rh-eclipse46-devstudio10.4-0.20170320.0955.el7.log.Without_clean_test_strict.txt, rh-eclipse46-devstudio10.4-0.20170425.1442.el7.log.20170426-0913_strict.txt, rh-eclipse46-devstudio10.4-0.20170425.1442.el7.log.20170426-0913_strict_FILTERED.txt, rh-eclipse46-devstudio10.4-0.20170428.0013.el7.log.All_from_central_without_clean_Fedora24_strict.txt, rh-eclipse46-devstudio10.4-0.20170428.0013.el7.log.All_from_central_without_clean_RHEL7_strict.txt, rpm-installed-everything-from-central.png, rpm-installed-everything-from-central.update.rpm.deps.txt > > > When I install something from Red Hat Central and then start Devstudio without -clean then I get this error: > {code} > !ENTRY org.eclipse.e4.ui.workbench 4 0 2017-03-23 07:51:22.689 > !MESSAGE Unable to load resource platform:/plugin/org.eclipse.platform/LegacyIDE.e4xmi > !STACK 0 > java.lang.NullPointerException > {code} > There are multiple errors but this one seems to be common for multiple items. > And this window appear: > !Start_without_clean.png|thumbnail! > There is easy workaround but user won't start Devstudio with -clean and many of them could be upset. > Please see the log: [^rh-eclipse46-devstudio10.4-0.20170320.0955.el7.log.Without_clean_test_strict.txt] There is what I got when I installed FindBugs. I put some comments there so you can find sections installation/start without clean/start with clean. > CC: [~psrna] [~vkadlcik] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4555) Unknown category error in Red Hat Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4555?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4555: ---------------------------------- No what happens is the CERTIFICATION label disappears. Compare the Fuse entry, which is Supported, to the ones above, which don't have a certification link. This should be fixed for GA once IS 11.1.0.Beta1 is released. > Unknown category error in Red Hat Central > ----------------------------------------- > > Key: JBDS-4555 > URL: https://issues.jboss.org/browse/JBDS-4555 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: central > Affects Versions: 11.1.0.AM2 > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 11.1.0.GA > > Attachments: categories.png > > > I installed devstudio 11.1.0.AM2 B1060 and went to central's Updates/Software tab and immediately got these errors: > Unknown category 'com.jboss.jbds.discovery.certification.supported' referenced by connector 'jboss.integration-stack.bundle.switchyard' declared in com.jboss.jbds.central.discovery.integration_stack_11.0.0.GA_v20170811_1249_B41.jar_3405701925693823433.jar > Unknown category 'com.jboss.jbds.discovery.certification.supported' referenced by connector 'jboss.integration-stack.bundle.soa' declared in com.jboss.jbds.central.discovery.integration_stack_11.0.0.GA_v20170811_1249_B41.jar_3405701925693823433.jar > Unknown category 'com.jboss.jbds.discovery.certification.supported' referenced by connector 'jboss.integration-stack.bundle.bpr' declared in com.jboss.jbds.central.discovery.integration_stack_11.0.0.GA_v20170811_1249_B41.jar_3405701925693823433.jar -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20431) Make sure all installed features have branding features and are shown in Help->About->Installation Details->Features

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20431?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-20431: ------------------------------- Fix Version/s: 4.5.x (was: 4.5.1.AM3) > Make sure all installed features have branding features and are shown in Help->About->Installation Details->Features > -------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20431 > URL: https://issues.jboss.org/browse/JBIDE-20431 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim, common, visual-page-editor-core > Affects Versions: 4.3.0.Beta2 > Reporter: Alexey Kazakov > Assignee: Nick Boldt > Priority: Minor > Fix For: 4.5.x > > Attachments: features.txt, featureslist-00.png, featureslist-01.png, jst-feature.plugins.png > > > We miss a few features in Help->About->Installation Details->Features such as VPE, browsersim, JST. Maybe more. > See JBIDE-20069 for details how we can fix that. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 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 October 2017