October 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-15204) New Project wizard hangs when an invalid package is provided as input.

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15204?page=com.atlassian.jira.plugi... ] Pavol Srna updated JBIDE-15204: ------------------------------- Fix Version/s: (was: 4.2.0.Alpha1) > New Project wizard hangs when an invalid package is provided as input. > ---------------------------------------------------------------------- > > Key: JBIDE-15204 > URL: https://issues.jboss.org/browse/JBIDE-15204 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.1.0.Beta2 > Reporter: Vineet Reynolds > Assignee: Koen Aers > Fix For: 4.1.1.Beta1 > > Attachments: eclipse-threaddump-1373927608559.tdump, forge-threaddump-1373927611426.tdump > > > The new project wizard hangs when an invalid package name (according to Forge) is provided in the dialog box. On clicking the Finish button in the wizard, it hangs when running the {{new-project ....}} Forge command. > This is due to Forge waiting for the user to supply a valid package name. See attached thread dumps. > Other comments: > In a way, this is related to FORGE-687, but the fix should probably go into the wizard so users can correct the name instead of Forge deciding on a default. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15204) New Project wizard hangs when an invalid package is provided as input.

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15204?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-15204. ------------------------------ Verified in 4.1.1.Beta1 build. > New Project wizard hangs when an invalid package is provided as input. > ---------------------------------------------------------------------- > > Key: JBIDE-15204 > URL: https://issues.jboss.org/browse/JBIDE-15204 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.1.0.Beta2 > Reporter: Vineet Reynolds > Assignee: Koen Aers > Fix For: 4.1.1.Beta1 > > Attachments: eclipse-threaddump-1373927608559.tdump, forge-threaddump-1373927611426.tdump > > > The new project wizard hangs when an invalid package name (according to Forge) is provided in the dialog box. On clicking the Finish button in the wizard, it hangs when running the {{new-project ....}} Forge command. > This is due to Forge waiting for the user to supply a valid package name. See attached thread dumps. > Other comments: > In a way, this is related to FORGE-687, but the fix should probably go into the wizard so users can correct the name instead of Forge deciding on a default. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15777) CLONE - New Project wizard hangs when an invalid package is provided as input.

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15777?page=com.atlassian.jira.plugi... ] Pavol Srna updated JBIDE-15777: ------------------------------- Fix Version/s: (was: 4.1.1.Beta1) > CLONE - New Project wizard hangs when an invalid package is provided as input. > ------------------------------------------------------------------------------ > > Key: JBIDE-15777 > URL: https://issues.jboss.org/browse/JBIDE-15777 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Reporter: Pavol Srna > Assignee: Koen Aers > Fix For: 4.2.0.Alpha1 > > > The new project wizard hangs when an invalid package name (according to Forge) is provided in the dialog box. On clicking the Finish button in the wizard, it hangs when running the {{new-project ....}} Forge command. > This is due to Forge waiting for the user to supply a valid package name. See attached thread dumps. > Other comments: > In a way, this is related to FORGE-687, but the fix should probably go into the wizard so users can correct the name instead of Forge deciding on a default. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15777) CLONE - New Project wizard hangs when an invalid package is provided as input.

by Pavol Srna (JIRA)

Pavol Srna created JBIDE-15777: ---------------------------------- Summary: CLONE - New Project wizard hangs when an invalid package is provided as input. Key: JBIDE-15777 URL: https://issues.jboss.org/browse/JBIDE-15777 Project: Tools (JBoss Tools) Issue Type: Bug Components: forge Reporter: Pavol Srna Assignee: Koen Aers Fix For: 4.1.1.Beta1, 4.2.0.Alpha1 The new project wizard hangs when an invalid package name (according to Forge) is provided in the dialog box. On clicking the Finish button in the wizard, it hangs when running the {{new-project ....}} Forge command. This is due to Forge waiting for the user to supply a valid package name. See attached thread dumps. Other comments: In a way, this is related to FORGE-687, but the fix should probably go into the wizard so users can correct the name instead of Forge deciding on a default. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15777) CLONE - New Project wizard hangs when an invalid package is provided as input.

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15777?page=com.atlassian.jira.plugi... ] Pavol Srna resolved JBIDE-15777. -------------------------------- Resolution: Done > CLONE - New Project wizard hangs when an invalid package is provided as input. > ------------------------------------------------------------------------------ > > Key: JBIDE-15777 > URL: https://issues.jboss.org/browse/JBIDE-15777 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Reporter: Pavol Srna > Assignee: Koen Aers > Fix For: 4.2.0.Alpha1 > > > The new project wizard hangs when an invalid package name (according to Forge) is provided in the dialog box. On clicking the Finish button in the wizard, it hangs when running the {{new-project ....}} Forge command. > This is due to Forge waiting for the user to supply a valid package name. See attached thread dumps. > Other comments: > In a way, this is related to FORGE-687, but the fix should probably go into the wizard so users can correct the name instead of Forge deciding on a default. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-198) Split BPMN2 tests into *.reddeer and *.ui.bot.test projects

by Marek Baluch (JIRA)

[ https://issues.jboss.org/browse/JBTIS-198?page=com.atlassian.jira.plugin.... ] Marek Baluch updated JBTIS-198: ------------------------------- Comment: was deleted (was: PR: https://github.com/jbosstools/jbosstools-integration-stack-tests/pull/7 ) > Split BPMN2 tests into *.reddeer and *.ui.bot.test projects > ----------------------------------------------------------- > > Key: JBTIS-198 > URL: https://issues.jboss.org/browse/JBTIS-198 > Project: JBoss Tools Integration Stack > Issue Type: Task > Security Level: Public(Everyone can see) > Components: QE > Affects Versions: 4.1.3 > Reporter: Andrej Podhradsky > Assignee: Marek Baluch > Fix For: 4.1.3 > > > There should be the following projects > * org.jboss.tools.bpmn2.reddeer > * org.jboss.tools.bpmn2.ui.bot.test > Please put into org.jboss.tools.bpmn2.reddeer only classes related to BPMN2 editor without all 3rd party libs. I think you are using them in tests so the dependent libs should be in org.jboss.tools.bpmn2.ui.bot.test. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15766) openshift-java-client: dont refresh env variables on each addition/removal

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15766?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-15766: ------------------------------------------ [~mwigglesworth-redhat] very valid concerns, did not think about them when rushing for the rest of the UI. But thinking this API through a 2nd time I pretend that the whole backend API is broken. The general rule of thumb is that you need the diff to be done as close as possible to the peer that stores it. Having to do the diff in the remote client is the worst possible solution. There's 0 guarantee for the client to be up-to-date anyhow. It is verly likely that he'll run into a race condition. In this situation I still dont see the benefit of constantly refreshing the env vars. > openshift-java-client: dont refresh env variables on each addition/removal > -------------------------------------------------------------------------- > > Key: JBIDE-15766 > URL: https://issues.jboss.org/browse/JBIDE-15766 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.1.Beta1, 4.2.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.1.1.Beta1, 4.2.0.Alpha1 > > > When adding/removing environment variables, the openshift-java-client would always request the backend for the full list. This should not be required and avoided > {code:title=ApplicationResource#addEnvironmentVariable} > EnvironmentVariableResourceDTO environmentVariableResourceDTO = > new AddEnvironmentVariableRequest().execute(name, value); > IEnvironmentVariable environmentVariable = new EnvironmentVariableResource(environmentVariableResourceDTO, this); > updateEnvironmentVariables(); > return environmentVariable; > {code} > {code:title=ApplicationResource#updateEnvironmentVariables} > protected void updateEnvironmentVariables() throws OpenShiftException { > if (environmentVariableByName == null) { > environmentVariableByName = loadEnvironmentVariables(); > } else { > environmentVariableByName.clear(); > environmentVariableByName.putAll(loadEnvironmentVariables()); > } > } > {code} -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-198) Split BPMN2 tests into *.reddeer and *.ui.bot.test projects

by Marek Baluch (JIRA)

[ https://issues.jboss.org/browse/JBTIS-198?page=com.atlassian.jira.plugin.... ] Marek Baluch resolved JBTIS-198. -------------------------------- Resolution: Done PR: https://github.com/jbosstools/jbosstools-integration-stack-tests/pull/7 > Split BPMN2 tests into *.reddeer and *.ui.bot.test projects > ----------------------------------------------------------- > > Key: JBTIS-198 > URL: https://issues.jboss.org/browse/JBTIS-198 > Project: JBoss Tools Integration Stack > Issue Type: Task > Security Level: Public(Everyone can see) > Components: QE > Affects Versions: 4.1.3 > Reporter: Andrej Podhradsky > Assignee: Marek Baluch > Fix For: 4.1.3 > > > There should be the following projects > * org.jboss.tools.bpmn2.reddeer > * org.jboss.tools.bpmn2.ui.bot.test > Please put into org.jboss.tools.bpmn2.reddeer only classes related to BPMN2 editor without all 3rd party libs. I think you are using them in tests so the dependent libs should be in org.jboss.tools.bpmn2.ui.bot.test. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14376) JBoss Aerogear Tools succeed to start Android Emulator but Cordova app is failing

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14376?page=com.atlassian.jira.plugi... ] Vlado Pakan commented on JBIDE-14376: ------------------------------------- Sebastien could you please verify this Jira? > JBoss Aerogear Tools succeed to start Android Emulator but Cordova app is failing > ---------------------------------------------------------------------------------- > > Key: JBIDE-14376 > URL: https://issues.jboss.org/browse/JBIDE-14376 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Environment: Fedora 17 > Reporter: Sebastien Blanc > Assignee: Gorkem Ercan > Fix For: 4.1.1.Beta1 > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > JBoss Aerogear Tools succeed to start Android Emulator but Cordova app is failing. See logs : > https://gist.github.com/sebastienblanc/5501833 -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15617) Forge New Project UI Wizard hangs

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15617?page=com.atlassian.jira.plugi... ] Pavol Srna updated JBIDE-15617: ------------------------------- Fix Version/s: (was: 4.2.0.Alpha1) > Forge New Project UI Wizard hangs > --------------------------------- > > Key: JBIDE-15617 > URL: https://issues.jboss.org/browse/JBIDE-15617 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.1.0.Final > Reporter: Pavol Srna > Assignee: Koen Aers > Fix For: 4.1.1.Beta1 > > Attachments: eclipse_jstack.txt, forge-new-project.png, forge_jstack.txt, wizard.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, 6 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 October 2013