January 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-11367) Run jobs outside of Wizards instead of within container (wizard launches background jobs and closes)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11367?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-11367: ------------------------------------- Summary: Run jobs outside of Wizards instead of within container (wizard launches background jobs and closes) (was: Run jobs outside of Wizards instead of within container) > Run jobs outside of Wizards instead of within container (wizard launches background jobs and closes) > ---------------------------------------------------------------------------------------------------- > > Key: JBIDE-11367 > URL: https://issues.jboss.org/browse/JBIDE-11367 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 3.3.0.Beta1 > Reporter: Xavier Coulon > Assignee: Andre Dietisheim > Fix For: 4.1.x > > > After 3.3.0.Beta1, most of the operations are run at the end of the wizard (ie, in the performFinish() method). > The current implementation requires a DelegatingProgressMonitor to drive monitors in the Wizard container and in the Workbench status. > We could simplify this design by closing the wizard, then running the job, which could simplify the code, remove the wizard blocking the UI while the operation is in progress. > -- 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

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11367) Run jobs outside of Wizards instead of within container

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11367?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-11367: ------------------------------------- Fix Version/s: 4.1.x (was: 4.0.x) > Run jobs outside of Wizards instead of within container > ------------------------------------------------------- > > Key: JBIDE-11367 > URL: https://issues.jboss.org/browse/JBIDE-11367 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 3.3.0.Beta1 > Reporter: Xavier Coulon > Assignee: Andre Dietisheim > Priority: Optional > Fix For: 4.1.x > > > After 3.3.0.Beta1, most of the operations are run at the end of the wizard (ie, in the performFinish() method). > The current implementation requires a DelegatingProgressMonitor to drive monitors in the Wizard container and in the Workbench status. > We could simplify this design by closing the wizard, then running the job, which could simplify the code, remove the wizard blocking the UI while the operation is in progress. > -- 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

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11367) Run jobs outside of Wizards instead of within container

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11367?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-11367: ------------------------------------- Priority: Major (was: Optional) > Run jobs outside of Wizards instead of within container > ------------------------------------------------------- > > Key: JBIDE-11367 > URL: https://issues.jboss.org/browse/JBIDE-11367 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 3.3.0.Beta1 > Reporter: Xavier Coulon > Assignee: Andre Dietisheim > Fix For: 4.1.x > > > After 3.3.0.Beta1, most of the operations are run at the end of the wizard (ie, in the performFinish() method). > The current implementation requires a DelegatingProgressMonitor to drive monitors in the Wizard container and in the Workbench status. > We could simplify this design by closing the wizard, then running the job, which could simplify the code, remove the wizard blocking the UI while the operation is in progress. > -- 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

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11411) OpenShift server adapter: Warn user when the deployments folder is changed

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11411?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-11411: ------------------------------------- Priority: Minor (was: Major) > OpenShift server adapter: Warn user when the deployments folder is changed > -------------------------------------------------------------------------- > > Key: JBIDE-11411 > URL: https://issues.jboss.org/browse/JBIDE-11411 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 3.3.0.Beta1 > Reporter: Stefan Bunciak > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.0.x > > > As Max comment: > We could warn the user if the deployments folder is not deployments (or even better look for .openshift/config/standalone.xml setting if the apptype is JBoss and only validate then) -- 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

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11411) OpenShift server adapter: Warn user when the deployments folder is changed

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11411?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-11411: ------------------------------------- Fix Version/s: 4.1.x (was: 4.0.x) > OpenShift server adapter: Warn user when the deployments folder is changed > -------------------------------------------------------------------------- > > Key: JBIDE-11411 > URL: https://issues.jboss.org/browse/JBIDE-11411 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 3.3.0.Beta1 > Reporter: Stefan Bunciak > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.1.x > > > As Max comment: > We could warn the user if the deployments folder is not deployments (or even better look for .openshift/config/standalone.xml setting if the apptype is JBoss and only validate then) -- 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

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11408) Eclipse SSH Preferences creates SSH keys with permissions 755

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11408?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-11408: ------------------------------------- Fix Version/s: 4.1.x (was: 4.0.x) > Eclipse SSH Preferences creates SSH keys with permissions 755 > ------------------------------------------------------------- > > Key: JBIDE-11408 > URL: https://issues.jboss.org/browse/JBIDE-11408 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, UpStream > Environment: windows 7 > Reporter: Nam Duong > Assignee: Andre Dietisheim > Priority: Critical > Fix For: 4.1.x > > > similar to https://issues.jboss.org/browse/JBIDE-10061 > When I create a domain for the first time on a clean windows environment, I have to create a new set of keys. Those keys have permissions 755 but they need to be 600 in order to run git/ssh commands with them. I get this error: > git clone ssh://118b5a4772744905b3c19059c5c0ac9c@kitchensink-nduongdemo.rhcloud.com/~/git/kitchensink.git/ > Cloning into 'kitchensink'... > The authenticity of host 'kitchensink-nduongdemo.rhcloud.com (174.129.77.140)' can't be established. > RSA key fingerprint is cf:ee:77:cb:0e:fc:027:72:7e:ae:80:c0:90:88:a7. > Are you sure you want to continue connecting (yes/no)? yes > Warning: Permanently added 'kitchensink-nduongdemo.rhcloud.com,174.129.77.140' (RSA) to the list of known hosts. > @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ > @ WARNING: UNPROTECTED PRIVATE KEY FILE! @ > @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ > Permissions 0755 for '/home/spousty/.ssh/id_rsa' are too open. > It is required that your private key files are NOT accessible by others. > This private key will be ignored. > bad permissions: ignore key: /home/spousty/.ssh/id_rsa > Permission denied (publickey,gssapi-keyex,gssapi-with-mic). > fatal: The remote end hung up unexpectedly -- 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

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11402) Use a caching mecanism to keep list of cartridges and embeddable cartridges beyond eclipse restarts

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11402?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-11402: ------------------------------------- Fix Version/s: LATER (was: 4.0.x) > Use a caching mecanism to keep list of cartridges and embeddable cartridges beyond eclipse restarts > --------------------------------------------------------------------------------------------------- > > Key: JBIDE-11402 > URL: https://issues.jboss.org/browse/JBIDE-11402 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 3.3.0.Beta1 > Reporter: Xavier Coulon > Assignee: Andre Dietisheim > Priority: Optional > Fix For: LATER > > > Instead of querying for available cartridges and embeddable cartridges each time the wizard is started, we could use some persistent cache to immediately retrieve this information, then run a background job to refresh the lists and update the wizard combos if any change occurred. -- 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

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11417) OpenShift Express: Embedded cartridge 10gen-mms-agent-0.1

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11417?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-11417: ------------------------------------- Attachment: mongodb-required-for-mms.png detailled-error-msg.png > OpenShift Express: Embedded cartridge 10gen-mms-agent-0.1 > ---------------------------------------------------------- > > Key: JBIDE-11417 > URL: https://issues.jboss.org/browse/JBIDE-11417 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 3.3.0.Beta3 > Reporter: Attila Nagy > Assignee: Andre Dietisheim > Labels: new_and_noteworthy > Fix For: 4.0.x > > Attachments: detailled-error-msg.png, mongodb-required-for-mms.png > > > There are more problems with the embedded cartridge 10gen-mms-agent > 1) It needs MongoDB and OpenShift application wizard in JBoss Tools doesn't resolve the dependency by default. > It means that the user is not warned in advance. The new application wizard will fail and user will be unable to make the initial git clone. > 2) Actually the user is unable to embed the cartridge, because in the first round the user has to commit and push the 10gen-mss configuration file. > The main problem is: the JBoss Tools wizard only reports that there was an error during the configuration, no details are provided. > Here is the error message from JBoss Tools: > Could not embed cartridges to application php10genmms2012032701 > Could not configure application "php10genmms2012032701" at "https://ec2-50-16-87-180.compute-1.amazonaws.com/broker/embed_cartridge" > And here is the error message from the command line: > Missing settings.py file: /var/lib/stickshift/9bd1f27bba0e40f2b77fdc4b22081991/myphp2with10genmms/.openshift/mms/settings.py > This file is part of the agent zip file: 10gen-mms-agent-<group-name>.zip > The zip file is available to download from https://mms.10gen.com/ after you register with their service. > It contains your 10gen MMS credentials and is required for running the agent. > You will need to add this file and then do a git commit and push before you can embed the 10gen-mms-agent-0.1 cartridge. -- 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

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11417) OpenShift Express: Embedded cartridge 10gen-mms-agent-0.1

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11417?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-11417: ------------------------------------------ 1) was implemented in JBIDE-10852. The wizard prompts the user and informs it that mongo is required for mms: !mongodb-required-for-mms.png! 2) is also resolved. The current error-dialog is displaying the error message with all the details: !detailled-error-msg.png! > OpenShift Express: Embedded cartridge 10gen-mms-agent-0.1 > ---------------------------------------------------------- > > Key: JBIDE-11417 > URL: https://issues.jboss.org/browse/JBIDE-11417 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 3.3.0.Beta3 > Reporter: Attila Nagy > Assignee: Andre Dietisheim > Labels: new_and_noteworthy > Fix For: 4.0.x > > Attachments: detailled-error-msg.png, mongodb-required-for-mms.png > > > There are more problems with the embedded cartridge 10gen-mms-agent > 1) It needs MongoDB and OpenShift application wizard in JBoss Tools doesn't resolve the dependency by default. > It means that the user is not warned in advance. The new application wizard will fail and user will be unable to make the initial git clone. > 2) Actually the user is unable to embed the cartridge, because in the first round the user has to commit and push the 10gen-mss configuration file. > The main problem is: the JBoss Tools wizard only reports that there was an error during the configuration, no details are provided. > Here is the error message from JBoss Tools: > Could not embed cartridges to application php10genmms2012032701 > Could not configure application "php10genmms2012032701" at "https://ec2-50-16-87-180.compute-1.amazonaws.com/broker/embed_cartridge" > And here is the error message from the command line: > Missing settings.py file: /var/lib/stickshift/9bd1f27bba0e40f2b77fdc4b22081991/myphp2with10genmms/.openshift/mms/settings.py > This file is part of the agent zip file: 10gen-mms-agent-<group-name>.zip > The zip file is available to download from https://mms.10gen.com/ after you register with their service. > It contains your 10gen MMS credentials and is required for running the agent. > You will need to add this file and then do a git commit and push before you can embed the 10gen-mms-agent-0.1 cartridge. -- 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

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11417) OpenShift Express: Embedded cartridge 10gen-mms-agent-0.1

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11417?page=com.atlassian.jira.plugi... ] Andre Dietisheim resolved JBIDE-11417. -------------------------------------- Fix Version/s: 4.1.0.Alpha1 (was: 4.0.x) Resolution: Done > OpenShift Express: Embedded cartridge 10gen-mms-agent-0.1 > ---------------------------------------------------------- > > Key: JBIDE-11417 > URL: https://issues.jboss.org/browse/JBIDE-11417 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 3.3.0.Beta3 > Reporter: Attila Nagy > Assignee: Andre Dietisheim > Labels: new_and_noteworthy > Fix For: 4.1.0.Alpha1 > > Attachments: detailled-error-msg.png, mongodb-required-for-mms.png > > > There are more problems with the embedded cartridge 10gen-mms-agent > 1) It needs MongoDB and OpenShift application wizard in JBoss Tools doesn't resolve the dependency by default. > It means that the user is not warned in advance. The new application wizard will fail and user will be unable to make the initial git clone. > 2) Actually the user is unable to embed the cartridge, because in the first round the user has to commit and push the 10gen-mss configuration file. > The main problem is: the JBoss Tools wizard only reports that there was an error during the configuration, no details are provided. > Here is the error message from JBoss Tools: > Could not embed cartridges to application php10genmms2012032701 > Could not configure application "php10genmms2012032701" at "https://ec2-50-16-87-180.compute-1.amazonaws.com/broker/embed_cartridge" > And here is the error message from the command line: > Missing settings.py file: /var/lib/stickshift/9bd1f27bba0e40f2b77fdc4b22081991/myphp2with10genmms/.openshift/mms/settings.py > This file is part of the agent zip file: 10gen-mms-agent-<group-name>.zip > The zip file is available to download from https://mms.10gen.com/ after you register with their service. > It contains your 10gen MMS credentials and is required for running the agent. > You will need to add this file and then do a git commit and push before you can embed the 10gen-mms-agent-0.1 cartridge. -- 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

13 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 January 2013