November 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-21080) Explorer: "Import Application" context menu item is available for any tree item under an OpenShift 3 connection

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21080?page=com.atlassian.jira.plugi... ] Fred Bricon resolved JBIDE-21080. --------------------------------- Resolution: Done There you go : "Import Application" menu now restricted to connection, project and build configs. > Explorer: "Import Application" context menu item is available for any tree item under an OpenShift 3 connection > --------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21080 > URL: https://issues.jboss.org/browse/JBIDE-21080 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Marián Labuda > Assignee: Fred Bricon > Priority: Minor > Labels: explorer, import_wizard, openshift_v3 > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > There is a context menu item to import an existing OpenShift 3 application available on every tree item placed under OpenShift 3 connection. Even "folder" for any resource has it (e.g. Routes, Services) and any resource too (e.g. specific pod, service, replication controller). > I think this is not good because it go against concept of *context* menu. We could have it for a project and build config (maybe also for a connection) that would be sufficient. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20990) Add "CDK Server" for start/stop for the CDK

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20990?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-20990: ------------------------------------- Initial PRs have been merged. Still need to fix Windows support though (currently hard codes vagrant path for linux in plugins/org.jboss.tools.openshift.cdk.server/src/org/jboss/tools/openshift/cdk/server/core/internal/CDKConstantUtility.java) > Add "CDK Server" for start/stop for the CDK > ------------------------------------------- > > Key: JBIDE-20990 > URL: https://issues.jboss.org/browse/JBIDE-20990 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Fix For: 4.4.0.Alpha1 > > > We want to be able to start/stop CDK easily. > Current suggestion is to use a server entry in server view that can start/stop vagrant by simply knowing its file location would be a good start. > note: the vagrant image might already be running so just need to be able to take care of that. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21155) fix test failures

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21155?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-21155: ---------------------------------------- Assignee: Andre Dietisheim > fix test failures > ----------------- > > Key: JBIDE-21155 > URL: https://issues.jboss.org/browse/JBIDE-21155 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > {code} > Tests in error: > ConnectionPropertySourceTest.setup:29 » IllegalArgument > ConnectionPropertySourceTest.setup:29 » IllegalArgument > ConnectionPersistencyTest.setup:36 » IllegalArgument > ConnectionPersistencyTest.setup:36 » IllegalArgument > ConnectionPersistencyTest.setup:36 » IllegalArgument > ConnectionTest.setup:52 » IllegalArgument > ConnectionTest.setup:52 » IllegalArgument > ConnectionTest.setup:52 » IllegalArgument > ConnectionTest.setup:52 » IllegalArgument > ConnectionTest.setup:52 » IllegalArgument > ConnectionTest.setup:52 » IllegalArgument > ConnectionTest.setup:52 » IllegalArgument > ConnectionTest.setup:52 » IllegalArgument > ConnectionTest.setup:52 » IllegalArgument > ConnectionTest.setup:52 » IllegalArgument > OpenShiftExplorerContentProviderTest.setup:51 » IllegalArgument > OpenShiftExplorerContentProviderTest.setup:51 » IllegalArgument > OpenShiftExplorerContentProviderTest.setup:51 » IllegalArgument > OpenShiftExplorerContentProviderTest.setup:51 » IllegalArgument > OpenShiftExplorerContentProviderTest.setup:51 » IllegalArgument > OpenShiftExplorerContentProviderTest.setup:51 » IllegalArgument > OpenShiftExplorerContentProviderTest.setup:51 » IllegalArgument > OpenShiftExplorerLabelProviderTest.getStyledTextForAConnection:188 » IllegalArgument > OpenShiftExplorerLabelProviderTest.getStyledTextForAConnectionWithoutUserName:195 » IllegalArgument > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21155) fix test failures

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21155?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21155: ------------------------------------- Fix Version/s: 4.3.1.Beta1 4.4.0.Alpha1 > fix test failures > ----------------- > > Key: JBIDE-21155 > URL: https://issues.jboss.org/browse/JBIDE-21155 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Andre Dietisheim > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > {code} > Tests in error: > ConnectionPropertySourceTest.setup:29 » IllegalArgument > ConnectionPropertySourceTest.setup:29 » IllegalArgument > ConnectionPersistencyTest.setup:36 » IllegalArgument > ConnectionPersistencyTest.setup:36 » IllegalArgument > ConnectionPersistencyTest.setup:36 » IllegalArgument > ConnectionTest.setup:52 » IllegalArgument > ConnectionTest.setup:52 » IllegalArgument > ConnectionTest.setup:52 » IllegalArgument > ConnectionTest.setup:52 » IllegalArgument > ConnectionTest.setup:52 » IllegalArgument > ConnectionTest.setup:52 » IllegalArgument > ConnectionTest.setup:52 » IllegalArgument > ConnectionTest.setup:52 » IllegalArgument > ConnectionTest.setup:52 » IllegalArgument > ConnectionTest.setup:52 » IllegalArgument > OpenShiftExplorerContentProviderTest.setup:51 » IllegalArgument > OpenShiftExplorerContentProviderTest.setup:51 » IllegalArgument > OpenShiftExplorerContentProviderTest.setup:51 » IllegalArgument > OpenShiftExplorerContentProviderTest.setup:51 » IllegalArgument > OpenShiftExplorerContentProviderTest.setup:51 » IllegalArgument > OpenShiftExplorerContentProviderTest.setup:51 » IllegalArgument > OpenShiftExplorerContentProviderTest.setup:51 » IllegalArgument > OpenShiftExplorerLabelProviderTest.getStyledTextForAConnection:188 » IllegalArgument > OpenShiftExplorerLabelProviderTest.getStyledTextForAConnectionWithoutUserName:195 » IllegalArgument > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21155) fix test failures

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-21155: ---------------------------------------- Summary: fix test failures Key: JBIDE-21155 URL: https://issues.jboss.org/browse/JBIDE-21155 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.1.Beta1 Reporter: Andre Dietisheim {code} Tests in error: ConnectionPropertySourceTest.setup:29 » IllegalArgument ConnectionPropertySourceTest.setup:29 » IllegalArgument ConnectionPersistencyTest.setup:36 » IllegalArgument ConnectionPersistencyTest.setup:36 » IllegalArgument ConnectionPersistencyTest.setup:36 » IllegalArgument ConnectionTest.setup:52 » IllegalArgument ConnectionTest.setup:52 » IllegalArgument ConnectionTest.setup:52 » IllegalArgument ConnectionTest.setup:52 » IllegalArgument ConnectionTest.setup:52 » IllegalArgument ConnectionTest.setup:52 » IllegalArgument ConnectionTest.setup:52 » IllegalArgument ConnectionTest.setup:52 » IllegalArgument ConnectionTest.setup:52 » IllegalArgument ConnectionTest.setup:52 » IllegalArgument OpenShiftExplorerContentProviderTest.setup:51 » IllegalArgument OpenShiftExplorerContentProviderTest.setup:51 » IllegalArgument OpenShiftExplorerContentProviderTest.setup:51 » IllegalArgument OpenShiftExplorerContentProviderTest.setup:51 » IllegalArgument OpenShiftExplorerContentProviderTest.setup:51 » IllegalArgument OpenShiftExplorerContentProviderTest.setup:51 » IllegalArgument OpenShiftExplorerContentProviderTest.setup:51 » IllegalArgument OpenShiftExplorerLabelProviderTest.getStyledTextForAConnection:188 » IllegalArgument OpenShiftExplorerLabelProviderTest.getStyledTextForAConnectionWithoutUserName:195 » IllegalArgument {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21142) could JBDS Discovery build depend on JDBS root pom?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21142?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-21142. ------------------------------ Resolution: Done Closing. Should anyone feel compelled to reopen, please do so and explain why we need to publish another pom or introduce a jbt -> jbds -> jbt project dependency for such a trivial concern. > could JBDS Discovery build depend on JDBS root pom? > --------------------------------------------------- > > Key: JBIDE-21142 > URL: https://issues.jboss.org/browse/JBIDE-21142 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Trivial > Fix For: 4.4.0.Alpha1 > > > {quote} > creation of a JBDS/discovery parent pom? > https://github.com/jbosstools/jbosstools-build/commit/5ce5c5aa9c6febd562d... > and https://github.com/jbosstools/jbosstools-discovery/pull/279 > try this: jbds disco depends on jbds prod root pom?{quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21147) Cannot deploy docker image to OpenShift because of image tag

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21147?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-21147: --------------------------------------- [~fbricon] [~adietish] please review > Cannot deploy docker image to OpenShift because of image tag > ------------------------------------------------------------ > > Key: JBIDE-21147 > URL: https://issues.jboss.org/browse/JBIDE-21147 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: docker, openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Marián Labuda > Assignee: Jeff Cantrill > Priority: Critical > Fix For: 4.3.1.Beta1 > > Attachments: resources_summary.png > > > When I am trying to deploy a docker image to OpenShift, I get following error when dialog with created resources shows up > !resources_summary.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21142) could JBDS Discovery build depend on JDBS root pom?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21142?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-21142: ------------------------------- Priority: Trivial (was: Major) > could JBDS Discovery build depend on JDBS root pom? > --------------------------------------------------- > > Key: JBIDE-21142 > URL: https://issues.jboss.org/browse/JBIDE-21142 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Trivial > Fix For: 4.4.0.Alpha1 > > > {quote} > creation of a JBDS/discovery parent pom? > https://github.com/jbosstools/jbosstools-build/commit/5ce5c5aa9c6febd562d... > and https://github.com/jbosstools/jbosstools-discovery/pull/279 > try this: jbds disco depends on jbds prod root pom?{quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21142) could JBDS Discovery build depend on JDBS root pom?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21142?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-21142: ------------------------------- Issue Type: Enhancement (was: Bug) > could JBDS Discovery build depend on JDBS root pom? > --------------------------------------------------- > > Key: JBIDE-21142 > URL: https://issues.jboss.org/browse/JBIDE-21142 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Trivial > Fix For: 4.4.0.Alpha1 > > > {quote} > creation of a JBDS/discovery parent pom? > https://github.com/jbosstools/jbosstools-build/commit/5ce5c5aa9c6febd562d... > and https://github.com/jbosstools/jbosstools-discovery/pull/279 > try this: jbds disco depends on jbds prod root pom?{quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21142) could JBDS Discovery build depend on JDBS root pom?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21142?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-21142: ------------------------------- Fix Version/s: 4.4.0.Alpha1 > could JBDS Discovery build depend on JDBS root pom? > --------------------------------------------------- > > Key: JBIDE-21142 > URL: https://issues.jboss.org/browse/JBIDE-21142 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha1 > > > {quote} > creation of a JBDS/discovery parent pom? > https://github.com/jbosstools/jbosstools-build/commit/5ce5c5aa9c6febd562d... > and https://github.com/jbosstools/jbosstools-discovery/pull/279 > try this: jbds disco depends on jbds prod root pom?{quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues November 2015