June 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22605) Remote server with fs operations sometimes cannot be stopped

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22605?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-22605: ------------------------------------- There is no problem with a .undeployed marker sitting there. That is fine and expected under most cases. The .undeployed marker also shouldn't intefere with shutdown at all. The other issue seems to be we don't add the .dodeploy all the time (?), but my tests seem to show we do. I'll keep invetigating. > Remote server with fs operations sometimes cannot be stopped > ------------------------------------------------------------ > > Key: JBIDE-22605 > URL: https://issues.jboss.org/browse/JBIDE-22605 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.4.0.Final > Reporter: Martin Malina > Assignee: Rob Stryker > > Yesterday when we were found out that remote servers don't work with management operations (JBIDE-22601) I wanted to check if at least FS operations work. > In one instance of Eclipse, stopping such server didn't work. > But then I tried in devstudio and it worked, so I assumed it was some glitch. > But today this happened to me again with the latest devstudio 10.0.0.GA B30 build - the one that contains a fix to the above mentioned JIRA. > From several attempts, it seems that this is only reproducible if you deploy a project. If you just start the server and then stop, it will stop just fine. > One more thing, regardless of whether a given server can be stopped or not, I always get this in the Error Log view during server startup: > {code}Unable to retrieve a list of remote deployment scanners for server Red Hat JBoss EAP 7.0 marvin{code} > (Let me know if you want an additional JIRA for that.) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22619) Decide strategy for fixversion targets in JIRA

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22619?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-22619: ------------------------------------ Thought we had agreed to the new plan via conversation in HipChat. But I can revert the change in less time than it takes to type out this comment. Should I revert? > Decide strategy for fixversion targets in JIRA > ---------------------------------------------- > > Key: JBIDE-22619 > URL: https://issues.jboss.org/browse/JBIDE-22619 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.4.1.S116 > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Fix For: 4.4.1.S116 > > > We need to decide the strategy for milestones / fixversions in JIRA. > One suggestion has been to align fixversions w/ sprint numbers, thus: > * 4.4.1.S116, 4.4.1.S117, 4.4.1.S118, 4.4.1.S119, ...? > instead of > * 4.4.1.Alpha1, 4.4.1.Alpha2, 4.4.1.Alpha3, 4.4.1.Beta1, ... ? > Questions/concerns: > * what do we do for unscheduled milestones (4.5.0.Alpha1, 11.0.0.Alpha1) and placeholders (4.4.1.Final, 10.0.1.GA) ? Should we just use Alpha1 or Final/GA until we know which sprint applies? > * whatever schema we adopt has to work with bzira and jiralint > * any other systems that parse JIRA for integration purposes? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22598) Support runtime detection for manual CDK install

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22598?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-22598: ------------------------------------- Waiting for CDK to get jira first. > Support runtime detection for manual CDK install > ------------------------------------------------ > > Key: JBIDE-22598 > URL: https://issues.jboss.org/browse/JBIDE-22598 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdk, runtime-detection > Affects Versions: 4.4.0.Final > Reporter: Martin Malina > Assignee: Rob Stryker > > Right now with CDK 2.1 when you have a manual cdk install (i.e. using cdk.zip and then adding the vagrant box yourself), there will be no .cdk marker, so Runtime Detection will not work. > The only case where Runtime Detection will work is when you use the (as of now Windows-only) suite installer. At that point Runtime Detection will do its thing silently without you noticing. > The way I see it there are two options: > a) Create and upstream issue with CDK and ask them to include a basic .cdk in their zip > b) Make the runtime detection work without .cdk -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22619) Decide strategy for fixversion targets in JIRA

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22619?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-22619: ---------------------------------------- And please Nick, do not change stuff which affects a lot of people like versioning changes in JIRA before it's agreed and properly announced. You have dome it twice already. > Decide strategy for fixversion targets in JIRA > ---------------------------------------------- > > Key: JBIDE-22619 > URL: https://issues.jboss.org/browse/JBIDE-22619 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.4.1.S116 > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Fix For: 4.4.1.S116 > > > We need to decide the strategy for milestones / fixversions in JIRA. > One suggestion has been to align fixversions w/ sprint numbers, thus: > * 4.4.1.S116, 4.4.1.S117, 4.4.1.S118, 4.4.1.S119, ...? > instead of > * 4.4.1.Alpha1, 4.4.1.Alpha2, 4.4.1.Alpha3, 4.4.1.Beta1, ... ? > Questions/concerns: > * what do we do for unscheduled milestones (4.5.0.Alpha1, 11.0.0.Alpha1) and placeholders (4.4.1.Final, 10.0.1.GA) ? Should we just use Alpha1 or Final/GA until we know which sprint applies? > * whatever schema we adopt has to work with bzira and jiralint > * any other systems that parse JIRA for integration purposes? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22619) Decide strategy for fixversion targets in JIRA

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22619?page=com.atlassian.jira.plugi... ] Alexey Kazakov edited comment on JBIDE-22619 at 6/20/16 3:55 PM: ----------------------------------------------------------------- And please Nick, do not change stuff which affects a lot of people like versioning changes in JIRA before it's agreed and properly announced. You have done it twice already. was (Author: akazakov): And please Nick, do not change stuff which affects a lot of people like versioning changes in JIRA before it's agreed and properly announced. You have dome it twice already. > Decide strategy for fixversion targets in JIRA > ---------------------------------------------- > > Key: JBIDE-22619 > URL: https://issues.jboss.org/browse/JBIDE-22619 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.4.1.S116 > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Fix For: 4.4.1.S116 > > > We need to decide the strategy for milestones / fixversions in JIRA. > One suggestion has been to align fixversions w/ sprint numbers, thus: > * 4.4.1.S116, 4.4.1.S117, 4.4.1.S118, 4.4.1.S119, ...? > instead of > * 4.4.1.Alpha1, 4.4.1.Alpha2, 4.4.1.Alpha3, 4.4.1.Beta1, ... ? > Questions/concerns: > * what do we do for unscheduled milestones (4.5.0.Alpha1, 11.0.0.Alpha1) and placeholders (4.4.1.Final, 10.0.1.GA) ? Should we just use Alpha1 or Final/GA until we know which sprint applies? > * whatever schema we adopt has to work with bzira and jiralint > * any other systems that parse JIRA for integration purposes? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22623) Bump openshift-rest-client to 4.1.0-SNAPSHOT

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22623?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22623: -------------------------------- Fix Version/s: 4.4.1.S116 > Bump openshift-rest-client to 4.1.0-SNAPSHOT > -------------------------------------------- > > Key: JBIDE-22623 > URL: https://issues.jboss.org/browse/JBIDE-22623 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.1.S116 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Fix For: 4.4.1.S116 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22623) Bump openshift-rest-client to 4.1.0-SNAPSHOT

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22623?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22623: -------------------------------- Affects Version/s: 4.4.1.S116 > Bump openshift-rest-client to 4.1.0-SNAPSHOT > -------------------------------------------- > > Key: JBIDE-22623 > URL: https://issues.jboss.org/browse/JBIDE-22623 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.1.S116 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Fix For: 4.4.1.S116 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22623) Bump openshift-rest-client to 4.1.0-SNAPSHOT

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22623?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22623: -------------------------------- Story Points: 1 Sprint: devex #116 2016/06/15 - 07/05 > Bump openshift-rest-client to 4.1.0-SNAPSHOT > -------------------------------------------- > > Key: JBIDE-22623 > URL: https://issues.jboss.org/browse/JBIDE-22623 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.1.S116 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Fix For: 4.4.1.S116 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22623) Bump openshift-rest-client to 4.1.0-SNAPSHOT

by Jeff Cantrill (JIRA)

Jeff Cantrill created JBIDE-22623: ------------------------------------- Summary: Bump openshift-rest-client to 4.1.0-SNAPSHOT Key: JBIDE-22623 URL: https://issues.jboss.org/browse/JBIDE-22623 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: openshift Reporter: Jeff Cantrill Assignee: Jeff Cantrill -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-235) Docker registry account allows for non URL server address [EBZ#495076]

by Roland Grunberg (JIRA)

[ https://issues.jboss.org/browse/ERT-235?page=com.atlassian.jira.plugin.sy... ] Roland Grunberg updated ERT-235: -------------------------------- Sprint: devex #116 2016/06/15 - 07/05 > Docker registry account allows for non URL server address [EBZ#495076] > ---------------------------------------------------------------------- > > Key: ERT-235 > URL: https://issues.jboss.org/browse/ERT-235 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Labels: Docker, bzira > > When creating/editing Docker registry accounts, the server address seems rather open instead of URL. Maybe a check on the syntax could be valuable -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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