December 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-21306) "untrusted ssl certificate" dialog ask to Accept or Deny but buttons say No and Yes

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21306?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21306: -------------------------------- Priority: Minor (was: Major) > "untrusted ssl certificate" dialog ask to Accept or Deny but buttons say No and Yes > ----------------------------------------------------------------------------------- > > Key: JBIDE-21306 > URL: https://issues.jboss.org/browse/JBIDE-21306 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Priority: Minor > Fix For: 4.3.1.Beta1 > > > when connecting to CDK I get dialog stating: > Please Accept or Deny the following untrusted SSL certificate" > but the buttons say No Yes. > Either make the title into a question or change the buttons to say Accept / Deny -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21305) Include Docker tooling 1.2.0.Final in TP

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21305?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-21305: ---------------------------------- Description: Please include the 1.2.0 (stable) release of Docker tooling in the target platform from http://download.eclipse.org/linuxtools/update-docker-1.2 (once it's available for download at eclipse.org) in TP 4.50.x and 4.51.x (since consumed by OpenShift tooling) for both JBoss Tools and JBoss Developer Studio (was: Please include the 1.2.0 (stable) release of Docker tooling in the target platform (once it's available for download at eclipse.org). Affected: JBT and JBDS TPs from all three 4.50.x, 4.51.x and 4.60.x branches, as we did last time there was a docker update on Nov 17. ) > Include Docker tooling 1.2.0.Final in TP > ---------------------------------------- > > Key: JBIDE-21305 > URL: https://issues.jboss.org/browse/JBIDE-21305 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: target-platform > Affects Versions: 4.3.0.Beta1 > Reporter: Xavier Coulon > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1 > > > Please include the 1.2.0 (stable) release of Docker tooling in the target platform from http://download.eclipse.org/linuxtools/update-docker-1.2 (once it's available for download at eclipse.org) in TP 4.50.x and 4.51.x (since consumed by OpenShift tooling) for both JBoss Tools and JBoss Developer Studio -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20923) Wrong archetype is picked for unreleased EAP (7)

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20923?page=com.atlassian.jira.plugi... ] Fred Bricon resolved JBIDE-20923. --------------------------------- Resolution: Done Fixed in master/4.3.x. EAP 7 will now pick up the JavaEE 7 archetypes > Wrong archetype is picked for unreleased EAP (7) > ------------------------------------------------ > > Key: JBIDE-20923 > URL: https://issues.jboss.org/browse/JBIDE-20923 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.3.0.Final > Reporter: Radim Hopp > Assignee: Fred Bricon > Fix For: 4.3.1.Beta1 > > > When EAP 7 is selected as target runtime when creating project from archetype (EAR Project for example), version org.jboss.spec.archetypes:jboss-javaee6-webapp-ear-archetype:7.1.3.Final is selected (JBoss AS 7.1 archetype). > Instead of this, either last released EAP version (currently 6.4) archetype should be selected, or the "most compatible" (at this time probably WFLY 8.2 archetype) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21305) Include Docker tooling 1.2.0.Final in TP

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21305?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-21305: ------------------------------- Description: Please include the 1.2.0 (stable) release of Docker tooling in the target platform (once it's available for download at eclipse.org). Affected: JBT and JBDS TPs from all three 4.50.x, 4.51.x and 4.60.x branches, as we did last time there was a docker update on Nov 17. was: Please include the 1.2.0 (stable) release of Docker tooling in the target platform (once it's available for download at eclipse.org). Affected: JBT and JBDS TPs from both 4.50.x and 4.51.x branches, as we did last time there was a docker update on Nov 17. > Include Docker tooling 1.2.0.Final in TP > ---------------------------------------- > > Key: JBIDE-21305 > URL: https://issues.jboss.org/browse/JBIDE-21305 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: target-platform > Affects Versions: 4.3.0.Beta1 > Reporter: Xavier Coulon > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1 > > > Please include the 1.2.0 (stable) release of Docker tooling in the target platform (once it's available for download at eclipse.org). > Affected: JBT and JBDS TPs from all three 4.50.x, 4.51.x and 4.60.x branches, as we did last time there was a docker update on Nov 17. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21305) Include Docker tooling 1.2.0.Final in TP

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21305?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-21305: ------------------------------- Description: Please include the 1.2.0 (stable) release of Docker tooling in the target platform (once it's available for download at eclipse.org). Affected: JBT and JBDS TPs from both 4.50.x and 4.51.x branches, as we did last time there was a docker update on Nov 17. was:Please include the 1.2.0 (stable) release of Docker tooling in the target platform (once it's available for download at eclipse.org) > Include Docker tooling 1.2.0.Final in TP > ---------------------------------------- > > Key: JBIDE-21305 > URL: https://issues.jboss.org/browse/JBIDE-21305 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: target-platform > Affects Versions: 4.3.0.Beta1 > Reporter: Xavier Coulon > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1 > > > Please include the 1.2.0 (stable) release of Docker tooling in the target platform (once it's available for download at eclipse.org). > Affected: JBT and JBDS TPs from both 4.50.x and 4.51.x branches, as we did last time there was a docker update on Nov 17. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21306) "untrusted ssl certificate" dialog ask to Accept or Deny but buttons say No and Yes

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21306?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21306: -------------------------------- Fix Version/s: 4.3.1.Beta1 > "untrusted ssl certificate" dialog ask to Accept or Deny but buttons say No and Yes > ----------------------------------------------------------------------------------- > > Key: JBIDE-21306 > URL: https://issues.jboss.org/browse/JBIDE-21306 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Fix For: 4.3.1.Beta1 > > > when connecting to CDK I get dialog stating: > Please Accept or Deny the following untrusted SSL certificate" > but the buttons say No Yes. > Either make the title into a question or change the buttons to say Accept / Deny -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21306) "untrusted ssl certificate" dialog ask to Accept or Deny but buttons say No and Yes

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21306?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-21306: ----------------------------------- Assignee: Fred Bricon > "untrusted ssl certificate" dialog ask to Accept or Deny but buttons say No and Yes > ----------------------------------------------------------------------------------- > > Key: JBIDE-21306 > URL: https://issues.jboss.org/browse/JBIDE-21306 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Fix For: 4.3.1.Beta1 > > > when connecting to CDK I get dialog stating: > Please Accept or Deny the following untrusted SSL certificate" > but the buttons say No Yes. > Either make the title into a question or change the buttons to say Accept / Deny -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21290) CDK 2 is detected as version 1.0

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21290?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-21290: ------------------------------------- Perhaps we can get this added to the .cdk file. Then it can be more accurate, and my handler can pull from there. > CDK 2 is detected as version 1.0 > -------------------------------- > > Key: JBIDE-21290 > URL: https://issues.jboss.org/browse/JBIDE-21290 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Minor > Attachments: cdk-runtime-detection.png > > > When you detect CDK using runtime detection, it will show you the name cdk-v2 which clearly shows it's version 2 (this is actually just based on the folder it seems). But the Version column says Version 1.0. > !cdk-runtime-detection.png! > Could we change it to version 2? > I know that this probably doesn't have any meaning right now - I noticed there is no runtime anymore, so the version is nowhere to be seen once you create the cdk server adapter. But it would still be nicer to show the correct version if possible. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21193) runtime detection detects *any* folder as a CDK and jboss multiple times

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21193?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-21193: ------------------------------------- > I don't really see why the cdk runtime detector doesn't ignore the paths that don't have a .cdk marker. It does now. I was missing the call to validate a second time. I had mistakenly believed the handler would only be asked to instantiate detected cdk runtimedefinitions, not all runtime definitions. So now it re-validates. Was a small mistake / 1 line fix. > runtime detection detects *any* folder as a CDK and jboss multiple times > ------------------------------------------------------------------------ > > Key: JBIDE-21193 > URL: https://issues.jboss.org/browse/JBIDE-21193 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.3.1.Beta1 > > Attachments: Java_EE_-_jboss-eap-6_1_CDK_Server_-_Eclipse.png > > > with build from last week I now get this list of runtime detected in my folder of servers. > At first I thought it was the CDK being weird but something is also very weird about the basic runtime detection since I seem to have multiple WildFly 8.0's...as opposed to using the folder name. > Here is the content of my folder > {code} > apache-karaf-2.3.5 > apache-tomcat-7.0.35 > app.js > app.js.1 > fsw-6 > jboss as 7 > jboss-5.1.0.GA > jboss-as-7.0.1.Final > jboss-as-7.1.0.Final > jboss-as-7.1.1.Final > jboss-as-web-7.0.0.Final > jboss-as-web-7.0.2.Final > jboss-eap-6.0.1 > jboss-eap-6.1 > weld-1.1.0.Final > weld-1.1.5.Final > wildfly-10.0.0.CR4 > wildfly-8.0.0.Beta1 > wildfly-8.0.0.Final > wildfly-8.1.0.Final > wildfly-8.2.0 > wildfly-core-8.0.0.Final > {code} > and attached is the list I get. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21202) Central is stuck on "Loading JBoss Central" when offline

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21202?page=com.atlassian.jira.plugi... ] Fred Bricon resolved JBIDE-21202. --------------------------------- Resolution: Done Fixed in master/4.3.x > Central is stuck on "Loading JBoss Central" when offline > -------------------------------------------------------- > > Key: JBIDE-21202 > URL: https://issues.jboss.org/browse/JBIDE-21202 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.3.1.Beta1 > Environment: JBDS 9.1.0.Beta1-v20151208-1226-B169 > Reporter: Radim Hopp > Assignee: Fred Bricon > Priority: Blocker > Fix For: 4.3.1.Beta1 > > > When started without internet access, Central is stuck on "Loading JBoss Central, please wait..." and error pops up: > {noformat} > Unable to open /resources/jbosstools-central-webpage.zip > Can't find embedded central zip > {noformat} > even though studio/plugins/org.jboss.tools.central_2.0.1.Beta1-v20151116-2016-B57/resources/jbosstools-central-webpage.zip is present on file system. > In JBDS 9.0.0.GA Central can be loaded without issues when offline. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 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 December 2015