December 2013 - jbosstools-issues

[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: ------------------------------------------ Turns out that this issue is about the EGit Push dialog still not being able to show the output of the push operation as it comes in - something that our tooling is perfectly capable of doing. > 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 > Fix For: LATER > > > 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 push dialog > * The timeout counting time since the last received output message (by monitoring at the inputStream I guess) instead of counting time since the push 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

12 years, 4 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)

[ https://issues.jboss.org/browse/JBIDE-15380?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-15380: ---------------------------------------- This is more specific to the EGit dialog, and related bug for Eclipse is https://bugs.eclipse.org/bugs/show_bug.cgi?id=418653 > 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 > Fix For: LATER > > > 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 push dialog > * The timeout counting time since the last received output message (by monitoring at the inputStream I guess) instead of counting time since the push 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

12 years, 4 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 updated JBIDE-15380: ------------------------------------- Description: 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 push dialog * The timeout counting time since the last received output message (by monitoring at the inputStream I guess) instead of counting time since the push was triggered. was: 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 push 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. > 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 > Fix For: LATER > > > 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 push dialog > * The timeout counting time since the last received output message (by monitoring at the inputStream I guess) instead of counting time since the push 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

12 years, 4 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 updated JBIDE-15380: ------------------------------------- Description: 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 push 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. was: 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. > 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 > Fix For: LATER > > > 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 push 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

12 years, 4 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 updated JBIDE-15380: ------------------------------------- Fix Version/s: LATER (was: 4.2.x) > 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 > Fix For: LATER > > > 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

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12106) JAX-RS RESTful explorer out of sync

by Radoslav Rábara (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12106?page=com.atlassian.jira.plugi... ] Radoslav Rábara updated JBIDE-12106: ------------------------------------ Fix Version/s: 4.1.1.Final (was: 4.2.x) > JAX-RS RESTful explorer out of sync > ----------------------------------- > > Key: JBIDE-12106 > URL: https://issues.jboss.org/browse/JBIDE-12106 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 3.3.0.CR1 > Reporter: Jaroslav Jankovič > Assignee: Radoslav Rábara > Fix For: 4.1.1.Final > > Attachments: JBIDE-12106.ogv, JBIDE-12106.png > > -- 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

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12106) JAX-RS RESTful explorer out of sync

by Radoslav Rábara (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12106?page=com.atlassian.jira.plugi... ] Radoslav Rábara closed JBIDE-12106. ----------------------------------- Resolution: Done > JAX-RS RESTful explorer out of sync > ----------------------------------- > > Key: JBIDE-12106 > URL: https://issues.jboss.org/browse/JBIDE-12106 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 3.3.0.CR1 > Reporter: Jaroslav Jankovič > Assignee: Radoslav Rábara > Fix For: 4.1.1.Final > > Attachments: JBIDE-12106.ogv, JBIDE-12106.png > > -- 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

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-10748) Sometimes there is no update in JAX-RS explorer as it should be

by Radoslav Rábara (JIRA)

[ https://issues.jboss.org/browse/JBIDE-10748?page=com.atlassian.jira.plugi... ] Radoslav Rábara updated JBIDE-10748: ------------------------------------ Fix Version/s: 4.1.1.Final (was: 4.2.x) > Sometimes there is no update in JAX-RS explorer as it should be > --------------------------------------------------------------- > > Key: JBIDE-10748 > URL: https://issues.jboss.org/browse/JBIDE-10748 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 3.3.0.M5 > Reporter: Jaroslav Jankovič > Assignee: Radoslav Rábara > Fix For: 4.1.1.Final > > > When replacing annotation by another only by typing it manually, there is no bug. But if you would like to replace it with Copy-Paste way, there is no change in JAX-RS explorer. Clean build won't help as well. -- 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

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-10748) Sometimes there is no update in JAX-RS explorer as it should be

by Radoslav Rábara (JIRA)

[ https://issues.jboss.org/browse/JBIDE-10748?page=com.atlassian.jira.plugi... ] Radoslav Rábara closed JBIDE-10748. ----------------------------------- Resolution: Done > Sometimes there is no update in JAX-RS explorer as it should be > --------------------------------------------------------------- > > Key: JBIDE-10748 > URL: https://issues.jboss.org/browse/JBIDE-10748 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 3.3.0.M5 > Reporter: Jaroslav Jankovič > Assignee: Radoslav Rábara > Fix For: 4.1.1.Final > > > When replacing annotation by another only by typing it manually, there is no bug. But if you would like to replace it with Copy-Paste way, there is no change in JAX-RS explorer. Clean build won't help as well. -- 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

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15665) Appliaction wizard: Wrong output directory in new Tomcat 7 applications

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15665?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-15665: ------------------------------------- Summary: Appliaction wizard: Wrong output directory in new Tomcat 7 applications (was: Wrong output directory in new Tomcat 7 applications) > Appliaction wizard: Wrong output directory in new Tomcat 7 applications > ----------------------------------------------------------------------- > > Key: JBIDE-15665 > URL: https://issues.jboss.org/browse/JBIDE-15665 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.0.1.Final > Environment: Eclipse Kepler, Mac OS X 10.8.4 > Reporter: Jorge Yagüe París > Assignee: Andre Dietisheim > Labels: maven, tomcat7 > Fix For: 4.2.0.Alpha1 > > > I created a new Tomcat 7 Openshift application with the new project wizard, using an existing Maven project. The wizard adds the Openshift profile in pom.xml but outputDirectory is set as *deployments* instead of *webapps*, so when the application is pushed to the server it doesn't work. > Changing deployments to webapps in the Maven plugin makes it work. -- 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

12 years, 4 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 December 2013