January 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-23672) Move org.jboss.tools.maven.reddeer to jbosstools-central/maven/test-framework

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23672?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov reassigned JBIDE-23672: ---------------------------------------- Assignee: Dmitrii Bocharov > Move org.jboss.tools.maven.reddeer to jbosstools-central/maven/test-framework > ----------------------------------------------------------------------------- > > Key: JBIDE-23672 > URL: https://issues.jboss.org/browse/JBIDE-23672 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: integration-tests, maven > Reporter: Pavol Srna > Assignee: Dmitrii Bocharov > Fix For: 4.4.3.AM2 > > > https://github.com/jbosstools/jbosstools-integration-tests/tree/master/pl... > https://github.com/jbosstools/jbosstools-central/tree/master/maven -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23724) Integration tests: move webservices integration tests to jbosstools/webservice repo

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23724?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23724: ------------------------------- Component/s: openshift > Integration tests: move webservices integration tests to jbosstools/webservice repo > ------------------------------------------------------------------------------------ > > Key: JBIDE-23724 > URL: https://issues.jboss.org/browse/JBIDE-23724 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, webservices > Affects Versions: 4.4.2.Final > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Labels: integration-test > Fix For: 4.4.3.AM2 > > > we need to move jbosstools/webservices integration tests from their repo to the jbosstools/webservices tools repo -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23729) Implement integration ui tests for validation of job.xml file in design view tab

by Ondrej Dockal (JIRA)

Ondrej Dockal created JBIDE-23729: ------------------------------------- Summary: Implement integration ui tests for validation of job.xml file in design view tab Key: JBIDE-23729 URL: https://issues.jboss.org/browse/JBIDE-23729 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: qa Affects Versions: 4.4.2.AM1 Reporter: Ondrej Dockal Assignee: Ondrej Dockal Fix For: 4.4.3.AM2 Implement ui int. tests for batch job.xml validation that is used in design view tab. It is a subset of features referenced in [jira|https://issues.jboss.org/browse/JBIDE-23728]. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23728) Add new batch integration UI tests for validating the source in job.xml file

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23728?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-23728: ---------------------------------- Description: Implement integration ui tests for validation feature of batch job.xml file. Manipulate with xml file via source view and check its functionality resulting in Problems View. 1. Ref element contains valid name of specific artifact 2. Properties link to valid java field of #jobProperties["xyz"] 3. Id is unique 4. Attributes next and to refer to id of step | split | flow | decision at the same level as the current execution element 5. Attributes 'flow/stop/@restart', 'step/stop/@restart' should refer to id of step | split | flow | decision at the job level 6. Sequence of execution elements defined by @next and @to should not loop. 7. Value of attribute 'include/@class' and 'exclude/@class' is qualified name of an exception class. was:Implement integration ui tests for validation feature of batch job.xml file. Manipulate with xml file via source view and check its functionality resulting in Problems View. > Add new batch integration UI tests for validating the source in job.xml file > ---------------------------------------------------------------------------- > > Key: JBIDE-23728 > URL: https://issues.jboss.org/browse/JBIDE-23728 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: qa > Affects Versions: 4.4.2.AM1 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Labels: batch, integration-test > Fix For: 4.4.3.AM2 > > > Implement integration ui tests for validation feature of batch job.xml file. Manipulate with xml file via source view and check its functionality resulting in Problems View. > 1. Ref element contains valid name of specific artifact > 2. Properties link to valid java field of #jobProperties["xyz"] > 3. Id is unique > 4. Attributes next and to refer to id of step | split | flow | decision at the same level as the current execution element > 5. Attributes 'flow/stop/@restart', 'step/stop/@restart' should refer to id of step | split | flow | decision at the job level > 6. Sequence of execution elements defined by @next and @to should not loop. > 7. Value of attribute 'include/@class' and 'exclude/@class' is qualified name of an exception class. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23728) Add new batch integration UI tests for validating the source in job.xml file

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23728?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-23728: ---------------------------------- Description: Implement integration ui tests for validation feature of batch job.xml file. Manipulate with xml file via source tab and check its functionality resulting in Problems View. 1. Ref element contains valid name of specific artifact 2. Properties link to valid java field of #jobProperties["xyz"] 3. Id is unique 4. Attributes next and to refer to id of step | split | flow | decision at the same level as the current execution element 5. Attributes 'flow/stop/@restart', 'step/stop/@restart' should refer to id of step | split | flow | decision at the job level 6. Sequence of execution elements defined by @next and @to should not loop. 7. Value of attribute 'include/@class' and 'exclude/@class' is qualified name of an exception class. was: Implement integration ui tests for validation feature of batch job.xml file. Manipulate with xml file via source view and check its functionality resulting in Problems View. 1. Ref element contains valid name of specific artifact 2. Properties link to valid java field of #jobProperties["xyz"] 3. Id is unique 4. Attributes next and to refer to id of step | split | flow | decision at the same level as the current execution element 5. Attributes 'flow/stop/@restart', 'step/stop/@restart' should refer to id of step | split | flow | decision at the job level 6. Sequence of execution elements defined by @next and @to should not loop. 7. Value of attribute 'include/@class' and 'exclude/@class' is qualified name of an exception class. > Add new batch integration UI tests for validating the source in job.xml file > ---------------------------------------------------------------------------- > > Key: JBIDE-23728 > URL: https://issues.jboss.org/browse/JBIDE-23728 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: qa > Affects Versions: 4.4.2.AM1 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Labels: batch, integration-test > Fix For: 4.4.3.AM2 > > > Implement integration ui tests for validation feature of batch job.xml file. Manipulate with xml file via source tab and check its functionality resulting in Problems View. > 1. Ref element contains valid name of specific artifact > 2. Properties link to valid java field of #jobProperties["xyz"] > 3. Id is unique > 4. Attributes next and to refer to id of step | split | flow | decision at the same level as the current execution element > 5. Attributes 'flow/stop/@restart', 'step/stop/@restart' should refer to id of step | split | flow | decision at the job level > 6. Sequence of execution elements defined by @next and @to should not loop. > 7. Value of attribute 'include/@class' and 'exclude/@class' is qualified name of an exception class. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22969) Make sure OpenShift Tools support proxies

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22969?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-22969: ------------------------------------- Sprint: devex #123 November 2016, devex #126 January 2017 (was: devex #123 November 2016) > Make sure OpenShift Tools support proxies > ----------------------------------------- > > Key: JBIDE-22969 > URL: https://issues.jboss.org/browse/JBIDE-22969 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Reporter: Alexey Kazakov > Assignee: Dmitrii Bocharov > Fix For: 4.4.3.AM2 > > Attachments: proxy_settings.png, proxy_settings_2.png > > > CDK is now support proxy servers. We also should make sure OpenShift Tools works fine with proxies too. > If devstudio and cdk are installed using DevSuite installer and user configured proxy server correctly then everything should just work on Eclipse side. > This issue covers: > - testing > - creating all needed (currently missing) automated tests (including reddeer/swt bot Integration Tests) > - fixing any problems we have in OpenShift tooling regarding proxy support. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23728) Add new batch integration UI tests for validating the source in job.xml file

by Ondrej Dockal (JIRA)

Ondrej Dockal created JBIDE-23728: ------------------------------------- Summary: Add new batch integration UI tests for validating the source in job.xml file Key: JBIDE-23728 URL: https://issues.jboss.org/browse/JBIDE-23728 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: qa Affects Versions: 4.4.2.AM1 Reporter: Ondrej Dockal Assignee: Ondrej Dockal Fix For: 4.4.3.AM2 Implement integration ui tests for validation feature of batch job.xml file. Manipulate with xml file via source view and check its functionality resulting in Problems View. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22613) Connection wizard: When a connection is configured with a stored token, switching back with basic will fail if token is invalid

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22613?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-22613: ------------------------------------- Sprint: devex #123 November 2016 (was: devex #123 November 2016, devex #126 January 2017) > Connection wizard: When a connection is configured with a stored token, switching back with basic will fail if token is invalid > ------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22613 > URL: https://issues.jboss.org/browse/JBIDE-22613 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Jeff MAURY > Assignee: Dmitrii Bocharov > Labels: connection, connection_wizard, openshift_v3 > Fix For: 4.4.3.AM2 > > > If an Openshift is configured with a OAuth and a stored token, if you want to switch back to basic, the connection will fail because the connection is still made using Oauth -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23136) Deploy Docker Wizard: Pushing image to CDK registry results in an image with no tag

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23136?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-23136: ------------------------------------- Sprint: devex #123 November 2016, devex #126 January 2017 (was: devex #123 November 2016, devex #125 December 2016) > Deploy Docker Wizard: Pushing image to CDK registry results in an image with no tag > ----------------------------------------------------------------------------------- > > Key: JBIDE-23136 > URL: https://issues.jboss.org/browse/JBIDE-23136 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.Final > Reporter: Marián Labuda > Assignee: Dmitrii Bocharov > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.4.3.AM2 > > Attachments: eap64-basic-s2i-new-app-from-cli-1.png, eap64-basic-s2i-new-app-from-jbosstools-1.png, local-docker-images-after-pull-1.png > > > I have a docker connection to local docker daemon and a CDK docker connection. I am pushing an image from a docker connection to CDK registry via Deploy Image to OpenShift wizard. Push of an image pass, but it results into an image with no tag, see: > 172.30.192.49:5000/msa/msa <none> 238200ae067d 4 months ago 1.05 GB > Such images are not shown in docker explorer under a docker connection because of upstream bug ERT-411 > Steps to reproduce: > - have a project with a file named {{Dockerfile}} with the following content (1 line): > {code} > FROM fedora:latest > {code} > - Select the file in the project explorer, then {{Run As > Docker Image Build}}. Use the CDK connection and give it a name (eg: {{username/fedora}}) > - Select the image in the Docker Explorer view, then {{Deploy to OpenShift}}. > - In the wizard, select the option to push the image to the registry (add a dummy port if needed) > - once the operation completed, there's an unexpected image named like {{172.30.164.33:5000/<project>/fedora}} in the output of the {{docker images}} command (in CLI) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22613) Connection wizard: When a connection is configured with a stored token, switching back with basic will fail if token is invalid

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22613?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-22613: ------------------------------------- Sprint: devex #123 November 2016, devex #126 January 2017 (was: devex #123 November 2016, devex #125 December 2016) > Connection wizard: When a connection is configured with a stored token, switching back with basic will fail if token is invalid > ------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22613 > URL: https://issues.jboss.org/browse/JBIDE-22613 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Jeff MAURY > Assignee: Dmitrii Bocharov > Labels: connection, connection_wizard, openshift_v3 > Fix For: 4.4.3.AM2 > > > If an Openshift is configured with a OAuth and a stored token, if you want to switch back to basic, the connection will fail because the connection is still made using Oauth -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 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 January 2017