August 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24870) switch to new Oxygen baselines & update plugin/feature versions accordingly

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24870?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24870: ------------------------------- Fix Version/s: 4.5.1.AM1 > switch to new Oxygen baselines & update plugin/feature versions accordingly > --------------------------------------------------------------------------- > > Key: JBIDE-24870 > URL: https://issues.jboss.org/browse/JBIDE-24870 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.5.1.AM1 > Reporter: Nick Boldt > Fix For: 4.5.1.AM1 > > > When I apply this PR, we'll be comparing our latest build against the Oxygen release, not the old Neon one. > As such, features and plugins will need to be bumped. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24870) switch to new Oxygen baselines & update plugin/feature versions accordingly

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24870?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-24870: ---------------------------------- Assignee: Nick Boldt > switch to new Oxygen baselines & update plugin/feature versions accordingly > --------------------------------------------------------------------------- > > Key: JBIDE-24870 > URL: https://issues.jboss.org/browse/JBIDE-24870 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.5.1.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.1.AM1 > > > When I apply this PR, we'll be comparing our latest build against the Oxygen release, not the old Neon one. > As such, features and plugins will need to be bumped. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24870) switch to new Oxygen baselines & update plugin/feature versions accordingly

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-24870: ---------------------------------- Summary: switch to new Oxygen baselines & update plugin/feature versions accordingly Key: JBIDE-24870 URL: https://issues.jboss.org/browse/JBIDE-24870 Project: Tools (JBoss Tools) Issue Type: Bug Components: build Affects Versions: 4.5.1.AM1 Reporter: Nick Boldt When I apply this PR, we'll be comparing our latest build against the Oxygen release, not the old Neon one. As such, features and plugins will need to be bumped. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24868) Switch off livenessProbe.periodSecond property during debug session

by Roland Huß (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24868?page=com.atlassian.jira.plugi... ] Roland Huß commented on JBIDE-24868: ------------------------------------ Actually, a request timeout is another source of 'killed' debug session, when you are debugging a synchronous web request. The liveness-check however also kills sessions which are debugging async processing of business logic within an app. One could prevent a router timeout by going directly to the Service (e.g. via nodePort) or even the Pod (oc port-forward), as I currently haven't found an easy way to adapt the router timeout temporarily (and might e.g. not even possible when being in the cloud). > Switch off livenessProbe.periodSecond property during debug session > ------------------------------------------------------------------- > > Key: JBIDE-24868 > URL: https://issues.jboss.org/browse/JBIDE-24868 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Reporter: Aurélien Pupier > > it will avoid to have "debug connections always killed after 30s staying in a breakpoint" > see https://twitter.com/ro14nd/status/895886024387067904 for source of suggestion -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24854) For JBIDE 4.5.1.AM1: Prepare for 4.5.1.AM1 / 11.1.0.AM1 [fusetools]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24854?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-24854 at 8/11/17 12:04 PM: -------------------------------------------------------------- Well, that's just wrong. I guess I forgot to update your fusesource jenkins job. Can you fix that? You should be using TP version 4.70.2.Final for now. was (Author: nickboldt): Well, that's just wrong. I guess I forgot to update your fusesource jenkins job. Can you fix that? > For JBIDE 4.5.1.AM1: Prepare for 4.5.1.AM1 / 11.1.0.AM1 [fusetools] > ------------------------------------------------------------------- > > Key: JBIDE-24854 > URL: https://issues.jboss.org/browse/JBIDE-24854 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: fusetools > Reporter: Nick Boldt > Assignee: Lars Heinemann > Priority: Blocker > Labels: task > Fix For: 4.5.1.AM1 > > > For JBIDE 4.5.1.AM1 [fusetools]: 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.5.1.AM1-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.5.1.AM1-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.5.1.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.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > > > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.70.2.Final > > {code} > mvn clean verify -Dtpc.version=4.70.2.Final > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.70.2.Final > > {code} > mvn clean verify -Dtpc.version=4.70.2.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 fusetools task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24854) For JBIDE 4.5.1.AM1: Prepare for 4.5.1.AM1 / 11.1.0.AM1 [fusetools]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24854?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24854: ------------------------------------ Well, that's just wrong. I guess I forgot to update your fusesource jenkins job. Can you fix that? > For JBIDE 4.5.1.AM1: Prepare for 4.5.1.AM1 / 11.1.0.AM1 [fusetools] > ------------------------------------------------------------------- > > Key: JBIDE-24854 > URL: https://issues.jboss.org/browse/JBIDE-24854 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: fusetools > Reporter: Nick Boldt > Assignee: Lars Heinemann > Priority: Blocker > Labels: task > Fix For: 4.5.1.AM1 > > > For JBIDE 4.5.1.AM1 [fusetools]: 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.5.1.AM1-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.5.1.AM1-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.5.1.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.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > > > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.70.2.Final > > {code} > mvn clean verify -Dtpc.version=4.70.2.Final > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.70.2.Final > > {code} > mvn clean verify -Dtpc.version=4.70.2.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 fusetools task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24868) Switch off livenessProbe.periodSecond property during debug session

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24868?page=com.atlassian.jira.plugi... ] Aurélien Pupier commented on JBIDE-24868: ----------------------------------------- Jeff mentioned that the current "workaround" used is to "increase the timeout for request in the router" > Switch off livenessProbe.periodSecond property during debug session > ------------------------------------------------------------------- > > Key: JBIDE-24868 > URL: https://issues.jboss.org/browse/JBIDE-24868 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Reporter: Aurélien Pupier > > it will avoid to have "debug connections always killed after 30s staying in a breakpoint" > see https://twitter.com/ro14nd/status/895886024387067904 for source of suggestion -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24869) Server adapter: add tests for debugging, docker image metadata retrieval etc.

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-24869: ---------------------------------------- Summary: Server adapter: add tests for debugging, docker image metadata retrieval etc. Key: JBIDE-24869 URL: https://issues.jboss.org/browse/JBIDE-24869 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 4.5.0.AM1 Reporter: Andre Dietisheim In JBIDE-24184 server adapters were refactored and reading docker image metadata to enable/disable devmode and debugging was added. Tests should now get adapted and added to assert the current implementation. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24783) Update default registry url for cdk 3

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24783?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-24783: --------------------------------------- [~adietish] I agree with you. And also, if the registry command fails, that should probably produce an error message in the tooling. > Update default registry url for cdk 3 > ------------------------------------- > > Key: JBIDE-24783 > URL: https://issues.jboss.org/browse/JBIDE-24783 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdk, openshift > Affects Versions: 4.5.0.AM2 > Reporter: Martin Malina > > Yesterday I started cdk 3 and it seemed to start ok, but was not really ok. > The registry command didn't really work: > {code} > $ ./minishift openshift registry > No information found for 'service/docker-registry' > {code} > The result is that the openshift connection details showed this under Image Registry URL: > https://hub.openshift.rhel-cdk.10.1.2.2.xip.io > This seems like the default value for cdk 2. I think we should update the default value for cdk 3. Or is this simply a default value for an openshift connection? In any case, this should use the cdk 3 value. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24783) Update default registry url for cdk 3

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24783?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-24783: ---------------------------------- Description: Yesterday I started cdk 3 and it seemed to start ok, but was not really ok. The registry command didn't really work: {code} $ ./minishift openshift registry No information found for 'service/docker-registry' {code} The result is that the openshift connection details showed this under Image Registry URL: https://hub.openshift.rhel-cdk.10.1.2.2.xip.io This seems like the default value for cdk 2. I think we should update the default value for cdk 3. Or is this simply a default value for an openshift connection? In any case, this should use the cdk 3 value. was: Yesterday I started cdk 3 and it seemed to start ok, but was not really ok. The registry command didn't really work: {code} $ ./minishift openshift registry No information found for 'service/docker-registry' {code} The result is that the openshift connection details showed this under Image Registry URL: https://hub.openshift.rhel-cdk.10.1.2.2.xip.io This seems like the default value for cdk 3. I think we should update the default value for cdk 3. Or is this simply a default value for an openshift connection? In any case, this should use the cdk 3 value. > Update default registry url for cdk 3 > ------------------------------------- > > Key: JBIDE-24783 > URL: https://issues.jboss.org/browse/JBIDE-24783 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdk, openshift > Affects Versions: 4.5.0.AM2 > Reporter: Martin Malina > > Yesterday I started cdk 3 and it seemed to start ok, but was not really ok. > The registry command didn't really work: > {code} > $ ./minishift openshift registry > No information found for 'service/docker-registry' > {code} > The result is that the openshift connection details showed this under Image Registry URL: > https://hub.openshift.rhel-cdk.10.1.2.2.xip.io > This seems like the default value for cdk 2. I think we should update the default value for cdk 3. Or is this simply a default value for an openshift connection? In any case, this should use the cdk 3 value. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 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 August 2017