December 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-21056) Application wizard: Read-only labels should have a visual hint they're read-only

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21056?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21056: -------------------------------- Fix Version/s: 4.3.1.Beta2 (was: 4.3.1.Beta1) > Application wizard: Read-only labels should have a visual hint they're read-only > -------------------------------------------------------------------------------- > > Key: JBIDE-21056 > URL: https://issues.jboss.org/browse/JBIDE-21056 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta1 > Environment: Nightly JBT. OpenShift tooling build Version: 3.1.0.Beta1-v20151104-0336-B66 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Priority: Minor > Labels: application_wizard, openshift_v3 > Fix For: 4.3.1.Beta2 > > > Labels in a New OpenShift Application wizard on the page containing label managing are not treated equally. When application is build on a template with more predefined labels, the first one listed in the table with labels is read-only, but the second one (maybe also further labels) are editable and removable. We should treat all labels equally. Either take them as read only from templates or allow user to modify them. As an testing example was used template located at https://github.com/jboss-openshift/application-templates/blob/master/eap/... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20719) Updating a token for OpenShift 3 connection via Edit Connection does not update resources

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20719?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-20719: -------------------------------- Fix Version/s: 4.3.1.Beta2 (was: 4.3.1.Beta1) > Updating a token for OpenShift 3 connection via Edit Connection does not update resources > ----------------------------------------------------------------------------------------- > > Key: JBIDE-20719 > URL: https://issues.jboss.org/browse/JBIDE-20719 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Marián Labuda > Fix For: 4.3.1.Beta2 > > > If token storage in secure storage expires and new one is required to be able to work with OpenShift 3 connection, then updating token via Edit Connection dialog does not automatically update connection. There is still error tree item under resources saying to obtain a new token. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21122) Port Forwarding: Start All button should be disabled if port forwarding is already active

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21122?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21122: -------------------------------- Fix Version/s: 4.3.1.Beta2 (was: 4.3.1.Beta1) > Port Forwarding: Start All button should be disabled if port forwarding is already active > ----------------------------------------------------------------------------------------- > > Key: JBIDE-21122 > URL: https://issues.jboss.org/browse/JBIDE-21122 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Marián Labuda > Labels: openshift_v3, port_forwarding_wizard > Fix For: 4.3.1.Beta2 > > > In Port Forwarding wizard is a button "Start All" which starts port forwarding for all services listed in a table. If user triggers the button and port forwarding is already active, Start All is still enabled and user can click on it again and again but nothing happens. Accessibility of this button should be similar as Stop All, which works as expected - if port forwarding is not active, it is disabled, otherwise it is enabled. > There is also a checkbox to find free ports for port forwarding. Once port forwarding is active, checking and unchecking this checkbox do nothing. It should have same accessibility as Start All button - if there is active port forwarding, the checkbox should be disabled, otherwise it should be enabled. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20603) context menu of openshift is not using global commands like delete or properties

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20603?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-20603: -------------------------------- Fix Version/s: 4.3.1.Beta2 (was: 4.3.1.Beta1) > context menu of openshift is not using global commands like delete or properties > -------------------------------------------------------------------------------- > > Key: JBIDE-20603 > URL: https://issues.jboss.org/browse/JBIDE-20603 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Max Rydahl Andersen > Priority: Critical > Fix For: 4.3.1.Beta2 > > > Delete Project, resource etc. should use the normal Delete command. It seems we've created custom commands and UI for it instead of just using the default Delete command as used in other context menus. > Similar we dont seem to use standard Properties > see https://wiki.eclipse.org/Menu_Contributions/Problems_View_Example on how to use org.eclipse.ui.edit.delete etc. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20636) Push changes: Management interface wont come up while deployment

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20636?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-20636: -------------------------------- Fix Version/s: 4.3.1.Beta2 (was: 4.3.1.Beta1) > Push changes: Management interface wont come up while deployment > ---------------------------------------------------------------- > > Key: JBIDE-20636 > URL: https://issues.jboss.org/browse/JBIDE-20636 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Jeff Cantrill > Labels: openshift_v2 > Fix For: 4.3.1.Beta2 > > > Reference: https://github.com/openshift/origin/issues/4502 > {code} > Preparing build for deployment > Deployment id is f2c69660 > Activating deployment > Starting PHPMyAdmin cartridge > Starting MySQL 5.5 cartridge Deploying JBoss > Starting jbossas cartridge > Found 127.3.158.129:8080 listening port > Found 127.3.158.129:9999 listening port > CLIENT_MESSAGE: Could not connect to JBoss management interface, skipping deployment verification > ------------------------- > Git Post-Receive Result: success > Activation status: success > Deployment completed with status: success > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20568) Duplicate templates in different OpenShift projects are not distinguishable from each other

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20568?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-20568: -------------------------------- Fix Version/s: 4.3.1.Beta2 (was: 4.3.1.Beta1) > Duplicate templates in different OpenShift projects are not distinguishable from each other > ------------------------------------------------------------------------------------------- > > Key: JBIDE-20568 > URL: https://issues.jboss.org/browse/JBIDE-20568 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Jeff Cantrill > Priority: Minor > Fix For: 4.3.1.Beta2 > > Attachments: screenshot-1.png > > > New app from template should allow a user to pick templates form either the 'OpenShift' project or their own and they should be able to tell the difference. The attached screen show displays the same template twice but actually, one is in the openshift project and the other is in the 'hello-world' -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20761) Support editing Build Configuration parameters

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20761?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-20761: -------------------------------- Fix Version/s: 4.3.1.Beta2 (was: 4.3.1.Beta1) > Support editing Build Configuration parameters > ---------------------------------------------- > > Key: JBIDE-20761 > URL: https://issues.jboss.org/browse/JBIDE-20761 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21162) cannot decide to only save username

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21162?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-21162: -------------------------------- Fix Version/s: 4.3.1.Beta1 4.4.0.Alpha1 > cannot decide to only save username > ----------------------------------- > > Key: JBIDE-21162 > URL: https://issues.jboss.org/browse/JBIDE-21162 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > with the new credentials I seem to be *forced* to store my password for things like the CDK server adapter. > I should be able to use credentials that just ask me when it is needed and not persist across workspace sessions. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21205) Modify runtime detection to ensure a detector is only asked to initialize runtime definitions it created

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21205?page=com.atlassian.jira.plugi... ] Rob Stryker reassigned JBIDE-21205: ----------------------------------- Assignee: Rob Stryker > Modify runtime detection to ensure a detector is only asked to initialize runtime definitions it created > -------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21205 > URL: https://issues.jboss.org/browse/JBIDE-21205 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.3.0.Beta2 > Reporter: Rob Stryker > Assignee: Rob Stryker > Priority: Minor > > See https://issues.jboss.org/browse/JBIDE-21193 for some background. > A runtime detector is asked to initialize all RuntimeDefinition objects, not just ones it created. While this "works" if you expect a detector to know all type-strings that it creates RuntimeDefinition objects using, it is still less than optimal and the workflow is a bit counter-intuitive. > Suggestion is to add a new constructor to RuntimeDefinition and add abstract method for creating those definitions to AbstractRuntimeDetectorDelegate to instantiate these definitions. > Care should be taken since this is all public API and used in Fuse, cdk, servertools, and other locations. It may not be possible to compel consumers to use the new API at all, and so the benefit may be zero. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16970) create mechanism to verify that nightly build is different from previous milestone

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16970?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-16970: ------------------------------------ p2diff now builds in Jenkins [1] and deploys to Nexus [2]. [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/p2diff/ [2] https://repository.jboss.org/nexus/content/repositories/snapshots/org/ecl... > create mechanism to verify that nightly build is different from previous milestone > ---------------------------------------------------------------------------------- > > Key: JBIDE-16970 > URL: https://issues.jboss.org/browse/JBIDE-16970 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.2.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.x > > > After the discovery site build job is done, we should: > * get a list of JIRAs for a given target fixversion, eg., 4.2.0.Beta1 or 8.0.0.Beta1 *job param* milestone = Beta1, Beta2, CR1, Final/GA (special case) > * for respins, use *job param* label = "respin-a" or "respin-b" in jira query > * filter query to only show the components and map those to actual project names - see https://github.com/jbdevstudio/jbdevstudio-ci/blob/master/bin/createTaskJ... for mappings > * install Eclipse from *job param* eclipseBundleVersion = luna.M6 > * install last milestone from *job param* oldURL = http://download.jboss.org/jbosstools/updates/staging/JBossTools-4.2.0.Bet... > * install Eclipse from *job param* eclipseBundleVersion = luna.M6 (in a different folder) > * install new nightly from *job param* oldURL = http://download.jboss.org/jbosstools/updates/nightlycore/4.2.luna/ > * compare installed footprints - see https://github.com/jbosstools/jbosstools-build-ci/blob/master/util/instal... > * run p2diff on the two repos - see https://github.com/irbull/p2diff -- 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