January 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-23812) Server adapter editor: server adapter wired to offline server is not editable any more

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23812?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23812: ------------------------------------- Attachment: (was: ©.png) > Server adapter editor: server adapter wired to offline server is not editable any more > -------------------------------------------------------------------------------------- > > Key: JBIDE-23812 > URL: https://issues.jboss.org/browse/JBIDE-23812 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.AM2 > Reporter: Andre Dietisheim > Fix For: 4.4.3.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23812) Server adapter editor: server adapter wired to offline server is not editable any more

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23812?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23812: ------------------------------------- Attachment: ©.png > Server adapter editor: server adapter wired to offline server is not editable any more > -------------------------------------------------------------------------------------- > > Key: JBIDE-23812 > URL: https://issues.jboss.org/browse/JBIDE-23812 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.AM2 > Reporter: Andre Dietisheim > Fix For: 4.4.3.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4164) Project Examples don't work behind proxy

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBDS-4164?page=com.atlassian.jira.plugin.... ] Snjezana Peco updated JBDS-4164: -------------------------------- Fix Version/s: 10.3.0.GA (was: 10.3.0.AM2) > Project Examples don't work behind proxy > ---------------------------------------- > > Key: JBDS-4164 > URL: https://issues.jboss.org/browse/JBDS-4164 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: jbpm, project-examples, upstream > Affects Versions: 9.1.0.GA > Reporter: Denis Golovin > Assignee: Snjezana Peco > Fix For: 10.3.0.GA > > > Issue is reported on forum (see [forum reference|https://developer.jboss.org/message/964401#964401]). Examples does not work behind proxy with eclipse configured to use proxy in settings. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22718) NullPointerException in HIDDEN

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22718?page=com.atlassian.jira.plugi... ] Snjezana Peco updated JBIDE-22718: ---------------------------------- Fix Version/s: 4.4.3.Final (was: 4.4.3.AM2) > NullPointerException in HIDDEN > ------------------------------ > > Key: JBIDE-22718 > URL: https://issues.jboss.org/browse/JBIDE-22718 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: arquillian > Affects Versions: 4.4.0.Final > Reporter: Automated Error Reporting Bot > Assignee: Snjezana Peco > Fix For: 4.4.3.Final > > > The following problem was reported via the automated error reporting: > Message: > {noformat} > java.lang.NullPointerException: null > at HIDDEN.HIDDEN(HIDDEN:-1) > at sun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethodAccessorImpl.java:-2) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.jboss.tools.arquillian.ui.internal.utils.ArquillianUIUtil.addContainerProperties(ArquillianUIUtil.java:581) > at org.jboss.tools.arquillian.ui.internal.utils.ArquillianUIUtil.getArquillianProperties(ArquillianUIUtil.java:507) > at org.jboss.tools.arquillian.ui.internal.launcher.ArquillianTab.initializeFrom(ArquillianTab.java:644) > at org.eclipse.debug.ui.AbstractLaunchConfigurationTab.activated(AbstractLaunchConfigurationTab.java:411) > at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.handleTabSelected(LaunchConfigurationTabGroupViewer.java:1365) > at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer$6.widgetSelected(LaunchConfigurationTabGroupViewer.java:377) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > {noformat} > Bundles: > | org.eclipse.core.runtime | 3.11.1.v20150903-1804 | 3.11.1.v20150903-1804 | > | org.eclipse.debug.ui | 3.11.101.v20160203-1230 | 3.11.101.v20160203-1230 | > | org.eclipse.jface | 3.11.1.v20160128-1644 | 3.11.1.v20160128-1644 | > | org.eclipse.swt | 3.104.2.v20160212-1350 | 3.104.2.v20160212-1350 | > | org.eclipse.ui | 3.107.0.v20150507-1945 | 3.107.0.v20150507-1945 | > | org.jboss.tools.arquillian.ui | 1.2.1.Final-v20160331-0142-B69 | 1.2.1.Final-v20160331-0142-B69 | > Operating Systems: > | Windows | 6.3.0 | 6.3.0 | > The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/57344b2ee4b0138d62...] for the latest data. > Thank you for your assistance. > Your friendly error-reports-inbox. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22719) JavaModelException below DependencyCache.getDependentTypes (thrown in JavaElement.newJavaModelException)

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22719?page=com.atlassian.jira.plugi... ] Snjezana Peco updated JBIDE-22719: ---------------------------------- Fix Version/s: 4.4.3.Final (was: 4.4.3.AM2) > JavaModelException below DependencyCache.getDependentTypes (thrown in JavaElement.newJavaModelException) > -------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22719 > URL: https://issues.jboss.org/browse/JBIDE-22719 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: arquillian > Affects Versions: 4.4.0.Final > Reporter: Automated Error Reporting Bot > Assignee: Snjezana Peco > Fix For: 4.4.3.Final > > > The following problem was reported via the automated error reporting: > Message: ticket-monster does not exist > {noformat} > org.eclipse.jdt.core.JavaModelException: ticket-monster does not exist > at org.eclipse.jdt.internal.core.JavaElement.newJavaModelException(JavaElement.java:566) > at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:247) > at org.eclipse.jdt.internal.core.JavaElement.openWhenClosed(JavaElement.java:579) > at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:316) > at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:302) > at org.eclipse.jdt.internal.core.JavaProject.getJavaProjectElementInfo(JavaProject.java:1642) > at org.eclipse.jdt.internal.core.JavaProject.newNameLookup(JavaProject.java:2329) > at org.eclipse.jdt.internal.core.JavaProject.newNameLookup(JavaProject.java:2339) > at org.eclipse.jdt.internal.core.JavaProject.findType(JavaProject.java:1357) > at org.eclipse.jdt.internal.core.JavaProject.findType(JavaProject.java:1264) > at org.jboss.tools.arquillian.core.internal.dependencies.DependencyCache.getDependentTypes(DependencyCache.java:116) > at org.jboss.tools.arquillian.core.internal.builder.ArquillianBuilder$1.visit(ArquillianBuilder.java:174) > at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:63) > at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:74) > at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:74) > at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:74) > at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:74) > at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:74) > at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:74) > at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:74) > at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:74) > at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:74) > at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:74) > at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:47) > at org.jboss.tools.arquillian.core.internal.builder.ArquillianBuilder.buildDelta(ArquillianBuilder.java:128) > at org.jboss.tools.arquillian.core.internal.builder.ArquillianBuilder.build(ArquillianBuilder.java:112) > at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:734) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:205) > at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:245) > at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:300) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:303) > at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:359) > at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:382) > at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:144) > at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:235) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {noformat} > Bundles: > | org.eclipse.core.jobs | 3.7.0.v20150330-2103 | 3.8.0.v20160509-0411 | > | org.eclipse.core.runtime | 3.11.1.v20150903-1804 | 3.12.0.v20160606-1342 | > | org.eclipse.jdt.core | 3.11.2.v20160128-0629 | 3.12.0.v20160516-2131 | > | org.jboss.tools.arquillian.core | 1.2.1.Final-v20160331-0142-B69 | 1.2.100.Final-v20160610-0313-B2 | > Operating Systems: > | Linux | 3.16.0 | 4.6.0 | > The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/5741db16e4b0138d62...] for the latest data. > Thank you for your assistance. > Your friendly error-reports-inbox. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22720) ResourceException below ArquillianProjectConfigurator.configureInternal (thrown in Project.checkAccessible)

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22720?page=com.atlassian.jira.plugi... ] Snjezana Peco updated JBIDE-22720: ---------------------------------- Fix Version/s: 4.4.3.Final (was: 4.4.3.AM2) > ResourceException below ArquillianProjectConfigurator.configureInternal (thrown in Project.checkAccessible) > ----------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22720 > URL: https://issues.jboss.org/browse/JBIDE-22720 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: arquillian > Affects Versions: 4.4.0.Final > Reporter: Automated Error Reporting Bot > Assignee: Snjezana Peco > Fix For: 4.4.3.Final > > > The following problem was reported via the automated error reporting: > Message: Resource '/Roentgen-import-service' is not open. > {noformat} > org.eclipse.core.internal.resources.ResourceException: Resource '/Roentgen-import-service' is not open. > at org.eclipse.core.internal.resources.Project.checkAccessible(Project.java:144) > at org.eclipse.core.internal.resources.Project.hasNature(Project.java:516) > at org.jboss.tools.arquillian.maven.configurator.ArquillianProjectConfigurator.configureInternal(ArquillianProjectConfigurator.java:43) > at org.jboss.tools.arquillian.maven.configurator.ArquillianProjectConfigurator.mavenProjectChanged(ArquillianProjectConfigurator.java:72) > at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.mavenProjectChanged(ProjectConfigurationManager.java:1000) > at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.notifyProjectChangeListeners(ProjectRegistryManager.java:783) > at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.applyMutableProjectRegistry(ProjectRegistryManager.java:930) > at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryRefreshJob$1.call(ProjectRegistryRefreshJob.java:98) > at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryRefreshJob$1.call(ProjectRegistryRefreshJob.java:1) > at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176) > at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:151) > at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:99) > at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1355) > at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryRefreshJob.run(ProjectRegistryRefreshJob.java:81) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {noformat} > Bundles: > | org.eclipse.core.jobs | 3.7.0.v20150330-2103 | 3.8.0.v20160319-0610 | > | org.eclipse.core.resources | 3.10.1.v20150725-1910 | 3.11.0.v20160422-0304 | > | org.eclipse.m2e.core | 1.6.3.20160209-1446 | 1.7.0.20160504-0322 | > | org.jboss.tools.arquillian.maven.configurator | 1.2.1.Final-v20160331-0142-B69 | 1.2.1.Final-v20160331-0142-B69 | > Operating Systems: > | MacOSX | 10.11.5 | 10.11.5 | > | Windows | 6.1.0 | 6.3.0 | > The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/5742c4fae4b0138d62...] for the latest data. > Thank you for your assistance. > Your friendly error-reports-inbox. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23734) dedupe vpe unit test jobs / migrate vpe builds to CCI

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23734?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-23734: ------------------------------------- UI tests should be simple unit tests. It doesn't matter that they're UI. If they're just unit tests, then they should run in the unit test job. We do not need a completely new job for this. PR checks should just run unit tests. We need to stop depending on integration tests and make more unit tests wherever possible. If there's a bug in the integration tests, then we need to provide a similar test in unit tests that can also replicate it. There's no need to have 4 different types of jobs. It's ridiculous. I also don't think integration tests need to run daily. I really think that's overkill. If you really want to increase it, I'd say every 3rd day or something. But to have integration tests run daily is ridiculous. Again, if there's issues with failing integration tests, we need to make unit tests that fail similarly. > dedupe vpe unit test jobs / migrate vpe builds to CCI > ----------------------------------------------------- > > Key: JBIDE-23734 > URL: https://issues.jboss.org/browse/JBIDE-23734 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, integration-tests > Affects Versions: 4.4.3.AM1 > Reporter: Nick Boldt > Assignee: Rastislav Wagner > Fix For: 4.4.3.Final > > > There are four VPE unit test jobs. We probably only need 2 of those. > These both run on multiple OSes: > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > These probably run the same unit tests, but against master or 4.4.x branches, and are called from the VPE build jobs [1], [2] on Boston MW Jenkins (because the tests were failing to run in Boston): > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > [1] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-vpe_master/ > [2] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-vpe_4.4.neon/ -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4128) Missing a checkbox for creating a server in New EAP Runtime wizard

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBDS-4128?page=com.atlassian.jira.plugin.... ] Snjezana Peco updated JBDS-4128: -------------------------------- Fix Version/s: 10.3.0.GA (was: 10.3.0.AM2) > Missing a checkbox for creating a server in New EAP Runtime wizard > ------------------------------------------------------------------ > > Key: JBDS-4128 > URL: https://issues.jboss.org/browse/JBDS-4128 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: runtime > Affects Versions: 10.2.0.AM2 > Environment: Red Hat JBoss Developer Studio > Version: 10.2.0.AM2 > Build id: AM2-v20161014-1657-B6205 > Build date: 20161014-1657 > Reporter: Andrej Podhradsky > Assignee: Snjezana Peco > Fix For: 10.3.0.GA > > Attachments: new_server_checkbox.png > > > There is no checkbox for creating a server in New EAP Runtime wizard. > !new_server_checkbox.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20605) configure maven repo has layout issues

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20605?page=com.atlassian.jira.plugi... ] Snjezana Peco updated JBIDE-20605: ---------------------------------- Fix Version/s: 4.4.3.Final (was: 4.4.3.AM2) > configure maven repo has layout issues > -------------------------------------- > > Key: JBIDE-20605 > URL: https://issues.jboss.org/browse/JBIDE-20605 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Reporter: Max Rydahl Andersen > Assignee: Snjezana Peco > Fix For: 4.4.3.Final > > Attachments: Maven_Repositories_and_Attach_Files_ _JBIDE-20605_-_JBoss_Issue_Tracker.png > > > When using quickfix to add red hat maven repo due to openshift examples requiring it I end up with a very bad layout of the UI -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3022) Iintermittent/Recurring Crash of JBDS 7.1.1 - when defining a new server runtime

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBDS-3022?page=com.atlassian.jira.plugin.... ] Snjezana Peco resolved JBDS-3022. --------------------------------- Resolution: Out of Date > Iintermittent/Recurring Crash of JBDS 7.1.1 - when defining a new server runtime > -------------------------------------------------------------------------------- > > Key: JBDS-3022 > URL: https://issues.jboss.org/browse/JBDS-3022 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: runtime-detection, upstream > Affects Versions: 7.1.1.GA, 8.0.0.Beta2 > Environment: uname -a > Linux ldimaggi.csb 2.6.32-431.11.2.el6.x86_64 #1 SMP Mon Mar 3 13:32:45 EST 2014 x86_64 x86_64 x86_64 GNU/Linux > cat /etc/redhat-release > Red Hat Enterprise Linux Workstation release 6.5 (Santiago) > java -version > java version "1.7.0_51" > OpenJDK Runtime Environment (rhel-2.4.4.1.el6_5-x86_64 u51-b02) > OpenJDK 64-Bit Server VM (build 24.45-b08, mixed mode) > Reporter: Len DiMaggio > Assignee: Snjezana Peco > Fix For: 10.3.0.AM2 > > Attachments: Crash.mov, hs_error.log > > > Iintermittent/Recurring Crash of JBDS 7.1.1 - when defining a new server runtime > See attached screencast - crash occurs at the 14 second mark - seeing this 50-80% of the time on one RHEL 6.5 system. > Steps to repeat: > * install JBDS 7.1.1 > jbdevstudio-product-eap-universal-7.1.1.GA-v20140314-2145-B688.jar > -or- > jbdevstudio-product-universal-7.1.1.GA-v20140314-2145-B688.jar > * Create a new server runtime - at the point that Next> is pressed after selecting the runtime version, the crash occurs > * Only seeing this with JBDS - not Eclipse Kepler + JBTools -- 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