September 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-22319) Make OpenshiftServer implement IConnectionFacade

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22319?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-22319: ----------------------------------- Assignee: (was: Fred Bricon) > Make OpenshiftServer implement IConnectionFacade > ------------------------------------------------ > > Key: JBIDE-22319 > URL: https://issues.jboss.org/browse/JBIDE-22319 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Reporter: Thomas Mäder > Fix For: 4.4.2.AM1 > > > Add support for having a jmx conection via JBoss remoting to OpenShiftServer. > * need to add jmx client library > * find out the correct url > * configure deployment config with necessary env, ports, etc. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22581) Create and use Neon.1 target platform

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22581?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-22581: ------------------------------------ fetch mirror of tm 4.1.0.201606052351 > Create and use Neon.1 target platform > ------------------------------------- > > Key: JBIDE-22581 > URL: https://issues.jboss.org/browse/JBIDE-22581 > Project: Tools (JBoss Tools) > Issue Type: Component Upgrade > Components: target-platform > Affects Versions: 4.4.1.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.4.2.AM1 > > > Once available in late August or early September, we should move up to Neon.1. > https://wiki.eclipse.org/index.php?title=Neon/Simultaneous_Release_Plan#S... > Story points: 21 (fibonacci) > jbt tp, > jbds tp, > central tp; > jbt-build-sites, > jbds site build; > update install/matrix jobs to use new Eclipse JEE/platform binary; > mailing list announcements -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22581) Create and use Neon.1 target platform

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22581?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-22581: ------------------------------------ fetch mirror of webtools R3.8.1/R-3.8.1-20160912100321 > Create and use Neon.1 target platform > ------------------------------------- > > Key: JBIDE-22581 > URL: https://issues.jboss.org/browse/JBIDE-22581 > Project: Tools (JBoss Tools) > Issue Type: Component Upgrade > Components: target-platform > Affects Versions: 4.4.1.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.4.2.AM1 > > > Once available in late August or early September, we should move up to Neon.1. > https://wiki.eclipse.org/index.php?title=Neon/Simultaneous_Release_Plan#S... > Story points: 21 (fibonacci) > jbt tp, > jbds tp, > central tp; > jbt-build-sites, > jbds site build; > update install/matrix jobs to use new Eclipse JEE/platform binary; > mailing list announcements -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23203) For JBIDE 4.4.2.AM1: Prepare for 4.4.2.AM1 / 10.2.0.AM1 [LiveReload]

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23203?page=com.atlassian.jira.plugi... ] Xavier Coulon closed JBIDE-23203. --------------------------------- Resolution: Done closed after bumping component version > For JBIDE 4.4.2.AM1: Prepare for 4.4.2.AM1 / 10.2.0.AM1 [LiveReload] > -------------------------------------------------------------------- > > Key: JBIDE-23203 > URL: https://issues.jboss.org/browse/JBIDE-23203 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: livereload > Reporter: Friendly Jira Robot > Assignee: Xavier Coulon > Priority: Blocker > Labels: task > Fix For: 4.4.2.AM1 > > > For JBIDE 4.4.2.AM1 [LiveReload]: 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 LiveReload 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-23191) For JBIDE 4.4.2.AM1: Prepare for 4.4.2.AM1 / 10.2.0.AM1 [Server]

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23191?page=com.atlassian.jira.plugi... ] Alexey Kazakov closed JBIDE-23191. ---------------------------------- Resolution: Done [~rob.stryker] please do not forget to resolve issue when done. Resolving and closing. > For JBIDE 4.4.2.AM1: Prepare for 4.4.2.AM1 / 10.2.0.AM1 [Server] > ---------------------------------------------------------------- > > Key: JBIDE-23191 > URL: https://issues.jboss.org/browse/JBIDE-23191 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: server > Reporter: Friendly Jira Robot > Assignee: Rob Stryker > Priority: Blocker > Labels: task > Fix For: 4.4.2.AM1 > > > For JBIDE 4.4.2.AM1 [Server]: 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 Server 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-23192) For JBIDE 4.4.2.AM1: Prepare for 4.4.2.AM1 / 10.2.0.AM1 [Hibernate]

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23192?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-23192: ---------------------------------- Assignee: Jeff MAURY (was: Koen Aers) > For JBIDE 4.4.2.AM1: Prepare for 4.4.2.AM1 / 10.2.0.AM1 [Hibernate] > ------------------------------------------------------------------- > > Key: JBIDE-23192 > URL: https://issues.jboss.org/browse/JBIDE-23192 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: hibernate > Reporter: Friendly Jira Robot > Assignee: Jeff MAURY > Priority: Blocker > Labels: task > Fix For: 4.4.2.AM1 > > > For JBIDE 4.4.2.AM1 [Hibernate]: 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 Hibernate 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-23199) For JBIDE 4.4.2.AM1: Prepare for 4.4.2.AM1 / 10.2.0.AM1 [Webservices]

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23199?page=com.atlassian.jira.plugi... ] Xavier Coulon closed JBIDE-23199. --------------------------------- Resolution: Done Bumped component version to 1.9.2 > For JBIDE 4.4.2.AM1: Prepare for 4.4.2.AM1 / 10.2.0.AM1 [Webservices] > --------------------------------------------------------------------- > > Key: JBIDE-23199 > URL: https://issues.jboss.org/browse/JBIDE-23199 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: webservices > Reporter: Friendly Jira Robot > Assignee: Jeff MAURY > Priority: Blocker > Labels: task > Fix For: 4.4.2.AM1 > > > For JBIDE 4.4.2.AM1 [Webservices]: 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 Webservices 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-23209) Notify PR associated users, when CI build for the PR fails

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23209?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23209: ------------------------------------ enable email spam for failed PRs in the dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/DevStudio-Pull-... jobs > Notify PR associated users, when CI build for the PR fails > ---------------------------------------------------------- > > Key: JBIDE-23209 > URL: https://issues.jboss.org/browse/JBIDE-23209 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Reporter: Dmitrii Bocharov > Assignee: Nick Boldt > Priority: Minor > > Create Jenkins hook, which will notify people involved in the commits that build is failing and notifying them back when build is back to ok -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22626) Updating deployed docker image on OpenShift does not work

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22626?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-22626: --------------------------------------- I'm not certain the expectation here is properly framed. I believe you are asking why the image does not get redeployed when a new image is available. Based upon the sample provided: {code} from: kind: ImageStreamTag namespace: sample-project name: 'aloha:0.1' {code} A new deployment will only occur if you push a new image that has the tag 'aloha:0.1'. It looks as though you are expecting that pushing a new tag (e.g. 0.2) will produce a new deployment. This is not the case. You will need to either update the name to be 'aloha:latest' and push a new image or edit the name to the desired tag > Updating deployed docker image on OpenShift does not work > --------------------------------------------------------- > > Key: JBIDE-22626 > URL: https://issues.jboss.org/browse/JBIDE-22626 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Marián Labuda > Assignee: Dmitrii Bocharov > Priority: Critical > Labels: docker, openshift_v3 > Fix For: 4.4.2.AM1 > > Attachments: ImageStreamTags.jpg > > > In JBIDE-22515 was fixed use case when user have an image with specific tag. That works now ok. > But if user deploys image with tag e.g. :0.8 to OpenShift, resources are created for this specific tag. When I am trying to Deploy to OS image with tag :0.9 afterwards, everything finish without an error. No new resources are created, but no existing resources are modified to contain this new image. Deployment config still contains tag :0.8 and thus new deployment is not done. > Basically we need to modify deployment config in such cases to contains newer tag and let OpenShift do all magic and redeploy it. > In order to add this version tag after semicolon, right-click on the image -> Add tag -> Re-type namespace/imagename + add ":0.8" e.g. > Tagging Images: https://docs.openshift.com/enterprise/latest/dev_guide/managing_images.ht... > Image Change Trigger: https://docs.openshift.com/enterprise/latest/dev_guide/deployments.html#i... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23182) NullPointerException in PodLogsHandler.handleEvent

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23182?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-23182: ----------------------------------------------- Ok, then we need a helper that performs this chain of calls checking each object for null. The reporting bot is very keen at catching failures that may happen at closing Eclipse, which are quite rare for a user who is not likely to close Eclipse one millisecond after he calls a menu action, but that is the very likely thing for a bot to do. > NullPointerException in PodLogsHandler.handleEvent > -------------------------------------------------- > > Key: JBIDE-23182 > URL: https://issues.jboss.org/browse/JBIDE-23182 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Automated Error Reporting Bot > > The following problem was reported via the automated error reporting: > Message: Unhandled event loop exception > {noformat} > java.lang.NullPointerException: null > at org.jboss.tools.openshift.internal.ui.handler.PodLogsHandler.handleEvent(PodLogsHandler.java:46) > at org.jboss.tools.openshift.internal.ui.handler.AbstractOpenShiftCliHandler.execute(AbstractOpenShiftCliHandler.java:70) > at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:295) > at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90) > at sun.reflect.NativeMethodAccessorImpl.invoke0(null:-2) > at sun.reflect.NativeMethodAccessorImpl.invoke(null:-1) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(null:-1) > at java.lang.reflect.Method.invoke(null:-1) > at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:54) > {noformat} > Bundles: > | org.eclipse.e4.core.di | 1.6.0.v20160319-0612 | 1.6.0.v20160319-0612 | > | org.eclipse.ui | 3.108.0.v20160518-1929 | 3.108.0.v20160518-1929 | > | org.jboss.tools.openshift.ui | 3.3.0.v20160831-0703 | 3.3.0.v20160831-0703 | > Operating Systems: > | Windows | 10.0.0 | 10.0.0 | > The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/57d6df25e4b0fd7621...] for the latest data. > Thank you for your assistance. > Your friendly error-reports-inbox. -- 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