August 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24874) Browse button for Minishift Home is actually selecting Minishift Binary

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24874?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-24874. --------------------------------- Verified in devstudio 11.1.0.AM1 > Browse button for Minishift Home is actually selecting Minishift Binary > ----------------------------------------------------------------------- > > Key: JBIDE-24874 > URL: https://issues.jboss.org/browse/JBIDE-24874 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.5.1.AM1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.5.1.AM1 > > > Today I noticed that if I open the server editor for a cdk 3 adapter and try to change the minishift home using the browse button, it does not work as expected. > First thing I noticed is that you cannot select a directory - when you find your directory and click Open, it will simply take you inside. And then when you select a file and click Open, you will see that the Minishift home field does not change, but the Minishift Binary field does. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24825) Freemarker New and Noteworthy for 4.5.1.AM1

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24825?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-24825. ------------------------------ Resolution: Rejected > Freemarker New and Noteworthy for 4.5.1.AM1 > --------------------------------------------------- > > Key: JBIDE-24825 > URL: https://issues.jboss.org/browse/JBIDE-24825 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: freemarker > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Critical > Fix For: 4.5.1.AM1 > > > Jeff MAURY, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Freemarker 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 Freemarker, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Freemarker 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... {code}JBIDE-24806 #comment Create N&N for Freemarker 4.5.1.AM1 #close{code}... 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 Freemarker for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24830) LiveReload New and Noteworthy for 4.5.1.AM1

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24830?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-24830. ------------------------------ Resolution: Rejected > LiveReload New and Noteworthy for 4.5.1.AM1 > --------------------------------------------------- > > Key: JBIDE-24830 > URL: https://issues.jboss.org/browse/JBIDE-24830 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: livereload > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Critical > Fix For: 4.5.1.AM1 > > > Jeff MAURY, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed LiveReload 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 LiveReload, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for LiveReload 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... {code}JBIDE-24806 #comment Create N&N for LiveReload 4.5.1.AM1 #close{code}... 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 LiveReload for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24827) Batch New and Noteworthy for 4.5.1.AM1

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24827?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-24827. ------------------------------ Resolution: Rejected > Batch New and Noteworthy for 4.5.1.AM1 > --------------------------------------------------- > > Key: JBIDE-24827 > URL: https://issues.jboss.org/browse/JBIDE-24827 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: batch > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Critical > Fix For: 4.5.1.AM1 > > > Jeff MAURY, > 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... {code}JBIDE-24806 #comment Create N&N for Batch 4.5.1.AM1 #close{code}... 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)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24896) Cannot start any JBoss server

by Martin Malina (JIRA)

Martin Malina created JBIDE-24896: ------------------------------------- Summary: Cannot start any JBoss server Key: JBIDE-24896 URL: https://issues.jboss.org/browse/JBIDE-24896 Project: Tools (JBoss Tools) Issue Type: Bug Components: server Affects Versions: 4.5.1.AM1 Reporter: Martin Malina Priority: Blocker When I try to start any server such as WildFly or EAP 6/7, I immediately get a NPE: {code} An internal error occurred during: "Starting WildFly 10.1". java.lang.NullPointerException {code} {code} An internal error occurred during: "Starting WildFly 10.1". java.lang.NullPointerException at org.jboss.ide.eclipse.as.core.extensions.descriptors.XMLDocumentRepository.refresh(XMLDocumentRepository.java:131) at org.jboss.ide.eclipse.as.core.extensions.descriptors.XPathQuery.refresh(XPathQuery.java:146) at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.findPort(XPathsPortsController.java:84) at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.getPortOffset(XPathsPortsController.java:132) at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.getJBossWebPort(XPathsPortsController.java:114) at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.findPort(XPathsPortsController.java:58) at org.jboss.ide.eclipse.as.core.server.internal.JBossServer.findPort(JBossServer.java:209) at org.jboss.ide.eclipse.as.core.server.internal.JBossServer.getJBossWebPort(JBossServer.java:195) at org.jboss.ide.eclipse.as.core.extensions.polling.WebPortPoller.getURL(WebPortPoller.java:84) at org.jboss.ide.eclipse.as.core.extensions.polling.WebPortPoller.getCurrentStateSynchronous(WebPortPoller.java:155) at org.jboss.ide.eclipse.as.core.util.PollThreadUtils.isServerStarted(PollThreadUtils.java:218) at org.jboss.ide.eclipse.as.core.util.PollThreadUtils.isServerStarted(PollThreadUtils.java:204) at org.jboss.ide.eclipse.as.core.server.internal.launch.StandardLocalJBossStartLaunchDelegate.isServerStarted(StandardLocalJBossStartLaunchDelegate.java:67) at org.jboss.ide.eclipse.as.wtp.core.server.launch.AbstractStartJavaServerLaunchDelegate.preLaunchCheck(AbstractStartJavaServerLaunchDelegate.java:126) at org.jboss.tools.as.core.server.controllable.subsystems.internal.LocalJBossLaunchController.preLaunchCheck(LocalJBossLaunchController.java:110) at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.preLaunchCheck(ControllableServerLaunchConfiguration.java:86) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:840) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731) at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3566) at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3502) at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:377) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56) {code} I tried EAP 6.4, 7.0, 7.1 and WildFly 10.1. This is with devstudio 11.1.0.AM1 B873. As indicated by Rob, this is likely caused by this commit from JBIDE-24758: https://github.com/jbosstools/jbosstools-server/commit/1a58a4d54097e4d927... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24896) Cannot start any JBoss server

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24896?page=com.atlassian.jira.plugi... ] Martin Malina reassigned JBIDE-24896: ------------------------------------- Assignee: Rob Stryker > Cannot start any JBoss server > ----------------------------- > > Key: JBIDE-24896 > URL: https://issues.jboss.org/browse/JBIDE-24896 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.5.1.AM1 > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Blocker > > When I try to start any server such as WildFly or EAP 6/7, I immediately get a NPE: > {code} > An internal error occurred during: "Starting WildFly 10.1". > java.lang.NullPointerException > {code} > {code} > An internal error occurred during: "Starting WildFly 10.1". > java.lang.NullPointerException > at org.jboss.ide.eclipse.as.core.extensions.descriptors.XMLDocumentRepository.refresh(XMLDocumentRepository.java:131) > at org.jboss.ide.eclipse.as.core.extensions.descriptors.XPathQuery.refresh(XPathQuery.java:146) > at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.findPort(XPathsPortsController.java:84) > at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.getPortOffset(XPathsPortsController.java:132) > at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.getJBossWebPort(XPathsPortsController.java:114) > at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.findPort(XPathsPortsController.java:58) > at org.jboss.ide.eclipse.as.core.server.internal.JBossServer.findPort(JBossServer.java:209) > at org.jboss.ide.eclipse.as.core.server.internal.JBossServer.getJBossWebPort(JBossServer.java:195) > at org.jboss.ide.eclipse.as.core.extensions.polling.WebPortPoller.getURL(WebPortPoller.java:84) > at org.jboss.ide.eclipse.as.core.extensions.polling.WebPortPoller.getCurrentStateSynchronous(WebPortPoller.java:155) > at org.jboss.ide.eclipse.as.core.util.PollThreadUtils.isServerStarted(PollThreadUtils.java:218) > at org.jboss.ide.eclipse.as.core.util.PollThreadUtils.isServerStarted(PollThreadUtils.java:204) > at org.jboss.ide.eclipse.as.core.server.internal.launch.StandardLocalJBossStartLaunchDelegate.isServerStarted(StandardLocalJBossStartLaunchDelegate.java:67) > at org.jboss.ide.eclipse.as.wtp.core.server.launch.AbstractStartJavaServerLaunchDelegate.preLaunchCheck(AbstractStartJavaServerLaunchDelegate.java:126) > at org.jboss.tools.as.core.server.controllable.subsystems.internal.LocalJBossLaunchController.preLaunchCheck(LocalJBossLaunchController.java:110) > at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.preLaunchCheck(ControllableServerLaunchConfiguration.java:86) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:840) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731) > at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3566) > at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3502) > at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:377) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56) > {code} > I tried EAP 6.4, 7.0, 7.1 and WildFly 10.1. > This is with devstudio 11.1.0.AM1 B873. > As indicated by Rob, this is likely caused by this commit from JBIDE-24758: > https://github.com/jbosstools/jbosstools-server/commit/1a58a4d54097e4d927... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23882) Automate test of installation of software from Red Hat Central into devstudio RPM (headless)

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23882?page=com.atlassian.jira.plugi... ] Lukáš Valach updated JBIDE-23882: --------------------------------- Sprint: (was: devex #136 August 2017) > Automate test of installation of software from Red Hat Central into devstudio RPM (headless) > -------------------------------------------------------------------------------------------- > > Key: JBIDE-23882 > URL: https://issues.jboss.org/browse/JBIDE-23882 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, qa > Environment: RHEL7, devstudio RPM > Reporter: Lukáš Valach > Assignee: Lukáš Valach > Fix For: 4.5.x > > > We need to catch problems like in JBDS-4263. > [~lvalach] said: {quote} > I think I should automate test of installation from Central, because this procedure is quite time consuming. > {quote} > [~nickboldt] said: {quote} > before you do that might want to look at the existing automated tests we have: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-g.... > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-p.... > of course those are not based on rpm installs, but on eclipse platform binary or JEE packages. We could try modifying both p2director (headless) and install-grinder (head w/ swt) scripts to support doing an rpm install too... not sure how since that would require running as root > maybe you could just use the scripts to automate the process of doing the installs AFTER you have rpm installed locally > so ... partial automation > {quote} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3839) Change the progress bar color to red in case of failure

by Mohit Suman (JIRA)

[ https://issues.jboss.org/browse/JBDS-3839?page=com.atlassian.jira.plugin.... ] Mohit Suman reassigned JBDS-3839: --------------------------------- Assignee: Mohit Suman (was: Denis Golovin) > Change the progress bar color to red in case of failure > ------------------------------------------------------- > > Key: JBDS-3839 > URL: https://issues.jboss.org/browse/JBDS-3839 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 9.1.0.CR1 > Reporter: Pavol Srna > Assignee: Mohit Suman > Labels: ui > Fix For: 11.x > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24844) fix *.it.weekly jobs to properly build on macos w/ jdk1.8 (not openjdk 1.8)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24844?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24844: ------------------------------- Attachment: red-weekly-smoke-tests.png > fix *.it.weekly jobs to properly build on macos w/ jdk1.8 (not openjdk 1.8) > --------------------------------------------------------------------------- > > Key: JBIDE-24844 > URL: https://issues.jboss.org/browse/JBIDE-24844 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.5.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.1.AM2 > > Attachments: red-weekly-smoke-tests.png > > > As noted in JBIDE-24835, the it.weekly jobs try to run on macos w/ openjdk 1.8, but no such JDK exists there. Therefore need a combinationFilter to let us build with openjdk on windows and linux, and oracle jdk on macos. > {code} > combinationFilter = (label_exp == "macosx").implies(jdk == "jdk1.8") && (label_exp != "macosx").implies(jdk == "openjdk-1.8") > {code} > TODO: verify all the jobs linked from here [1] are working for all OSes > [1] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/devstudi... > * hibernatetools-itests.download-devstudio - test failures on rhel7 (not a matrix job) > * livereload.it.weekly - failing for windows 8.1 & 10 due to unresolved parent pom > * browsersim.it.weekly - failing for windows 8.1 due to unresolved parent pom > * archives.it.weekly - failed to resolve tycho-plugins:repo-utils1.0.0 (bad Nexus settings?) on win81 > * vpe.it.weekly - test failures on win81 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24844) fix *.it.weekly jobs to properly build on macos w/ jdk1.8 (not openjdk 1.8)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24844?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24844: ------------------------------------ Updated a number of smoke/weekly jobs to use label_exp instead of label, and run the macosx configs w/ jdk1.8 (not openjdk-1.8). For jobs where configuration has fedora or ubuntu, I didn't change the jobs (even if there was a filter for mac, but the job doesn't run on mac). https://github.com/jbdevstudio/jbdevstudio-ci/commit/c6da931da894697a0b2c... Current state: !red-weekly-smoke-tests.png|thumbnail! See also JBIDE-24895 > fix *.it.weekly jobs to properly build on macos w/ jdk1.8 (not openjdk 1.8) > --------------------------------------------------------------------------- > > Key: JBIDE-24844 > URL: https://issues.jboss.org/browse/JBIDE-24844 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.5.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.1.AM2 > > Attachments: red-weekly-smoke-tests.png > > > As noted in JBIDE-24835, the it.weekly jobs try to run on macos w/ openjdk 1.8, but no such JDK exists there. Therefore need a combinationFilter to let us build with openjdk on windows and linux, and oracle jdk on macos. > {code} > combinationFilter = (label_exp == "macosx").implies(jdk == "jdk1.8") && (label_exp != "macosx").implies(jdk == "openjdk-1.8") > {code} > TODO: verify all the jobs linked from here [1] are working for all OSes > [1] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/devstudi... > * hibernatetools-itests.download-devstudio - test failures on rhel7 (not a matrix job) > * livereload.it.weekly - failing for windows 8.1 & 10 due to unresolved parent pom > * browsersim.it.weekly - failing for windows 8.1 due to unresolved parent pom > * archives.it.weekly - failed to resolve tycho-plugins:repo-utils1.0.0 (bad Nexus settings?) on win81 > * vpe.it.weekly - test failures on win81 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

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