April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21111) [connection wizard] empty password should not be allowed

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21111?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21111. --------------------------------- Verified in JBDS 10.0.0.Alpha1 B5240. > [connection wizard] empty password should not be allowed > -------------------------------------------------------- > > Key: JBIDE-21111 > URL: https://issues.jboss.org/browse/JBIDE-21111 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Final > Reporter: Fred Bricon > Assignee: Fred Bricon > Fix For: 4.4.0.Alpha1 > > > https://github.com/redhat-developer/openshift-vagrant (requires read authorization) provides a VM with OpenShift where anonymous authentication is supported, i.e. any username will be accepted (a user will be created on-the-fly) and there's no check on passwords. > However the connection wizard doesn't allow blank/empty passwords. Also it currently trims whitespaces from passwords. So one has to type in a dummy password in order to get through authentication. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-512) Move from staging TP dependency repos to released development repos.

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-512?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-512. ----------------------------------- Closed as obsolete. Current JBTIS TP 4.3.1.Final refers to the final repos. > Move from staging TP dependency repos to released development repos. > -------------------------------------------------------------------- > > Key: JBTIS-512 > URL: https://issues.jboss.org/browse/JBTIS-512 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: target-platform > Affects Versions: 4.3.0.Final-TP > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 4.3.0.Final-TP > > > *Reason:* Move from staging TP dependency repos to released development repos. Also move from an https locus URL to http > *Project page/sources:* > *Version:* 4.3.0.Beta1f-SNAPSHOT > *License and owner:* EPL > *Original p2 repo:* > *JBoss mirror:* > *Include Sources:* Yes > *Affected JBoss Tools components:* .JBDSIS > *Include in JBDS:* Yes (JBDSIS) > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > No changes - just moved to development URLs from staging URLs. > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-522) Update 4.3.0.Final composites

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-522?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-522. ----------------------------------- Verified. JBTIS 4.3.0.Final contains the following final components * BPEL 1.0.5.Final * BPMN2 1.2.4.Final * Drools 6.4.0.Final * ESB 1.6.100.Final * jBPM3 4.5.200.Final and earlyaccess components * Fuse 8.0.0.Beta2 * SwitchYard 2.1.0.Beta3 * Modeshape 3.8.0.Beta1 * Teiid designer 10.0.0.Beta3 > Update 4.3.0.Final composites > ----------------------------- > > Key: JBTIS-522 > URL: https://issues.jboss.org/browse/JBTIS-522 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 4.3.0.Final-TP, 4.3.0.Final > > > The IS is now at 9.0.0.GA/ 4.3.0.Final - update the community side. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22265) Application wizard: Allow users to reset values of all template parameters

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-22265: ------------------------------------- Summary: Application wizard: Allow users to reset values of all template parameters Key: JBIDE-22265 URL: https://issues.jboss.org/browse/JBIDE-22265 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 4.4.0.Alpha1 Reporter: Marián Labuda At the moment we allow users to reset a specific value in the table containing template parameters in New OpenShift Application wizard. It would be nice to have option to reset all template parameters (get default values for all) to have it consistent across wizards. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22265) Application wizard: Allow users to reset values of all template parameters

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22265?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-22265: ---------------------------------- Labels: application_wizard openshift_v3 (was: ) > Application wizard: Allow users to reset values of all template parameters > -------------------------------------------------------------------------- > > Key: JBIDE-22265 > URL: https://issues.jboss.org/browse/JBIDE-22265 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Labels: application_wizard, openshift_v3 > > At the moment we allow users to reset a specific value in the table containing template parameters in New OpenShift Application wizard. It would be nice to have option to reset all template parameters (get default values for all) to have it consistent across wizards. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22263) Deploy Docker Wizard: Reset button on Deployment Configuration wizard page in Deploy Image could reset ALL env. vars

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22263?page=com.atlassian.jira.plugi... ] Marián Labuda commented on JBIDE-22263: --------------------------------------- Hmm yeah, I agree with you. Useful both options - reset a single value and reset whole table. This is related also to reset values of template parameters in New OpenShift Application wizard. I will create a JIRA for that one too and link it to this one. > Deploy Docker Wizard: Reset button on Deployment Configuration wizard page in Deploy Image could reset ALL env. vars > -------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22263 > URL: https://issues.jboss.org/browse/JBIDE-22263 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Labels: deploy_, deploy_docker_wizard, docker, openshift_v3 > > In Deploy Image to OpenShift wizard on the wizard page containing environment variables there is a Reset button. At the moment reset works only for one environment variable at the moment. It would be nice, if reset would set all environment variables (whole table) to default state. Currently the next wizard page containing ports mapping behave in desired way (reset set ports to default values), therefore it would be nice to have it consistent across wizard pages which are next to each other. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22262) Only OpenShift 3 connections should be listed when opening Deploy Image to OpenShift wizard

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22262?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-22262 at 4/28/16 6:20 AM: ------------------------------------------------------------------- This is already supported and used in other places. When adding the connection wizard page to the wizard, simply use a type parameter (Connection.class) when instantiating the page: {code:title=ConnectionWizardPage} public <C extends IConnection> ConnectionWizardPage(IWizard wizard, IConnectionAware<C> wizardModel, Class<? extends IConnection> connectionType) { {code} A usage example is in the ConnectionWizardFragment which is using the WrappedConnectionWizardPage: {code} private WrappedConnectionWizardPage(IWizardHandle wizardHandle) { super(((IWizardPage) wizardHandle).getWizard(), new ConnectionWizardModel(Connection.class), Connection.class); {code} was (Author: adietish): This is already supported and used in other places. When adding the connection wizard page to the wizard, simply use a type parameter (Connection.class) when instantiating the page: {code:title=ConnectionWizardPage} protected <C extends IConnection> ConnectionWizardPage(IWizard wizard, IConnectionAware<C> wizardModel, Class<? extends IConnection> connectionType, boolean allowConnectionChange) { {code} > Only OpenShift 3 connections should be listed when opening Deploy Image to OpenShift wizard > ------------------------------------------------------------------------------------------- > > Key: JBIDE-22262 > URL: https://issues.jboss.org/browse/JBIDE-22262 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Labels: docker, openshift_v3 > Fix For: 4.4.0.Alpha1 > > > When opening Deploy Image to OpenShift wizard from context menu of a docker image, connection dialog is opened at first. There is available OpenShift 3 type of server as well as OpenShift 2 server. There should be available only OpenShift 3 server type and listed only OpenShift 3 connections. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22262) Only OpenShift 3 connections should be listed when opening Deploy Image to OpenShift wizard

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22262?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-22262: ------------------------------------------ This is already supported and used in other places. When adding the connection wizard page to the wizard, simply use a type parameter (Connection.class) when instantiating the page: {code:title=ConnectionWizardPage} protected <C extends IConnection> ConnectionWizardPage(IWizard wizard, IConnectionAware<C> wizardModel, Class<? extends IConnection> connectionType, boolean allowConnectionChange) { {code} > Only OpenShift 3 connections should be listed when opening Deploy Image to OpenShift wizard > ------------------------------------------------------------------------------------------- > > Key: JBIDE-22262 > URL: https://issues.jboss.org/browse/JBIDE-22262 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Labels: docker, openshift_v3 > Fix For: 4.4.0.Alpha1 > > > When opening Deploy Image to OpenShift wizard from context menu of a docker image, connection dialog is opened at first. There is available OpenShift 3 type of server as well as OpenShift 2 server. There should be available only OpenShift 3 server type and listed only OpenShift 3 connections. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22262) Only OpenShift 3 connections should be listed when opening Deploy Image to OpenShift wizard

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22262?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22262: ------------------------------------- Fix Version/s: 4.4.0.Alpha1 > Only OpenShift 3 connections should be listed when opening Deploy Image to OpenShift wizard > ------------------------------------------------------------------------------------------- > > Key: JBIDE-22262 > URL: https://issues.jboss.org/browse/JBIDE-22262 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Labels: docker, openshift_v3 > Fix For: 4.4.0.Alpha1 > > > When opening Deploy Image to OpenShift wizard from context menu of a docker image, connection dialog is opened at first. There is available OpenShift 3 type of server as well as OpenShift 2 server. There should be available only OpenShift 3 server type and listed only OpenShift 3 connections. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22264) Tracing: Distinguish OpenShift versions on Tracing preference page

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22264?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22264: ------------------------------------- Summary: Tracing: Distinguish OpenShift versions on Tracing preference page (was: Distinguish OpenShift versions on Tracing preference page) > Tracing: Distinguish OpenShift versions on Tracing preference page > ------------------------------------------------------------------ > > Key: JBIDE-22264 > URL: https://issues.jboss.org/browse/JBIDE-22264 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Labels: openshift_v2, openshift_v3, tracing > Fix For: 4.4.0.Alpha2 > > > On preference page Tracing there are OpenShift plugin to trace. At the moment plugins are not distinguished and if user does not know that \*express\* is related to OpenShift 2 he can be lost. It would be nice if plugins could be spotted distinct on first sight. In the tree on the preference page are at the moment tree items "OpenShift client" for both. It could be "OpenShift 2 client" and "OpenShift 3 client". -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 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 April 2016