[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
[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
[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
[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
[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