[JBoss JIRA] (JBIDE-11041) It will popup "problem occured" dialog when nested mongodb and rockmongo simultaneously
by bin zhao (JIRA)
bin zhao created JBIDE-11041:
--------------------------------
Summary: It will popup "problem occured" dialog when nested mongodb and rockmongo simultaneously
Key: JBIDE-11041
URL: https://issues.jboss.org/browse/JBIDE-11041
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 3.3.0.Beta1
Environment: Red Hat Enterprise Linux Server release 6.1 (Santiago)
64 Bit
Reporter: bin zhao
Assignee: Andre Dietisheim
Priority: Critical
1. Create a new Openshift application for example: phptest
2. nested rockmongo-1.1 and mongodb-2.0 to the application of the php type
3. Edit the application and select mongodb-2.0 and rockmongo-1.1 from the embeddable cartridge and click 'Finish'.
Notes:
It has also the same issue for nested rockmongo-1.1 individually.
Actual Result:
It will popup "problem occured" dialog...
Expect Result:
For individually nested rockmongo, it should popup "warning dialog" said that Mongodb must be embedded before rockmongo.
For simultaneously nested mongodb and rockmongo, it should be successful without any error.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months
[JBoss JIRA] (JBIDE-11563) OpenShift wizard allows to deploy alredy versioned project
by Stefan Bunciak (JIRA)
Stefan Bunciak created JBIDE-11563:
--------------------------------------
Summary: OpenShift wizard allows to deploy alredy versioned project
Key: JBIDE-11563
URL: https://issues.jboss.org/browse/JBIDE-11563
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 3.3.0.Beta2
Reporter: Stefan Bunciak
Assignee: Andre Dietisheim
Priority: Critical
Fix For: 3.3.0.Beta3
Stack trace:
{code}
org.jboss.tools.openshift.express.internal.ui.OpenShiftUIException: Could not enable OpenShift on project poh5. Theres already a a remote called {1} that points to a differnt git repository.
at org.jboss.tools.openshift.express.internal.ui.wizard.appimport.ConfigureGitSharedProject.addRemote(ConfigureGitSharedProject.java:126)
at org.jboss.tools.openshift.express.internal.ui.wizard.appimport.ConfigureGitSharedProject.execute(ConfigureGitSharedProject.java:106)
at org.jboss.tools.openshift.express.internal.ui.wizard.OpenShiftExpressApplicationWizardModel.configureGitSharedProject(OpenShiftExpressApplicationWizardModel.java:162)
at org.jboss.tools.openshift.express.internal.ui.wizard.OpenShiftExpressApplicationWizard$ImportJob.runInWorkspace(OpenShiftExpressApplicationWizard.java:307)
at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months
[JBoss JIRA] (JBIDE-11687) Add Mac x86_64 and Win x86_64 to target platform in parent pom
by Lucia Jelinkova (JIRA)
Lucia Jelinkova created JBIDE-11687:
---------------------------------------
Summary: Add Mac x86_64 and Win x86_64 to target platform in parent pom
Key: JBIDE-11687
URL: https://issues.jboss.org/browse/JBIDE-11687
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Build/Releng
Affects Versions: 3.3.0.Beta3
Reporter: Lucia Jelinkova
Assignee: Nick Boldt
Plugin configuration for org.eclipse.tycho:target-platform-configuration does not intentionally specify the Mac x86_64 and Win x86_64 environments since these entries break XulRunner build.
However, QE would like to run SWTBot tests also on these environments and overriding the configuration in every bot test plugin is probably not a good idea.
One solution could be to specify those environments in parent pom and override it only in XullRunner's pom file (the requirement not to specify the environments would be clearly defined and documented for XullRunner).
Other solution might be to specify a profile that we could activate on the command line that would add those two environments to the plugin's configuration.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months