March 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-571) Error loading file switchyard.xml. Unable to load the generated resource.

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBTIS-571?page=com.atlassian.jira.plugin.... ] Brian Fitzpatrick commented on JBTIS-571: ----------------------------------------- [~simplex-software] Can you tell me how you are opening the SwitchYard file? Are you double-clicking on the node that appears in the project tree or double-clicking on the switchyard.xml file that's in the src/main/resources directory? I ask because I am looking into this issue now. The workaround seems to be to open the switchyard.xml file directly (drilling into the project tree) and not using the tree node at all, but I'm digging further. > Error loading file switchyard.xml. Unable to load the generated resource. > ------------------------------------------------------------------------- > > Key: JBTIS-571 > URL: https://issues.jboss.org/browse/JBTIS-571 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: switchyard > Affects Versions: 9.0.0.Alpha2 > Reporter: nicolas duminil > Assignee: Brian Fitzpatrick > Priority: Blocker > Fix For: 9.0.0.Beta1 > > Attachments: jbtis-571_1.png, jbtis-571_2.png > > > After creating a new switchyard project, next time it starts up JBDS is not able to open its own generated siwtchyard.xml file. The error "Error loading file switchyard.xml. Unable to load the generated resource" is displayed. The only choice is the OK button. Pressing it, the JBDS screen doesn't display but JBDS seems to be started and the LCK file created. The only option the user has is to kill the process. > Tested on Windows 7 and Windows 10 with Java 8. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21457) Explorer: Show build in explorer deployment view if it any state other then complete

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21457?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21457. --------------------------------- Verified on nightly build of JBT with OpenShift plugin build B227. > Explorer: Show build in explorer deployment view if it any state other then complete > ------------------------------------------------------------------------------------ > > Key: JBIDE-21457 > URL: https://issues.jboss.org/browse/JBIDE-21457 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Labels: openshift_deployment_view > Fix For: 4.3.1.CR1 > > > Display the build in the tree view when it is any non-terminated state ("Complete", "Failed", "Error", "Cancelled"). Expectation is builds should be visible in the tree for a short period of time and then disappear. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21701) Enable port forwarding on a given pod and a given debug port

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21701?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-21701: ----------------------------------- Assignee: Xavier Coulon (was: Fred Bricon) Resolution: Done PR applied in master / 4.3.x. Thanks [~xcoulon]! > Enable port forwarding on a given pod and a given debug port > ------------------------------------------------------------ > > Key: JBIDE-21701 > URL: https://issues.jboss.org/browse/JBIDE-21701 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Fred Bricon > Assignee: Xavier Coulon > Fix For: 4.3.1.CR1 > > > Given a remote debug port, we need to ensure to programmatically enable port forwarding on a pod, return the matching local debug port (named debug). > The local port could be determined as the next available free port, or read from the server adapter's preferences. But that latter case would also require adding some UI to let a user set the local port. That could be done in a later iteration. > If port forwarding is already enabled on the remote pod, then the current local debug port should be returned -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-20719) Updating a token for OpenShift 3 connection via Edit Connection does not update resources

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20719?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-20719. --------------------------------- Verified on nightly build of JBT with OpenShift plugin build B227. > Updating a token for OpenShift 3 connection via Edit Connection does not update resources > ----------------------------------------------------------------------------------------- > > Key: JBIDE-20719 > URL: https://issues.jboss.org/browse/JBIDE-20719 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Fix For: 4.3.1.CR1 > > > If token storage in secure storage expires and new one is required to be able to work with OpenShift 3 connection, then updating token via Edit Connection dialog does not automatically update connection. There is still error tree item under resources saying to obtain a new token. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21881) Updating a token for OpenShift 3 connection via Edit Connection does not update resources

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21881?page=com.atlassian.jira.plugi... ] Marián Labuda resolved JBIDE-21881. ----------------------------------- Resolution: Done > Updating a token for OpenShift 3 connection via Edit Connection does not update resources > ----------------------------------------------------------------------------------------- > > Key: JBIDE-21881 > URL: https://issues.jboss.org/browse/JBIDE-21881 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Fix For: 4.4.0.Alpha1 > > > If token storage in secure storage expires and new one is required to be able to work with OpenShift 3 connection, then updating token via Edit Connection dialog does not automatically update connection. There is still error tree item under resources saying to obtain a new token. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21881) Updating a token for OpenShift 3 connection via Edit Connection does not update resources

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-21881: ------------------------------------- Summary: Updating a token for OpenShift 3 connection via Edit Connection does not update resources Key: JBIDE-21881 URL: https://issues.jboss.org/browse/JBIDE-21881 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Reporter: Marián Labuda Assignee: Viacheslav Kabanovich Fix For: 4.3.1.CR1, 4.4.0.Alpha1 If token storage in secure storage expires and new one is required to be able to work with OpenShift 3 connection, then updating token via Edit Connection dialog does not automatically update connection. There is still error tree item under resources saying to obtain a new token. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-20719) Updating a token for OpenShift 3 connection via Edit Connection does not update resources

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20719?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-20719: ---------------------------------- Fix Version/s: (was: 4.4.0.Alpha1) > Updating a token for OpenShift 3 connection via Edit Connection does not update resources > ----------------------------------------------------------------------------------------- > > Key: JBIDE-20719 > URL: https://issues.jboss.org/browse/JBIDE-20719 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Fix For: 4.3.1.CR1 > > > If token storage in secure storage expires and new one is required to be able to work with OpenShift 3 connection, then updating token via Edit Connection dialog does not automatically update connection. There is still error tree item under resources saying to obtain a new token. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21881) Updating a token for OpenShift 3 connection via Edit Connection does not update resources

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21881?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-21881: ---------------------------------- Fix Version/s: (was: 4.3.1.CR1) > Updating a token for OpenShift 3 connection via Edit Connection does not update resources > ----------------------------------------------------------------------------------------- > > Key: JBIDE-21881 > URL: https://issues.jboss.org/browse/JBIDE-21881 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Fix For: 4.4.0.Alpha1 > > > If token storage in secure storage expires and new one is required to be able to work with OpenShift 3 connection, then updating token via Edit Connection dialog does not automatically update connection. There is still error tree item under resources saying to obtain a new token. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21831) Change host to localhost when cdk is selected in new server dialog

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21831?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-21831. --------------------------------- Verified in today's build of JBDS 9.1.0.CR1. > Change host to localhost when cdk is selected in new server dialog > ------------------------------------------------------------------ > > Key: JBIDE-21831 > URL: https://issues.jboss.org/browse/JBIDE-21831 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.3.1.CR1 > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.3.1.CR1, 4.4.0.Alpha1 > > Attachments: new-cdk-server.png > > > When you open the new server dialog, select OpenShift 2, it will set host to openshift.redhat.com. When you then select cdk, it will complain that it only works on localhost. So the suggestion is to make it work the same way OpenShift adapters work and ensure that host is always changed to localhost when you select the cdk adapter. > This was spotted and brought up by [~mlabuda]. > For reference, this is the JIRA where similar thing was discussed for OpenShift: JBIDE-20114 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3566) include AERI in JBDS 9.1

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3566?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3566: ---------------------------------- Build I used is no longer there, but newer CI builds of JBDS 9.1.0.CR1 are avail: https://devstudio.jboss.com/9.0/snapshots/builds/devstudio.product_9.0.mars/ To test our Neon.M5-based stuff (JBDS 10.0.0.Alpha1), go here: https://devstudio.jboss.com/10.0/snapshots/builds/devstudio.product_master/ > include AERI in JBDS 9.1 > ------------------------ > > Key: JBDS-3566 > URL: https://issues.jboss.org/browse/JBDS-3566 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: aeri, build, target-platform > Affects Versions: 9.1.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 9.1.0.CR1 > > Attachments: aeri-in-jbds91.png, aeri-not-firing.png, error-prefs-jbds.png, error-prefs-jbt.png, error-reporting.png > > > Include required bundles for AERI in JBDS. Details TBD. > Maybe need these? > {code} > org.eclipse.epp.logging.aeri.feature_1.0.1.v20150913-0716 > org.eclipse.epp.logging.aeri.ide_1.0.1.v20150913-0657.jar > org.eclipse.epp.logging.aeri.ui_1.0.1.v20150913-0716.jar > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 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 2016