September 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-23057) Integration tests: test import project in server adapter wizard

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23057?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23057: ------------------------------------- Sprint: devex #121 October 2016 (was: devex #120 September 2016) > Integration tests: test import project in server adapter wizard > --------------------------------------------------------------- > > Key: JBIDE-23057 > URL: https://issues.jboss.org/browse/JBIDE-23057 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.4.2.AM2 > > > JBIDE-22621 allows the user to import a project in the server adapter wizard. We should add an integration test for this scenarion in CreateServerAdapterTest -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22914) OpenShift Deployment: Deploy latest does not work correctly

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22914?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22914: ------------------------------------- Fix Version/s: 4.4.2.AM2 (was: 4.4.2.AM1) > OpenShift Deployment: Deploy latest does not work correctly > ----------------------------------------------------------- > > Key: JBIDE-22914 > URL: https://issues.jboss.org/browse/JBIDE-22914 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Marián Labuda > Labels: openshift_v3 > Fix For: 4.4.2.AM2 > > > When I have an application where no replication controller is yet and I want to deploy latest, I get following error: > {code} > Unable to perform a deployment for config hello-openshift > com.openshift.restclient.NotFoundException: replicationcontrollers "hello-openshift-0" not found > at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.createOpenShiftException(ResponseCodeInterceptor.java:105) > at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.intercept(ResponseCodeInterceptor.java:59) > at okhttp3.RealCall$ApplicationInterceptorChain.proceed(RealCall.java:190) > at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.java:163) > at okhttp3.RealCall.execute(RealCall.java:57) > at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:200) > at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:181) > at com.openshift.internal.restclient.DefaultClient.get(DefaultClient.java:269) > at com.openshift.internal.restclient.capability.resources.DeployCapability.deploy(DeployCapability.java:59) > at org.jboss.tools.openshift.internal.ui.handler.TriggerDeploymentHandler$1$1.visit(TriggerDeploymentHandler.java:90) > at org.jboss.tools.openshift.internal.ui.handler.TriggerDeploymentHandler$1$1.visit(TriggerDeploymentHandler.java:1) > at com.openshift.internal.restclient.model.KubernetesResource.accept(KubernetesResource.java:91) > at org.jboss.tools.openshift.internal.ui.handler.TriggerDeploymentHandler$1.doRun(TriggerDeploymentHandler.java:85) > at org.jboss.tools.openshift.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:37) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {code} > This is wrong, because it is trying to "deploy latest replication controller" instead of deploying latest deployment configuration (as it works e.g. from oc binary - deployment uses latest deployment configuration not replication controller which could be understood as instance of deployment configuration). Therefore if there is no replication controller and I click Deploy Latest in context menu of a service in OpenShift Explorer view or in context menu of a deployment configuration in properties view, I get the error. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23091) use #close smart tag in commit messages so JIRAs are closed automatically

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23091?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23091: ------------------------------------ Turns out the problem is that my github commits were coming in as nickboldt@gmail, but my login in JIRA was nboldt@redhat. Fixed that and I can now change JIRA workflow states w/ smart commits. Details: https://issues.jboss.org/browse/JIRA-471?focusedCommentId=13297868&page=c... > use #close smart tag in commit messages so JIRAs are closed automatically > ------------------------------------------------------------------------- > > Key: JBIDE-23091 > URL: https://issues.jboss.org/browse/JBIDE-23091 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.2.AM1 > > > Rather than having to create and bulk-close 17 JIRAs, we should use smart commit msgs that cause JIRA workflow to close JIRAs automatically -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23262) Issue warnings about snapshot deps for all AMx milestones (not just AM3)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23262?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23262: ------------------------------------ smart commit comment test - will this actually resolve the issue? > Issue warnings about snapshot deps for all AMx milestones (not just AM3) > ------------------------------------------------------------------------ > > Key: JBIDE-23262 > URL: https://issues.jboss.org/browse/JBIDE-23262 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.2.AM1 > Reporter: Jeff MAURY > Assignee: Nick Boldt > Labels: build, parent > Fix For: 4.4.2.AM1 > > > The parent POM is configured to issue warnings when SNAPSHOT dependencies when build alias matches AM3 but it should match AM1, AM2 as well -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23262) Issue warnings about snapshot deps for all AMx milestones (not just AM3)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23262?page=com.atlassian.jira.plugi... ] Nick Boldt resolved JBIDE-23262. -------------------------------- Resolution: Done > Issue warnings about snapshot deps for all AMx milestones (not just AM3) > ------------------------------------------------------------------------ > > Key: JBIDE-23262 > URL: https://issues.jboss.org/browse/JBIDE-23262 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.2.AM1 > Reporter: Jeff MAURY > Assignee: Nick Boldt > Labels: build, parent > Fix For: 4.4.2.AM1 > > > The parent POM is configured to issue warnings when SNAPSHOT dependencies when build alias matches AM3 but it should match AM1, AM2 as well -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23262) Issue warnings about snapshot deps for all AMx milestones (not just AM3)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23262?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23262: ------------------------------------ smart commit comment test - will this actually reopen the issue? > Issue warnings about snapshot deps for all AMx milestones (not just AM3) > ------------------------------------------------------------------------ > > Key: JBIDE-23262 > URL: https://issues.jboss.org/browse/JBIDE-23262 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.2.AM1 > Reporter: Jeff MAURY > Assignee: Nick Boldt > Labels: build, parent > Fix For: 4.4.2.AM1 > > > The parent POM is configured to issue warnings when SNAPSHOT dependencies when build alias matches AM3 but it should match AM1, AM2 as well -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23262) Issue warnings about snapshot deps for all AMx milestones (not just AM3)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23262?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23262: ------------------------------------ smart commit comment test - will this actually close the issue? > Issue warnings about snapshot deps for all AMx milestones (not just AM3) > ------------------------------------------------------------------------ > > Key: JBIDE-23262 > URL: https://issues.jboss.org/browse/JBIDE-23262 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.2.AM1 > Reporter: Jeff MAURY > Assignee: Nick Boldt > Labels: build, parent > Fix For: 4.4.2.AM1 > > > The parent POM is configured to issue warnings when SNAPSHOT dependencies when build alias matches AM3 but it should match AM1, AM2 as well -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23262) Issue warnings about snapshot deps for all AMx milestones (not just AM3)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23262?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-23262. ------------------------------ > Issue warnings about snapshot deps for all AMx milestones (not just AM3) > ------------------------------------------------------------------------ > > Key: JBIDE-23262 > URL: https://issues.jboss.org/browse/JBIDE-23262 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.2.AM1 > Reporter: Jeff MAURY > Assignee: Nick Boldt > Labels: build, parent > Fix For: 4.4.2.AM1 > > > The parent POM is configured to issue warnings when SNAPSHOT dependencies when build alias matches AM3 but it should match AM1, AM2 as well -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23189) For JBIDE 4.4.2.AM1: Prepare for 4.4.2.AM1 / 10.2.0.AM1 [Integration Tests]

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23189?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-23189: --------------------------------------- Just confirming that the build works correctly. All good. > For JBIDE 4.4.2.AM1: Prepare for 4.4.2.AM1 / 10.2.0.AM1 [Integration Tests] > --------------------------------------------------------------------------- > > Key: JBIDE-23189 > URL: https://issues.jboss.org/browse/JBIDE-23189 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: qa > Reporter: Friendly Jira Robot > Assignee: Len DiMaggio > Priority: Blocker > Labels: task > Fix For: 4.4.2.AM1 > > > For JBIDE 4.4.2.AM1 [Integration Tests]: Please perform the following tasks: > 1. Check out your existing *{color:orange}master{color}* branch: > {code} > git checkout master > {code} > 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.2.AM1-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.2.AM1-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:orange}4.4.2.AM1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.25.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.1.Final > {code} > mvn clean verify -Dtpc.version=4.60.1.Final > {code} > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.60.1.Final > {code} > mvn clean verify -Dtpc.version=4.60.1.Final > {code} > 5. Close (do not resolve) this JIRA when done. > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Integration Tests task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23189) For JBIDE 4.4.2.AM1: Prepare for 4.4.2.AM1 / 10.2.0.AM1 [Integration Tests]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23189?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-23189. ------------------------------ Resolution: Done Yes, it's the same version so closing. Unless your build's been red for 15 days, you should be fine here. :D > For JBIDE 4.4.2.AM1: Prepare for 4.4.2.AM1 / 10.2.0.AM1 [Integration Tests] > --------------------------------------------------------------------------- > > Key: JBIDE-23189 > URL: https://issues.jboss.org/browse/JBIDE-23189 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: qa > Reporter: Friendly Jira Robot > Assignee: Len DiMaggio > Priority: Blocker > Labels: task > Fix For: 4.4.2.AM1 > > > For JBIDE 4.4.2.AM1 [Integration Tests]: Please perform the following tasks: > 1. Check out your existing *{color:orange}master{color}* branch: > {code} > git checkout master > {code} > 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.2.AM1-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.2.AM1-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:orange}4.4.2.AM1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.25.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.1.Final > {code} > mvn clean verify -Dtpc.version=4.60.1.Final > {code} > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.60.1.Final > {code} > mvn clean verify -Dtpc.version=4.60.1.Final > {code} > 5. Close (do not resolve) this JIRA when done. > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Integration Tests task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 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 September 2016