March 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (ERT-493) "org.eclipse.wst.jsdt.js.node" is requiring "org.eclipse.wst.jsdt.chromium.debug.core" version 0.4.0, and this is not into 4.6.2 build [EBZ#513341]

by Victor Rubezhny (JIRA)

[ https://issues.jboss.org/browse/ERT-493?page=com.atlassian.jira.plugin.sy... ] Victor Rubezhny reassigned ERT-493: ----------------------------------- Assignee: Victor Rubezhny > "org.eclipse.wst.jsdt.js.node" is requiring "org.eclipse.wst.jsdt.chromium.debug.core" version 0.4.0, and this is not into 4.6.2 build [EBZ#513341] > --------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: ERT-493 > URL: https://issues.jboss.org/browse/ERT-493 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Assignee: Victor Rubezhny > Labels: Debug, bzira > > Bundle "org.eclipse.wst.jsdt.js.node 1.0.0.v201608102114" requires exactly bundle "org.eclipse.wst.jsdt.chromium.debug.core" version 0.4.0, but this is not in the 4.6.2 GA build, the available version of this bundle into the 4.6.2 build is "0.5.0". > See the MANIFEST: > Manifest-Version: 1.0 > Bundle-SymbolicName: org.eclipse.wst.jsdt.js.node;singleton:=true > Archiver-Version: Plexus Archiver > Built-By: genie.webtools > Require-Bundle: org.eclipse.ui,org.eclipse.core.runtime,org.eclipse.co > re.resources;bundle-version="[3.10.1,4.0.0)",org.eclipse.wst.jsdt.js. > common,org.eclipse.wst.jsdt.core,org.eclipse.debug.ui,org.eclipse.ui. > ide;bundle-version="[3.11.0,4.0.0)",org.eclipse.core.variables,org.ec > lipse.core.expressions,com.google.gson;bundle-version="[2.2.4,3.0.0)" > ,org.eclipse.wst.jsdt.js.node.common,org.eclipse.debug.core,org.eclip > se.wst.jsdt.chromium.debug.core;bundle-version="0.4.0",org.eclipse.ws > t.jsdt.chromium;bundle-version="0.4.0",org.eclipse.wst.jsdt.chromium. > debug;bundle-version="0.4.0",org.eclipse.wst.jsdt.chromium.debug.ui;b > undle-version="[0.6.0,0.7.0)" -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-23136) Deploy Docker Wizard: Pushing image to CDK registry results in an image with no tag

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23136?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-23136: ------------------------------------- Sprint: devex #123 November 2016, devex #129 March 2017 (was: devex #123 November 2016, devex #128 February 2017) > Deploy Docker Wizard: Pushing image to CDK registry results in an image with no tag > ----------------------------------------------------------------------------------- > > Key: JBIDE-23136 > URL: https://issues.jboss.org/browse/JBIDE-23136 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.Final > Reporter: Marián Labuda > Assignee: Dmitrii Bocharov > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.4.4.AM2 > > Attachments: FedoraImageStream.png, ImagesWithDigest.png, eap64-basic-s2i-new-app-from-cli-1.png, eap64-basic-s2i-new-app-from-jbosstools-1.png, local-docker-images-after-pull-1.png > > > I have a docker connection to local docker daemon and a CDK docker connection. I am pushing an image from a docker connection to CDK registry via Deploy Image to OpenShift wizard. Push of an image pass, but it results into an image with no tag, see: > 172.30.192.49:5000/msa/msa <none> 238200ae067d 4 months ago 1.05 GB > Such images are not shown in docker explorer under a docker connection because of upstream bug ERT-411 > Steps to reproduce: > - have a project with a file named {{Dockerfile}} with the following content (1 line): > {code} > FROM fedora:latest > {code} > - Select the file in the project explorer, then {{Run As > Docker Image Build}}. Use the CDK connection and give it a name (eg: {{username/fedora}}) > - Select the image in the Docker Explorer view, then {{Deploy to OpenShift}}. > - In the wizard, select the option to push the image to the registry (add a dummy port if needed) > - once the operation completed, there's an unexpected image named like {{172.30.164.33:5000/<project>/fedora}} in the output of the {{docker images}} command (in CLI) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-23494) Tests: Should provide unit-tests for WatchManager

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23494?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-23494: ------------------------------------- Sprint: devex #129 March 2017 (was: devex #128 February 2017) > Tests: Should provide unit-tests for WatchManager > ------------------------------------------------- > > Key: JBIDE-23494 > URL: https://issues.jboss.org/browse/JBIDE-23494 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.2.AM3 > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Priority: Critical > Fix For: 4.5.0.AM1 > > > WatchManager proved to be a complex and sensitive component and thus it is highly required to have unit-tests for it. I'll jira -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-23900) Refactor OpenShift server adapter to isolate EAP/Wildfly and NodeJS specific stuff

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23900?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-23900: ------------------------------------- Sprint: devex #129 March 2017 (was: devex #128 February 2017) > Refactor OpenShift server adapter to isolate EAP/Wildfly and NodeJS specific stuff > ---------------------------------------------------------------------------------- > > Key: JBIDE-23900 > URL: https://issues.jboss.org/browse/JBIDE-23900 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.3.Final > Reporter: Jeff MAURY > Assignee: Dmitrii Bocharov > Fix For: 4.4.4.AM2 > > > We should isolate EAP/Wildfly and NodeJS specific stuff for the server adapter into separate classes / extensions > We should also provide a mechanism for the sever adapter to be stack agnostic so that we can add more stacks by just addding an extension > This will be probably required by FUSE integration -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-23731) Integration tests: move hibernate integration tests to jbosstools/jbosstools-hibernate repo

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23731?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov closed JBIDE-23731. ------------------------------------ Resolution: Duplicate Issue duplicate of JBIDE-23824 > Integration tests: move hibernate integration tests to jbosstools/jbosstools-hibernate repo > ------------------------------------------------------------------------------------------- > > Key: JBIDE-23731 > URL: https://issues.jboss.org/browse/JBIDE-23731 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, integration-tests > Affects Versions: 4.4.2.Final > Reporter: Dmitrii Bocharov > Assignee: Dmitrii Bocharov > Fix For: 4.4.4.AM1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-24077) NullPointerException in ProjectUtils.availablePersistenceUnits

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24077?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-24077: ------------------------------ Affects Version/s: 4.4.3.Final > NullPointerException in ProjectUtils.availablePersistenceUnits > -------------------------------------------------------------- > > Key: JBIDE-24077 > URL: https://issues.jboss.org/browse/JBIDE-24077 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.4.3.Final > Reporter: Automated Error Reporting Bot > Assignee: Koen Aers > Fix For: 4.4.4.AM2, 4.5.0.AM1 > > > The following problem was reported via the automated error reporting: > Message: Unhandled event loop exception > java.lang.NullPointerException: null > at org.hibernate.eclipse.console.utils.ProjectUtils.availablePersistenceUnits(ProjectUtils.java:402) > at org.hibernate.eclipse.console.utils.DialogSelectionHelper.choosePersistenceUnit(DialogSelectionHelper.java:94) > at org.hibernate.eclipse.launch.ConsoleConfigurationMainTab.handlePersistenceUnitBrowse(ConsoleConfigurationMainTab.java:292) > at org.hibernate.eclipse.launch.ConsoleConfigurationMainTab.access$3(ConsoleConfigurationMainTab.java:291) > at org.hibernate.eclipse.launch.ConsoleConfigurationMainTab$5.widgetSelected(ConsoleConfigurationMainTab.java:189) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > Bundles: > | org.eclipse.swt | 3.105.0.v20160603-0902 | 3.105.1.v20160907-0248 | > | org.hibernate.eclipse | 5.1.1.v20160613-0605 | 5.1.2.v20161111-1418 | > | org.hibernate.eclipse.console | 5.1.1.v20160730-1423 | 5.1.2.v20161116-1036 | > Operating Systems: > | Linux | 2.6.32.11 | 2.6.32.11 | > | Windows | 6.1.0 | 10.0.0 | > The above information is a snapshot of the collected data. Visit https://aer.ctrlflow.com/redhat/reviewers/#!/problems/571e114be4b08bd809c... 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-24077) NullPointerException in ProjectUtils.availablePersistenceUnits

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24077?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-24077: ------------------------------ Fix Version/s: 4.4.4.AM2 4.5.0.AM1 > NullPointerException in ProjectUtils.availablePersistenceUnits > -------------------------------------------------------------- > > Key: JBIDE-24077 > URL: https://issues.jboss.org/browse/JBIDE-24077 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.4.3.Final > Reporter: Automated Error Reporting Bot > Assignee: Koen Aers > Fix For: 4.4.4.AM2, 4.5.0.AM1 > > > The following problem was reported via the automated error reporting: > Message: Unhandled event loop exception > java.lang.NullPointerException: null > at org.hibernate.eclipse.console.utils.ProjectUtils.availablePersistenceUnits(ProjectUtils.java:402) > at org.hibernate.eclipse.console.utils.DialogSelectionHelper.choosePersistenceUnit(DialogSelectionHelper.java:94) > at org.hibernate.eclipse.launch.ConsoleConfigurationMainTab.handlePersistenceUnitBrowse(ConsoleConfigurationMainTab.java:292) > at org.hibernate.eclipse.launch.ConsoleConfigurationMainTab.access$3(ConsoleConfigurationMainTab.java:291) > at org.hibernate.eclipse.launch.ConsoleConfigurationMainTab$5.widgetSelected(ConsoleConfigurationMainTab.java:189) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > Bundles: > | org.eclipse.swt | 3.105.0.v20160603-0902 | 3.105.1.v20160907-0248 | > | org.hibernate.eclipse | 5.1.1.v20160613-0605 | 5.1.2.v20161111-1418 | > | org.hibernate.eclipse.console | 5.1.1.v20160730-1423 | 5.1.2.v20161116-1036 | > Operating Systems: > | Linux | 2.6.32.11 | 2.6.32.11 | > | Windows | 6.1.0 | 10.0.0 | > The above information is a snapshot of the collected data. Visit https://aer.ctrlflow.com/redhat/reviewers/#!/problems/571e114be4b08bd809c... 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-23055) Repeated toggling of JAX-RS support on project does not cause it to rebuild

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23055?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23055: ------------------------------- Fix Version/s: 4.4.4.AM2 (was: 4.4.x) > Repeated toggling of JAX-RS support on project does not cause it to rebuild > --------------------------------------------------------------------------- > > Key: JBIDE-23055 > URL: https://issues.jboss.org/browse/JBIDE-23055 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.4.1.AM3 > Reporter: Jan Richter > Assignee: Jeff MAURY > Fix For: 4.4.4.AM2 > > > When JAX-RS support is toggled in a project's preferences, clicking Apply will rebuild the project and JAX-RS services will (dis)/appear and validation is enabled/disabled. > But if without closing the preferences I toggle JAX-RS support again and press Apply, nothing happens - the project is not built with the new settings. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-23055) Repeated toggling of JAX-RS support on project does not cause it to rebuild

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23055?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23055: ------------------------------- Sprint: devex #129 March 2017 > Repeated toggling of JAX-RS support on project does not cause it to rebuild > --------------------------------------------------------------------------- > > Key: JBIDE-23055 > URL: https://issues.jboss.org/browse/JBIDE-23055 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.4.1.AM3 > Reporter: Jan Richter > Assignee: Jeff MAURY > Fix For: 4.4.4.AM2 > > > When JAX-RS support is toggled in a project's preferences, clicking Apply will rebuild the project and JAX-RS services will (dis)/appear and validation is enabled/disabled. > But if without closing the preferences I toggle JAX-RS support again and press Apply, nothing happens - the project is not built with the new settings. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-23055) Repeated toggling of JAX-RS support on project does not cause it to rebuild

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23055?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-23055: ---------------------------------- Assignee: Jeff MAURY (was: Xavier Coulon) > Repeated toggling of JAX-RS support on project does not cause it to rebuild > --------------------------------------------------------------------------- > > Key: JBIDE-23055 > URL: https://issues.jboss.org/browse/JBIDE-23055 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.4.1.AM3 > Reporter: Jan Richter > Assignee: Jeff MAURY > Fix For: 4.4.x > > > When JAX-RS support is toggled in a project's preferences, clicking Apply will rebuild the project and JAX-RS services will (dis)/appear and validation is enabled/disabled. > But if without closing the preferences I toggle JAX-RS support again and press Apply, nothing happens - the project is not built with the new settings. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 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 2017