August 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (ERT-378) [JS Debugger] Need to prevent "Choose Tab for Debugging" dialog appearing [EBZ#499579]

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/ERT-378?page=com.atlassian.jira.plugin.sy... ] Ilya Buziuk resolved ERT-378. ----------------------------- Resolution: Done > [JS Debugger] Need to prevent "Choose Tab for Debugging" dialog appearing [EBZ#499579] > -------------------------------------------------------------------------------------- > > Key: ERT-378 > URL: https://issues.jboss.org/browse/ERT-378 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Assignee: Ilya Buziuk > Labels: Debug, bzira > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-841) Please update JBoss Tools website features desc - Data Virt

by Paul Leacu (JIRA)

Paul Leacu created JBTIS-841: -------------------------------- Summary: Please update JBoss Tools website features desc - Data Virt Key: JBTIS-841 URL: https://issues.jboss.org/browse/JBTIS-841 Project: JBoss Tools Integration Stack Issue Type: Task Components: teiid Reporter: Paul Leacu Assignee: Barry LaFond http://tools.jboss.org/features/teiiddesigner.html The git source repo for the content can be found here: https://github.com/jbosstools/jbosstools-website/tree/master/features I'm happy to coordinate updating the repo if you'd like. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-840) Please update JBoss Tools website features desc - B*MS Tooling

by Paul Leacu (JIRA)

Paul Leacu created JBTIS-840: -------------------------------- Summary: Please update JBoss Tools website features desc - B*MS Tooling Key: JBTIS-840 URL: https://issues.jboss.org/browse/JBTIS-840 Project: JBoss Tools Integration Stack Issue Type: Task Components: BPEL, BPMN2, drools/ jBPM Reporter: Paul Leacu Assignee: Robert (Bob) Brodt http://tools.jboss.org/features/bpel.html http://tools.jboss.org/features/bpmn2.html http://tools.jboss.org/features/drools.html http://tools.jboss.org/features/jbpm.html The git source repo for the content can be found here: https://github.com/jbosstools/jbosstools-website/tree/master/features I'm happy to coordinate updating the repo if you'd like. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-839) Please update JBoss Tools website features desc - Fuse Tooling/SY/Fabric8

by Paul Leacu (JIRA)

Paul Leacu created JBTIS-839: -------------------------------- Summary: Please update JBoss Tools website features desc - Fuse Tooling/SY/Fabric8 Key: JBTIS-839 URL: https://issues.jboss.org/browse/JBTIS-839 Project: JBoss Tools Integration Stack Issue Type: Task Components: Fuse IDE Reporter: Paul Leacu Assignee: Lars Heinemann http://tools.jboss.org/features/apachecamel.html http://tools.jboss.org/features/fabric8.html http://tools.jboss.org/features/switchyard.html The git source repo for the content can be found here: https://github.com/jbosstools/jbosstools-website/tree/master/features I'm happy to coordinate updating the repo if you'd like. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-837) JBTIS Target Platform - Neon - sync with JBT 4.4.1.AM3

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-837?page=com.atlassian.jira.plugin.... ] Paul Leacu updated JBTIS-837: ----------------------------- Description: *Reason:* Sync w/ 4.4.1.AM3 *Project page/sources:* *Version:* .4.4.0.Alpha2 *License and owner:* EPL *Original p2 repo:* *JBoss mirror:* *Include Sources:* Yes *Affected JBoss Tools components:* IS *Include in JBDS:* Yes (IS) *Type of dependency:* distribution *List of bundles added/removed:* {code} {code} was:Sync w/ 4.4.1.AM3 > JBTIS Target Platform - Neon - sync with JBT 4.4.1.AM3 > ------------------------------------------------------ > > Key: JBTIS-837 > URL: https://issues.jboss.org/browse/JBTIS-837 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: target-platform > Affects Versions: 4.4.0.Alpha1-TP > Reporter: Paul Leacu > Assignee: Paul Leacu > > *Reason:* Sync w/ 4.4.1.AM3 > *Project page/sources:* > *Version:* .4.4.0.Alpha2 > *License and owner:* EPL > *Original p2 repo:* > *JBoss mirror:* > *Include Sources:* Yes > *Affected JBoss Tools components:* IS > *Include in JBDS:* Yes (IS) > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22969) Make sure OpenShift Tools support proxies

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22969?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov edited comment on JBIDE-22969 at 8/18/16 1:14 PM: ------------------------------------------------------------------- [~akazakov] [~mlabuda] , please, have a look. Am i doing something wrong? Or it is bugs? Tried on Fedora 24. Used [cdk-2.2 nightly build from August 17|http://cdk-builds.usersys.redhat.com/builds/nightly/17-Aug-2016/] 1) I did the following from the [Eclipse Proxy Testing|https://mojo.redhat.com/docs/DOC-989982] description: {code:bash} sudo iptables -P OUTPUT DROP sudo iptables -A OUTPUT -p udp -j ACCEPT sudo iptables -A OUTPUT -p tcp --destination-port 3128 --destination 10.38.5.41 -j ACCEPT {code} Then i tried _*vagrant up*_ from the terminal. It hangs on the _*==> default: Waiting for SSH to become available...*_. As soon as i _*sudo iptables -P OUTPUT ACCEPT*_, it immediately continues starting up 2) I set up proxy settings in Eclipse preferences: [^proxy_settings.png] + {code:bash} sudo iptables -P OUTPUT DROP sudo iptables -A OUTPUT -p udp -j ACCEPT sudo iptables -A OUTPUT -p tcp --destination-port 3128 --destination 10.38.5.41 -j ACCEPT {code} and tried to start the cdk from the Eclipse Servers view. Nor OS connection, neither Docker connection created with the following Error pop-up: {noformat} Unable to configure docker and openshift. Calls to vagrant service-manager are returning empty environments. {noformat} But when i do _*sudo iptables -P OUTPUT ACCEPT*_ connections are created in a usual way, even if i leave proxy settings in Eclipse tuned to http://10.38.5.41:3128/ was (Author: dbocharov): [~akazakov] [~mlabuda] , please, have a look. Am i doing something wrong? Or it is bugs? Tried on Fedora 24. Used [cdk-2.2 nightly build from August 17|http://cdk-builds.usersys.redhat.com/builds/nightly/17-Aug-2016/] 1) I did the following from the [Eclipse Proxy Testing|https://mojo.redhat.com/docs/DOC-989982] description: {code:bash} sudo iptables -P OUTPUT DROP sudo iptables -A OUTPUT -p udp -j ACCEPT sudo iptables -A OUTPUT -p tcp --destination-port 3128 --destination 10.38.5.41 -j ACCEPT {code} Then i tried _*vagrant up*_. It hangs on the _*==> default: Waiting for SSH to become available...*_. As soon as i _*sudo iptables -P OUTPUT ACCEPT*_, it immediately continues starting up 2) I set up proxy settings in Eclipse preferences: [^proxy_settings.png] + {code:bash} sudo iptables -P OUTPUT DROP sudo iptables -A OUTPUT -p udp -j ACCEPT sudo iptables -A OUTPUT -p tcp --destination-port 3128 --destination 10.38.5.41 -j ACCEPT {code} and tried to start the cdk. Nor OS connection, neither Docker connection created with the following Error pop-up: {noformat} Unable to configure docker and openshift. Calls to vagrant service-manager are returning empty environments. {noformat} But when i do _*sudo iptables -P OUTPUT ACCEPT*_ connections are created in a usual way, even if i leave proxy settings in Eclipse tuned to http://10.38.5.41:3128/ > Make sure OpenShift Tools support proxies > ----------------------------------------- > > Key: JBIDE-22969 > URL: https://issues.jboss.org/browse/JBIDE-22969 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Reporter: Alexey Kazakov > Assignee: Dmitrii Bocharov > Fix For: 4.4.1.Final > > Attachments: proxy_settings.png > > > CDK is now support proxy servers. We also should make sure OpenShift Tools works fine with proxies too. > If devstudio and cdk are installed using DevSuite installer and user configured proxy server correctly then everything should just work on Eclipse side. > This issue covers: > - testing > - creating all needed (currently missing) automated tests (including reddeer/swt bot Integration Tests) > - fixing any problems we have in OpenShift tooling regarding proxy support. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22969) Make sure OpenShift Tools support proxies

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22969?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-22969: ------------------------------------- Attachment: proxy_settings.png [~akazakov] [~mlabuda] , please, have a look. Am i doing something wrong? Or it is bugs? Tried on Fedora 24. Used [cdk-2.2 nightly build from August 17|http://cdk-builds.usersys.redhat.com/builds/nightly/17-Aug-2016/] 1) I did the following from the [Eclipse Proxy Testing|https://mojo.redhat.com/docs/DOC-989982] description: {code:bash} sudo iptables -P OUTPUT DROP sudo iptables -A OUTPUT -p udp -j ACCEPT sudo iptables -A OUTPUT -p tcp --destination-port 3128 --destination 10.38.5.41 -j ACCEPT {code} Then i tried _*vagrant up*_. It hangs on the _*==> default: Waiting for SSH to become available...*_. As soon as i _*sudo iptables -P OUTPUT ACCEPT*_, it immediately continues starting up 2) I set up proxy settings in Eclipse preferences: [^proxy_settings.png] + {code:bash} sudo iptables -P OUTPUT DROP sudo iptables -A OUTPUT -p udp -j ACCEPT sudo iptables -A OUTPUT -p tcp --destination-port 3128 --destination 10.38.5.41 -j ACCEPT {code} and tried to start the cdk. Nor OS connection, neither Docker connection created with the following Error pop-up: {noformat} Unable to configure docker and openshift. Calls to vagrant service-manager are returning empty environments. {noformat} But when i do _*sudo iptables -P OUTPUT ACCEPT*_ connections are created in a usual way, even if i leave proxy settings in Eclipse tuned to http://10.38.5.41:3128/ > Make sure OpenShift Tools support proxies > ----------------------------------------- > > Key: JBIDE-22969 > URL: https://issues.jboss.org/browse/JBIDE-22969 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Reporter: Alexey Kazakov > Assignee: Dmitrii Bocharov > Fix For: 4.4.1.Final > > Attachments: proxy_settings.png > > > CDK is now support proxy servers. We also should make sure OpenShift Tools works fine with proxies too. > If devstudio and cdk are installed using DevSuite installer and user configured proxy server correctly then everything should just work on Eclipse side. > This issue covers: > - testing > - creating all needed (currently missing) automated tests (including reddeer/swt bot Integration Tests) > - fixing any problems we have in OpenShift tooling regarding proxy support. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ERT-398) Deselected connection after deleted tag [EBZ#499919]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-398: --------------------------------------- Summary: Deselected connection after deleted tag [EBZ#499919] Key: ERT-398 URL: https://issues.jboss.org/browse/ERT-398 Project: Eclipse Release Train Issue Type: Task Components: Linux Tools Reporter: Friendly Jira Robot Priority: Minor Steps to reproduce: 1. Pull any image. 2. Add tag to this image. 3. Click on added tag in Docker Explorer. 4. Delete in Docker Images tab this newly created tag. 5. Tag is deleted, but connection is deselected, so the Docker Images tab is empty. I suggest in this case to select connection or images in Docker explorer. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22326) Enable JMX Connections Over "remoting-jmx"

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22326?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-22326: ------------------------------------- [~fbricon] What exactly are you thinking here? As of now, we use a local jboss / wf / eap runtime to locate the remoting-jmx and client jars. If you're considering bundling these somehow, we really need to discuss architecture before just running in and coding something. Also we must remember that openshift can hold several versions of as / wf / eap, and so fi we plan on bundling the jars, we need to be very careful how we do it. Also note that any change to how openshift server adapter connects to remote jmx may also apply to our standard jboss / wf / eap server adapters. > Enable JMX Connections Over "remoting-jmx" > ------------------------------------------ > > Key: JBIDE-22326 > URL: https://issues.jboss.org/browse/JBIDE-22326 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: jmx > Reporter: Thomas Mäder > Assignee: Fred Bricon > Fix For: 4.4.1.Final > > > Need to add "remoting-jmx" library and support that kind of connection for jmx -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23008) openshift.cdk.feature.source missing from JBT site; causes baseline check to fail

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23008?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-23008 at 8/18/16 12:12 PM: -------------------------------------------------------------- {quote} The main artifact has been replaced with the baseline version. The following attached artifacts are not present in the baseline and have been removed: [sources]{quote} The openshift.cdk.feature.source is NOT IN the baseline site (we forgot to add the source feature) so Tycho is removing the source feature from the reactor. And it's using the old version of the "main artifact", openshift.cdk.feature. I wonder if the replacement is happening because we used a SNAPSHOT dependency (openshift-restclient jar) inside the openshift.client plugin (which is in the openshift.feature, which is in the openshift.cdk.feature), so Tycho things the cdk.feature is the same (sources unchanged), but it's not (nested binary has changed). So, yes, we need to bump the features... and also org.jboss.tools.openshift.cdk.server. PR: https://github.com/jbosstools/jbosstools-openshift/pull/1288 was (Author: nickboldt): {quote} The main artifact has been replaced with the baseline version. The following attached artifacts are not present in the baseline and have been removed: [sources]{quote} The openshift.cdk.feature.source is NOT IN the baseline site (we forgot to add the source feature) so Tycho is removing the source feature from the reactor. And it's using the old version of the "main artifact", openshift.cdk.feature. I wonder if the replacement is happening because we used a SNAPSHOT dependency (openshift-restclient jar) inside the openshift.client plugin (which is in the openshift.feature, which is in the openshift.cdk.feature), so Tycho things the cdk.feature is the same (sources unchanged), but it's not (nested binary has changed). So, yes, we need to bump the feature. PR: https://github.com/jbosstools/jbosstools-openshift/pull/1288 > openshift.cdk.feature.source missing from JBT site; causes baseline check to fail > --------------------------------------------------------------------------------- > > Key: JBIDE-23008 > URL: https://issues.jboss.org/browse/JBIDE-23008 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, openshift, updatesite > Affects Versions: 4.4.1.AM3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.1.Final > > > Since the weekend (after I published an AM3 build into /neon/staging/updates/): > {code} > [INFO] --- tycho-source-plugin:0.25.0:plugin-source (plugin-source) @ org.jboss.tools.openshift.cdk.server --- > [INFO] Building jar: /Users/fbricon/Dev/projects/jbosstools-openshift/plugins/org.jboss.tools.openshift.cdk.server/target/org.jboss.tools.openshift.cdk.server-3.3.0-SNAPSHOT-sources.jar > [INFO] > [INFO] --- target-platform-configuration:0.25.0:target-platform (default-target-platform) @ org.jboss.tools.openshift.cdk.server --- > [INFO] > [INFO] --- tycho-packaging-plugin:0.25.0:package-plugin (default-package-plugin) @ org.jboss.tools.openshift.cdk.server --- > [INFO] Building jar: /Users/fbricon/Dev/projects/jbosstools-openshift/plugins/org.jboss.tools.openshift.cdk.server/target/org.jboss.tools.openshift.cdk.server-3.3.0-SNAPSHOT.jar > [INFO] > [INFO] --- tycho-p2-plugin:0.25.0:p2-metadata-default (default-p2-metadata-default) @ org.jboss.tools.openshift.cdk.server --- > [WARNING] MavenProject: org.jboss.tools.openshift.plugins:org.jboss.tools.openshift.cdk.server:3.3.0-SNAPSHOT @ /Users/fbricon/Dev/projects/jbosstools-openshift/plugins/org.jboss.tools.openshift.cdk.server/pom.xml: baseline and build artifacts have same version but different contents > [INFO] MavenProject: org.jboss.tools.openshift.plugins:org.jboss.tools.openshift.cdk.server:3.3.0-SNAPSHOT @ /Users/fbricon/Dev/projects/jbosstools-openshift/plugins/org.jboss.tools.openshift.cdk.server/pom.xml > The main artifact has been replaced with the baseline version. > The following attached artifacts are not present in the baseline and have been removed: [sources]{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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