December 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-21353) Creation of CDK adapter is not tracked in analytics

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21353?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-21353: ----------------------------------- Fix Version/s: 4.3.1.Beta2 4.4.0.Alpha1 > Creation of CDK adapter is not tracked in analytics > --------------------------------------------------- > > Key: JBIDE-21353 > URL: https://issues.jboss.org/browse/JBIDE-21353 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, server, usage > Affects Versions: 4.3.1.Beta1 > Environment: JBDS 9.1.0.Beta1a > Reporter: Radim Hopp > Assignee: Rob Stryker > Fix For: 4.3.1.Beta2, 4.4.0.Alpha1 > > > Manual creation (Server->New) nor via runtime detection of CDK is not sent to google analytics. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21353) Creation of CDK adapter is not tracked in analytics

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21353?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-21353: ----------------------------------- Component/s: openshift server > Creation of CDK adapter is not tracked in analytics > --------------------------------------------------- > > Key: JBIDE-21353 > URL: https://issues.jboss.org/browse/JBIDE-21353 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, server, usage > Affects Versions: 4.3.1.Beta1 > Environment: JBDS 9.1.0.Beta1a > Reporter: Radim Hopp > > Manual creation (Server->New) nor via runtime detection of CDK is not sent to google analytics. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21355) Edit resource properties from Properties view

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21355?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21355: -------------------------------- Description: Resources are currently editable from a source editor (see JBIDE-20761). It'd be nice to have a more fined grained approach, and have the properties be directly editable from the Properties view (eg. modify label, change git source url) (was: As a developer I want to be able to update the git url used in my existing OpenShift application buildconfig to use a different repository than what the default template used so I can publish my own changes to OS Pre-Req: - An application is deployed on OpenShift, using git for its source repository Goal: - Modify the git source url used to build and redeploy the application Build Config parameters should be editable from either the Properties view (but how exactly?) or another mechanism from OpenShift Explorer (TBD)) > Edit resource properties from Properties view > --------------------------------------------- > > Key: JBIDE-21355 > URL: https://issues.jboss.org/browse/JBIDE-21355 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Assignee: Fred Bricon > Labels: new_and_noteworthy > Fix For: 4.3.1.Beta2 > > > Resources are currently editable from a source editor (see JBIDE-20761). It'd be nice to have a more fined grained approach, and have the properties be directly editable from the Properties view (eg. modify label, change git source url) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21355) Edit resource properties from Properties view

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-21355: ----------------------------------- Summary: Edit resource properties from Properties view Key: JBIDE-21355 URL: https://issues.jboss.org/browse/JBIDE-21355 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: openshift Affects Versions: 4.3.0.CR1 Reporter: Fred Bricon Assignee: Fred Bricon Fix For: 4.3.1.Beta1 As a developer I want to be able to update the git url used in my existing OpenShift application buildconfig to use a different repository than what the default template used so I can publish my own changes to OS Pre-Req: - An application is deployed on OpenShift, using git for its source repository Goal: - Modify the git source url used to build and redeploy the application Build Config parameters should be editable from either the Properties view (but how exactly?) or another mechanism from OpenShift Explorer (TBD) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21355) Edit resource properties from Properties view

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21355?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21355: -------------------------------- Fix Version/s: 4.3.1.Beta2 (was: 4.3.1.Beta1) > Edit resource properties from Properties view > --------------------------------------------- > > Key: JBIDE-21355 > URL: https://issues.jboss.org/browse/JBIDE-21355 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Assignee: Fred Bricon > Labels: new_and_noteworthy > Fix For: 4.3.1.Beta2 > > > As a developer I want to be able to update the git url used in my existing OpenShift application buildconfig to use a different repository than what the default template used so I can publish my own changes to OS > Pre-Req: > - An application is deployed on OpenShift, using git for its source repository > Goal: > - Modify the git source url used to build and redeploy the application > Build Config parameters should be editable from either the Properties view (but how exactly?) or another mechanism from OpenShift Explorer (TBD) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21355) Edit resource properties from Properties view

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21355?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21355: -------------------------------- Git Pull Request: (was: https://github.com/jbosstools/jbosstools-openshift/pull/840) > Edit resource properties from Properties view > --------------------------------------------- > > Key: JBIDE-21355 > URL: https://issues.jboss.org/browse/JBIDE-21355 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Assignee: Fred Bricon > Labels: new_and_noteworthy > Fix For: 4.3.1.Beta2 > > > As a developer I want to be able to update the git url used in my existing OpenShift application buildconfig to use a different repository than what the default template used so I can publish my own changes to OS > Pre-Req: > - An application is deployed on OpenShift, using git for its source repository > Goal: > - Modify the git source url used to build and redeploy the application > Build Config parameters should be editable from either the Properties view (but how exactly?) or another mechanism from OpenShift Explorer (TBD) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21349) Server Adapter Wizard: "Workspace..." lets you choose files while it should present workspace projects

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21349?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-21349: ------------------------------------- The chooser should let you choose folders, not files. Default folder should be selected project root folder. > Server Adapter Wizard: "Workspace..." lets you choose files while it should present workspace projects > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-21349 > URL: https://issues.jboss.org/browse/JBIDE-21349 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Labels: openshift_v3, server_adapter_wizard > Fix For: 4.3.1.Beta2, 4.4.0.Alpha1 > > Attachments: browse-workspace.png > > > how to reproduce: > # EXEC: File > New > Server > OpenShift 3 > # ASSERT: connection page shows up > # EXEC: provide connection and hit Next > # ASSERT: you get to the server settings page > # EXEC: hit "Workspace..." to the right of "Source Path" > !browse-workspace.png! > Result: > You get a file-chooser that defaults to the workspace and lets you choose files/directories > Expected Result: > You should get a dialog where you can pick a workspace project -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21347) Server Adapter wizard: should default to existing v3 connection (not <New Connection>

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21347?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-21347: ------------------------------------- I think the better option would be to use the last used v3 connection by default > Server Adapter wizard: should default to existing v3 connection (not <New Connection> > ------------------------------------------------------------------------------------- > > Key: JBIDE-21347 > URL: https://issues.jboss.org/browse/JBIDE-21347 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Minor > Labels: connection_wizard > Fix For: 4.3.1.Beta2 > > Attachments: defaults-to-new-connection.png > > > how to reproduce: > # ASSERT: make sure that you have at least 1 connection to a v3 server defined (showing up in OpenShift Explorer) > # EXEC: launch v3 OpenShift server adapter wizard via File > New > Server > OpenShift 3 > # ASSERT: connection dialog shows up as 1st wizard page > Result: > <New Connection> is preselected even though I have 1 v3 connection: > !defaults-to-new-connection.png! > Expected Result: > The last v3 connection that I used should be preselected (if it exists) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21352) OpenShift Server Adapter: New server adapter could use preselected project from project explorer

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21352?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-21352 at 12/17/15 8:55 AM: -------------------------------------------------------------------- The reason is that we're querying the global selection which might be switched over from project explorer to ex. OpenShift Explorer (when we focused it - meanwhile the project explorer kept it's selection). To solve this we should simply query a specific set of explorers that we know of to list the workspace projects: * package explorer: org.eclipse.jdt.ui.PackageExplorer * project explorer: org.eclipse.ui.navigator.ProjectExplorer * navigator: org.eclipse.ui.views.ResourceNavigator was (Author: adietish): The reason is that we're querying the global selection which might be switched over from project explorer to ex. OpenShift Explorer (when we focused it - meanwhile the project explorer kept it's selection). To solve this we should simply query a specific set of explorers that we know of to list the workspace projects: * navigator: org.eclipse.ui.views.ResourceNavigator * project explorer: org.eclipse.ui.navigator.ProjectExplorer * package explorer: org.eclipse.jdt.ui.PackageExplorer > OpenShift Server Adapter: New server adapter could use preselected project from project explorer > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-21352 > URL: https://issues.jboss.org/browse/JBIDE-21352 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter_wizard > Fix For: 4.3.1.Beta2, 4.4.0.Alpha1 > > > It would be nice if wizard to create a new OpenShift 3 server adapter would use preselected project from Project explorer, if it is opened and selected. Currently it uses first eclipse project. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21352) OpenShift Server Adapter: New server adapter could use preselected project from project explorer

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21352?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-21352: ------------------------------------------ The reason is that we're querying the global selection which might be switched over from project explorer to ex. OpenShift Explorer (when we focused it - meanwhile the project explorer kept it's selection). To solve this we should simply query a specific set of explorers that we know of to list the workspace projects: * navigator: org.eclipse.ui.views.ResourceNavigator * project explorer: org.eclipse.ui.navigator.ProjectExplorer * package explorer: org.eclipse.jdt.ui.PackageExplorer > OpenShift Server Adapter: New server adapter could use preselected project from project explorer > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-21352 > URL: https://issues.jboss.org/browse/JBIDE-21352 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter_wizard > Fix For: 4.3.1.Beta2, 4.4.0.Alpha1 > > > It would be nice if wizard to create a new OpenShift 3 server adapter would use preselected project from Project explorer, if it is opened and selected. Currently it uses first eclipse project. -- 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