August 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-161) Should the JBTIS 4.1 target platform include SpringIDE 3.3 instead of 3.2?

by Nick Boldt (JIRA)

Nick Boldt created JBTIS-161: -------------------------------- Summary: Should the JBTIS 4.1 target platform include SpringIDE 3.3 instead of 3.2? Key: JBTIS-161 URL: https://issues.jboss.org/browse/JBTIS-161 Project: JBoss Tools Integration Stack Issue Type: Bug Security Level: Public (Everyone can see) Components: target-platform Affects Versions: 4.1.2 Reporter: Nick Boldt The version of SpringIDE vetted by QE to be included in JBDS 7 Central is Spring IDE 3.3 [1]. [1] http://download.jboss.org/jbosstools/updates/requirements/springide/3.3.0... However, as reported in http://fusesource.com/issues/browse/ECLIPSE-955 Fuse currently depends on Spring IDE 3.2 [2] [2] https://github.com/jbosstools/jbosstools-integration-stack/blob/master/ta... This disconnect may cause problems when co-installing SpringIDE 3.3 from JBDS Central and Fuse (which will bring in SpringIDE 3.2 jars). Therefore, should Central, JBTIS TP 4.1, and Fuse all use the same version of Spring IDE, namely 3.3 instead of 3.2 and 3.3? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2738) Support OpenShift 2.0 features

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-2738?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-2738: ----------------------------- CDW pm_ack: (was: ?) CDW release: (was: ?) > Support OpenShift 2.0 features > ------------------------------ > > Key: JBDS-2738 > URL: https://issues.jboss.org/browse/JBDS-2738 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Max Rydahl Andersen > Assignee: Andre Dietisheim > > OpenShift 2.0 is coming, needs to investigate when that happens and what it implies for eclipse (and eventually Forge) tooling. > This functionallity would need to be added without breaking how we work with current openshift online and openshift enterprise which has 1.x api's. > Opening this issue to track issues related to this (please create subtasks) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2738) Support OpenShift 2.0 features

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2738?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-2738: -------------------------------------- Target Release: (was: 3.0.2.GA) > Support OpenShift 2.0 features > ------------------------------ > > Key: JBDS-2738 > URL: https://issues.jboss.org/browse/JBDS-2738 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Max Rydahl Andersen > Assignee: Andre Dietisheim > > OpenShift 2.0 is coming, needs to investigate when that happens and what it implies for eclipse (and eventually Forge) tooling. > This functionallity would need to be added without breaking how we work with current openshift online and openshift enterprise which has 1.x api's. > Opening this issue to track issues related to this (please create subtasks) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2738) Support OpenShift 2.0 features

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBDS-2738?page=com.atlassian.jira.plugin.... ] Andre Dietisheim reassigned JBDS-2738: -------------------------------------- Assignee: Andre Dietisheim > Support OpenShift 2.0 features > ------------------------------ > > Key: JBDS-2738 > URL: https://issues.jboss.org/browse/JBDS-2738 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Max Rydahl Andersen > Assignee: Andre Dietisheim > > OpenShift 2.0 is coming, needs to investigate when that happens and what it implies for eclipse (and eventually Forge) tooling. > This functionallity would need to be added without breaking how we work with current openshift online and openshift enterprise which has 1.x api's. > Opening this issue to track issues related to this (please create subtasks) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2738) Support OpenShift 2.0 features

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-2738?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-2738: ----------------------------- CDW pm_ack: ? CDW release: ? Target Release: 3.0.2.GA > Support OpenShift 2.0 features > ------------------------------ > > Key: JBDS-2738 > URL: https://issues.jboss.org/browse/JBDS-2738 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Max Rydahl Andersen > > OpenShift 2.0 is coming, needs to investigate when that happens and what it implies for eclipse (and eventually Forge) tooling. > This functionallity would need to be added without breaking how we work with current openshift online and openshift enterprise which has 1.x api's. > Opening this issue to track issues related to this (please create subtasks) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2738) Support OpenShift 2.0 features

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBDS-2738: ----------------------------------------- Summary: Support OpenShift 2.0 features Key: JBDS-2738 URL: https://issues.jboss.org/browse/JBDS-2738 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Max Rydahl Andersen OpenShift 2.0 is coming, needs to investigate when that happens and what it implies for eclipse (and eventually Forge) tooling. This functionallity would need to be added without breaking how we work with current openshift online and openshift enterprise which has 1.x api's. Opening this issue to track issues related to this (please create subtasks) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15380) Show Git Hooks output and reset timeout when a new receiving new output

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15380?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-15380: ------------------------------------------ This is related to JBIDE-14366 in the sense that we need to increase the timeouts when creating applications/pushing to them. The only way to adapt timeouts so far was on a global base. > Show Git Hooks output and reset timeout when a new receiving new output > ----------------------------------------------------------------------- > > Key: JBIDE-15380 > URL: https://issues.jboss.org/browse/JBIDE-15380 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.1.0.Final > Reporter: Mickael Istria > Assignee: Andre Dietisheim > > When pushing to Openshift with JBT, it is very common to get a Timeout because the hooks take too much time to run. > Instead of this simple timeout, I'd rather see: > * The hooks output shown in the commit dialog > * The timeout counting time since the last received output message (by monitoring at the inputStream I guess) instead of counting time since the commit was triggered. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15380) Show Git Hooks output and reset timeout when a new receiving new output

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15380?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-15380: ---------------------------------------- Assignee: Andre Dietisheim > Show Git Hooks output and reset timeout when a new receiving new output > ----------------------------------------------------------------------- > > Key: JBIDE-15380 > URL: https://issues.jboss.org/browse/JBIDE-15380 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.1.0.Final > Reporter: Mickael Istria > Assignee: Andre Dietisheim > > When pushing to Openshift with JBT, it is very common to get a Timeout because the hooks take too much time to run. > Instead of this simple timeout, I'd rather see: > * The hooks output shown in the commit dialog > * The timeout counting time since the last received output message (by monitoring at the inputStream I guess) instead of counting time since the commit was triggered. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15362) Page is just simply rendered in VPE editor

by Yahor Radtsevich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15362?page=com.atlassian.jira.plugi... ] Yahor Radtsevich updated JBIDE-15362: ------------------------------------- Assignee: Yahor Radtsevich > Page is just simply rendered in VPE editor > ------------------------------------------ > > Key: JBIDE-15362 > URL: https://issues.jboss.org/browse/JBIDE-15362 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Visual Page Editor core > Affects Versions: 4.1.0.Final > Reporter: Jiri Peterka > Assignee: Yahor Radtsevich > Fix For: 4.1.1.Final > > Attachments: login-real-page.png, login-vpe-page.png > > > Not sure if this is not supported or if it's a bug. Thing is that page is not rendered with style but only very simple. See real output and output in VPE editor. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15380) Show Git Hooks output and reset timeout when a new receiving new output

by Mickael Istria (JIRA)

Mickael Istria created JBIDE-15380: -------------------------------------- Summary: Show Git Hooks output and reset timeout when a new receiving new output Key: JBIDE-15380 URL: https://issues.jboss.org/browse/JBIDE-15380 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: openshift Affects Versions: 4.1.0.Final Reporter: Mickael Istria When pushing to Openshift with JBT, it is very common to get a Timeout because the hooks take too much time to run. Instead of this simple timeout, I'd rather see: * The hooks output shown in the commit dialog * The timeout counting time since the last received output message (by monitoring at the inputStream I guess) instead of counting time since the commit was triggered. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues August 2013