December 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-21369) Project Manager: automatically select newly created project

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21369?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-21369: ----------------------------------- Assignee: Fred Bricon > Project Manager: automatically select newly created project > ----------------------------------------------------------- > > Key: JBIDE-21369 > URL: https://issues.jboss.org/browse/JBIDE-21369 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Fred Bricon > Assignee: Fred Bricon > Fix For: 4.3.1.Beta2 > > > - Open OpenShift 3's "new application" wizard > - click on the manage project link, the OpenShift Projects wizard opens > - click on the New... button to open the New OpenShift Project wizard > - enter a project name and click Finish to create it > ASSERT: the newly created project should be selected in OpenShift Projects wizard, so clicking finish will automatically use it in the new application wizard. > Instead, one has to manually select the new project. That's one click too many > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21369) Project Manager: automatically select newly created project

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21369?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21369: -------------------------------- Fix Version/s: 4.3.1.Beta2 > Project Manager: automatically select newly created project > ----------------------------------------------------------- > > Key: JBIDE-21369 > URL: https://issues.jboss.org/browse/JBIDE-21369 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Fred Bricon > Assignee: Fred Bricon > Fix For: 4.3.1.Beta2 > > > - Open OpenShift 3's "new application" wizard > - click on the manage project link, the OpenShift Projects wizard opens > - click on the New... button to open the New OpenShift Project wizard > - enter a project name and click Finish to create it > ASSERT: the newly created project should be selected in OpenShift Projects wizard, so clicking finish will automatically use it in the new application wizard. > Instead, one has to manually select the new project. That's one click too many > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21368) jboss-runtimes are still not scanned under windows

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21368?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-21368: ---------------------------------- Fix Version/s: 4.3.1.Beta2 (was: 4.3.1.Beta1) > jboss-runtimes are still not scanned under windows > -------------------------------------------------- > > Key: JBIDE-21368 > URL: https://issues.jboss.org/browse/JBIDE-21368 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Fix For: 4.3.1.Beta2, 4.4.0.Alpha1 > > > JBDS-2515 requested that ~/jboss-runtimes would be scanned but seem to have ended up being to only add this on new workspaces and *only* if the location exist when creating the new workspace. > I found no way to have restore defaults or any way to actually have the scan happen. > Why are we not always adding ~/jboss-runtimes to the list of locations to scan no matter if the location exists or not ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21368) jboss-runtimes are still not scanned under windows

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21368?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-21368: --------------------------------------- Under windows ~/jboss-runtimes are still not scanned, see test failures http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-base_maste... uder windows configuration. {code}Error Message expected:<1> but was:<0> Stacktrace junit.framework.AssertionFailedError: expected:<1> but was:<0> at junit.framework.Assert.fail(Assert.java:57) at junit.framework.Assert.failNotEquals(Assert.java:329) at junit.framework.Assert.assertEquals(Assert.java:78) at junit.framework.Assert.assertEquals(Assert.java:234) at junit.framework.TestCase.assertEquals(TestCase.java:401) at org.jboss.tools.runtime.test.RuntimeDetectionFrameworkTest.testLoadSaveRuntimePaths(RuntimeDetectionFrameworkTest.java:73) {code} > jboss-runtimes are still not scanned under windows > -------------------------------------------------- > > Key: JBIDE-21368 > URL: https://issues.jboss.org/browse/JBIDE-21368 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > JBDS-2515 requested that ~/jboss-runtimes would be scanned but seem to have ended up being to only add this on new workspaces and *only* if the location exist when creating the new workspace. > I found no way to have restore defaults or any way to actually have the scan happen. > Why are we not always adding ~/jboss-runtimes to the list of locations to scan no matter if the location exists or not ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21368) jboss-runtimes are still not scanned under windows

by Denis Golovin (JIRA)

Denis Golovin created JBIDE-21368: ------------------------------------- Summary: jboss-runtimes are still not scanned under windows Key: JBIDE-21368 URL: https://issues.jboss.org/browse/JBIDE-21368 Project: Tools (JBoss Tools) Issue Type: Bug Components: runtime-detection Reporter: Max Rydahl Andersen Assignee: Rob Stryker Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 JBDS-2515 requested that ~/jboss-runtimes would be scanned but seem to have ended up being to only add this on new workspaces and *only* if the location exist when creating the new workspace. I found no way to have restore defaults or any way to actually have the scan happen. Why are we not always adding ~/jboss-runtimes to the list of locations to scan no matter if the location exists or not ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21365) Beta 4.3.1 N&N for OpenShift should state that while the CDK is treated as a server, runtime detection is not possible

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21365?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-21365: ------------------------------------- [~fbricon] yeah I told [~ldimaggio] already, but he just wants the n&n updated to mention it. I'll get on it. > Beta 4.3.1 N&N for OpenShift should state that while the CDK is treated as a server, runtime detection is not possible > ---------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21365 > URL: https://issues.jboss.org/browse/JBIDE-21365 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Reporter: Len DiMaggio > Assignee: Rob Stryker > Priority: Minor > > This may be obvious to some/most users, but it may confuse other users - it would be better to make it explicit that runtime detection is not possible for runtime detection to detect the raw CDK. > Since it's a raw cdk it is proper to fail to detect - here's no real way to detect cdk vs any other random vagrantfile. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21365) Beta 4.3.1 N&N for OpenShift should state that while the CDK is treated as a server, runtime detection is not possible

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21365?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-21365: ------------------------------------- the detector requires the cdk to provide a .cdk file along the VagrantFile, thus it won't detect any random Vagrantfile as CDK, unless .cdk is present > Beta 4.3.1 N&N for OpenShift should state that while the CDK is treated as a server, runtime detection is not possible > ---------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21365 > URL: https://issues.jboss.org/browse/JBIDE-21365 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Reporter: Len DiMaggio > Assignee: Rob Stryker > Priority: Minor > > This may be obvious to some/most users, but it may confuse other users - it would be better to make it explicit that runtime detection is not possible for runtime detection to detect the raw CDK. > Since it's a raw cdk it is proper to fail to detect - here's no real way to detect cdk vs any other random vagrantfile. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3560) Arbitrary remote code execution with InvokerTransformer (COLLECTIONS-580)

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3560?page=com.atlassian.jira.plugin.... ] Fred Bricon updated JBDS-3560: ------------------------------ Fix Version/s: 9.1.0.Beta2 (was: 9.0.0.Beta2) > Arbitrary remote code execution with InvokerTransformer (COLLECTIONS-580) > ------------------------------------------------------------------------- > > Key: JBDS-3560 > URL: https://issues.jboss.org/browse/JBDS-3560 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: upstream > Affects Versions: 8.1.0.GA, 9.0.0.GA, 10.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 9.1.0.Beta2, 10.0.0.Alpha1 > > Attachments: apache-commons-collections-in-JBDS7,8,9,10.png, apache-commons-collections-in-JBDS7,8,9,10_refs1.png, apache-commons-collections-in-JBDS7,8,9,10_refs10.png, apache-commons-collections-in-JBDS7,8,9,10_refs7.png, apache-commons-collections-in-JBDS7,8,9,10_refs8-IS-fuse.png, apache-commons-collections-in-JBDS7,8,9,10_refs8.png, apache-commons-collections-in-JBDS7,8,9,10_refs9.png, orbit.R20150519210750_vs_I20151117200049.log.txt, orbit.R20150519210750_vs_I20151117200049.log_onlyLatest.txt > > > This is a container issue to wrap & track https://issues.apache.org/jira/browse/COLLECTIONS-580 > Problem is that JBDS 9 (and probably 8 and 10 too) include org.apache.commons.collections 3.2.0.v2013030210310, which is affected by COLLECTIONS-580 - Arbitrary remote code execution with InvokerTransformer -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-696) Support for the CDK in JBDS 9.1.beta1 should be more prominent in the release notes

by Len DiMaggio (JIRA)

Len DiMaggio created TOOLSDOC-696: ------------------------------------- Summary: Support for the CDK in JBDS 9.1.beta1 should be more prominent in the release notes Key: TOOLSDOC-696 URL: https://issues.jboss.org/browse/TOOLSDOC-696 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Bug Components: Release Notes Environment: Build Name: 23115, 9.1 Beta1 Release Notes-9.1-Beta1 Build Date: 18-12-2015 22:13:00 Topic ID: 44506-773485 [Latest] Reporter: Len DiMaggio Assignee: Misha Ali Title: New Features Describe the issue: The text describing the new support fo rthe CDK in JBDS 9.1 is correct in the draft release notes: '...Integration with Red Hat Container Development Kit: A new server adapter has been added to help start and stop the Red Hat Container Development Kit (CDK), a set of tools meant to quickly set up an OpenShift instance inside a Docker container running inside a virtual machine. While the server adapter itself has limited functionality, it is able to start and stop the CDK virtual machine via its Vagrantfile. Once started, Docker and OpenShift connections should appear in their respective views, allowing the user to quickly create a new OpenShift application and begin developing their AwesomeApp in a highly-replicatable environment...' But - I'd suggest that this moved to a more prominent location in the release notes as it is a major reason for the creation of the beta1 release. Can we also add a screenshot? Suggestions for improvement: Additional information: -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21367) Include nightly build of Docker tooling in TP

by Xavier Coulon (JIRA)

Xavier Coulon created JBIDE-21367: ------------------------------------- Summary: Include nightly build of Docker tooling in TP Key: JBIDE-21367 URL: https://issues.jboss.org/browse/JBIDE-21367 Project: Tools (JBoss Tools) Issue Type: Task Components: target-platform Affects Versions: 4.3.1.Beta2 Reporter: Xavier Coulon Fix For: 4.3.1.Beta2 Please include the latest nightly build of the Docker tooling once the TP for JBoss Tools 4.3.1.Beta1 needs to be built. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 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