[JBoss JIRA] (JBIDE-12117) Port forwarding wizard: Verifying SSH session job's dialog is displayed until the wizard is closed
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12117?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-12117:
-------------------------------------
Summary: Port forwarding wizard: Verifying SSH session job's dialog is displayed until the wizard is closed (was: Port forwarding wizard: Verifying SSH session job's dialog is displayed until the Port forwarding dialog is closed)
> Port forwarding wizard: Verifying SSH session job's dialog is displayed until the wizard is closed
> --------------------------------------------------------------------------------------------------
>
> Key: JBIDE-12117
> URL: https://issues.jboss.org/browse/JBIDE-12117
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 3.3.0.CR1
> Reporter: Lucia Jelinkova
> Assignee: Andre Dietisheim
> Priority: Minor
> Fix For: 4.2.x
>
> Attachments: eclipse.jpg
>
>
> In Openshift Explorer, when I invoke the Port forwarding menu item, the Verifying SSH session job's dialog is displayed and won't close until the Port forwarding dialog is closed.
> !eclipse.jpg!
> Could it be changed so that when the job is finished the dialog is closed and Port forwarding dialog is shown?
--
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-15807) Eclipe 4.4M3 with jbosstoolstarget-4.40.0.Alpa1-SNAPSHOT target platform does not start
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15807?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-15807:
----------------------------------
Workaround Description:
# Create new Eclipse Application laucher in Run Configurations dialog
# Select Plug-ins tab and switch Launch with to 'plug-ins selected below only'
# Press Deselect All button
# Select org.eclipse.platform bundle only and press 'Add Required Plug-ins'
# Select org.eclipse.ui.ide.application
# Select Workspace node, make sure all its children are selected as well andpress 'Add Required Plug-ins'
# Press Run button
Workaround updated
> Eclipe 4.4M3 with jbosstoolstarget-4.40.0.Alpa1-SNAPSHOT target platform does not start
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-15807
> URL: https://issues.jboss.org/browse/JBIDE-15807
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform
> Affects Versions: 4.2.0.Alpha1
> Reporter: Daniel Azarov
> Assignee: Denis Golovin
> Priority: Blocker
> Fix For: 4.2.0.Alpha1
>
> Attachments: mat.png, scr.png
>
>
> 1. I tried to run JBDS from developer's environment with vm args - -XX:MaxPermSize=512m -Xms1024m -Xmx2048m with all plugins from my workspace
> and I got follow exception:
> {code}
> java.lang.OutOfMemoryError: Java heap space
> at java.util.HashMap.createEntry(HashMap.java:869)
> at java.util.HashMap.addEntry(HashMap.java:856)
> at java.util.HashMap.put(HashMap.java:484)
> at org.apache.felix.resolver.Candidates.copy(Candidates.java:1002)
> at org.apache.felix.resolver.ResolverImpl.checkDynamicPackageSpaceConsistency(ResolverImpl.java:1288)
> at org.apache.felix.resolver.ResolverImpl.checkPackageSpaceConsistency(ResolverImpl.java:1083)
> at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:261)
> at org.eclipse.osgi.container.ModuleResolver$ResolveProcess.resolve(ModuleResolver.java:652)
> at org.eclipse.osgi.container.ModuleResolver.resolveDelta(ModuleResolver.java:75)
> at org.eclipse.osgi.container.ModuleContainer.resolveAndApply(ModuleContainer.java:451)
> at org.eclipse.osgi.container.ModuleContainer.resolve(ModuleContainer.java:409)
> at org.eclipse.osgi.container.ModuleContainer.refresh(ModuleContainer.java:877)
> at org.eclipse.osgi.storage.Storage.discardBundlesOnLoad(Storage.java:206)
> at org.eclipse.osgi.storage.Storage.createStorage(Storage.java:87)
> at org.eclipse.osgi.internal.framework.EquinoxContainer.<init>(EquinoxContainer.java:75)
> at org.eclipse.osgi.launch.Equinox.<init>(Equinox.java:31)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.startup(EclipseStarter.java:287)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:222)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
> {code}
> 2. If I try to run new run configuration with only plugins from target platform I got follow stack trace:
> {code}
> !SESSION 2013-10-28 10:29:47.350 -----------------------------------------------
> eclipse.buildId=unknown
> java.version=1.6.0_24
> java.vendor=Sun Microsystems Inc.
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product org.eclipse.platform.ide
> Command-line arguments: -product org.eclipse.platform.ide -data /home/daniel/workspaces/JBDS_GIT/../runtime-New_configuration(2) -dev file:/home/daniel/workspaces/JBDS_GIT/.metadata/.plugins/org.eclipse.pde.core/New_configuration (2)/dev.properties -os linux -ws gtk -arch x86_64 -consoleLog
> !ENTRY org.eclipse.equinox.simpleconfigurator 4 0 2013-10-28 10:36:19.748
> !MESSAGE FrameworkEvent ERROR
> !STACK 0
> org.osgi.framework.BundleException: Exception in org.eclipse.equinox.internal.simpleconfigurator.Activator.start() of bundle org.eclipse.equinox.simpleconfigurator.
> at org.eclipse.osgi.internal.framework.BundleContextImpl.startActivator(BundleContextImpl.java:782)
> at org.eclipse.osgi.internal.framework.BundleContextImpl.start(BundleContextImpl.java:717)
> at org.eclipse.osgi.internal.framework.EquinoxBundle.startWorker0(EquinoxBundle.java:869)
> at org.eclipse.osgi.internal.framework.EquinoxBundle$EquinoxModule.startWorker(EquinoxBundle.java:257)
> at org.eclipse.osgi.container.Module.doStart(Module.java:556)
> at org.eclipse.osgi.container.Module.start(Module.java:427)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1455)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1438)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1416)
> at org.eclipse.osgi.container.SystemModule.startWorker(SystemModule.java:216)
> at org.eclipse.osgi.container.Module.doStart(Module.java:556)
> at org.eclipse.osgi.container.Module.start(Module.java:427)
> at org.eclipse.osgi.container.SystemModule.start(SystemModule.java:151)
> at org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:347)
> at org.eclipse.osgi.launch.Equinox.start(Equinox.java:115)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.startup(EclipseStarter.java:310)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:222)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
> Caused by: java.lang.OutOfMemoryError: Java heap space
> at java.util.HashMap.addEntry(HashMap.java:770)
> at java.util.HashMap.put(HashMap.java:402)
> at org.apache.felix.resolver.ResolverImpl.mergeUses(ResolverImpl.java:960)
> at org.apache.felix.resolver.ResolverImpl.calculatePackageSpaces(ResolverImpl.java:787)
> at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:252)
> at org.eclipse.osgi.container.ModuleResolver$ResolveProcess.resolve(ModuleResolver.java:652)
> at org.eclipse.osgi.container.ModuleResolver.resolveDelta(ModuleResolver.java:75)
> at org.eclipse.osgi.container.ModuleContainer.resolveAndApply(ModuleContainer.java:451)
> at org.eclipse.osgi.container.ModuleContainer.resolve(ModuleContainer.java:409)
> at org.eclipse.osgi.container.ModuleContainer.resolve(ModuleContainer.java:399)
> at org.eclipse.osgi.container.Module.start(Module.java:406)
> at org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:347)
> at org.eclipse.equinox.internal.simpleconfigurator.ConfigApplier.startBundles(ConfigApplier.java:427)
> at org.eclipse.equinox.internal.simpleconfigurator.ConfigApplier.install(ConfigApplier.java:109)
> at org.eclipse.equinox.internal.simpleconfigurator.SimpleConfiguratorImpl.applyConfiguration(SimpleConfiguratorImpl.java:182)
> at org.eclipse.equinox.internal.simpleconfigurator.SimpleConfiguratorImpl.applyConfiguration(SimpleConfiguratorImpl.java:196)
> at org.eclipse.equinox.internal.simpleconfigurator.Activator.start(Activator.java:48)
> at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:761)
> at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:1)
> at java.security.AccessController.doPrivileged(Native Method)
> at org.eclipse.osgi.internal.framework.BundleContextImpl.startActivator(BundleContextImpl.java:754)
> at org.eclipse.osgi.internal.framework.BundleContextImpl.start(BundleContextImpl.java:717)
> at org.eclipse.osgi.internal.framework.EquinoxBundle.startWorker0(EquinoxBundle.java:869)
> at org.eclipse.osgi.internal.framework.EquinoxBundle$EquinoxModule.startWorker(EquinoxBundle.java:257)
> at org.eclipse.osgi.container.Module.doStart(Module.java:556)
> at org.eclipse.osgi.container.Module.start(Module.java:427)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1455)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1438)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1416)
> at org.eclipse.osgi.container.SystemModule.startWorker(SystemModule.java:216)
> at org.eclipse.osgi.container.Module.doStart(Module.java:556)
> at org.eclipse.osgi.container.Module.start(Module.java:427)
> Root exception:
> java.lang.OutOfMemoryError: Java heap space
> at java.util.HashMap.addEntry(HashMap.java:770)
> at java.util.HashMap.put(HashMap.java:402)
> at org.apache.felix.resolver.ResolverImpl.mergeUses(ResolverImpl.java:960)
> at org.apache.felix.resolver.ResolverImpl.calculatePackageSpaces(ResolverImpl.java:787)
> at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:252)
> at org.eclipse.osgi.container.ModuleResolver$ResolveProcess.resolve(ModuleResolver.java:652)
> at org.eclipse.osgi.container.ModuleResolver.resolveDelta(ModuleResolver.java:75)
> at org.eclipse.osgi.container.ModuleContainer.resolveAndApply(ModuleContainer.java:451)
> at org.eclipse.osgi.container.ModuleContainer.resolve(ModuleContainer.java:409)
> at org.eclipse.osgi.container.ModuleContainer.resolve(ModuleContainer.java:399)
> at org.eclipse.osgi.container.Module.start(Module.java:406)
> at org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:347)
> at org.eclipse.equinox.internal.simpleconfigurator.ConfigApplier.startBundles(ConfigApplier.java:427)
> at org.eclipse.equinox.internal.simpleconfigurator.ConfigApplier.install(ConfigApplier.java:109)
> at org.eclipse.equinox.internal.simpleconfigurator.SimpleConfiguratorImpl.applyConfiguration(SimpleConfiguratorImpl.java:182)
> at org.eclipse.equinox.internal.simpleconfigurator.SimpleConfiguratorImpl.applyConfiguration(SimpleConfiguratorImpl.java:196)
> at org.eclipse.equinox.internal.simpleconfigurator.Activator.start(Activator.java:48)
> at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:761)
> at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:1)
> at java.security.AccessController.doPrivileged(Native Method)
> at org.eclipse.osgi.internal.framework.BundleContextImpl.startActivator(BundleContextImpl.java:754)
> at org.eclipse.osgi.internal.framework.BundleContextImpl.start(BundleContextImpl.java:717)
> at org.eclipse.osgi.internal.framework.EquinoxBundle.startWorker0(EquinoxBundle.java:869)
> at org.eclipse.osgi.internal.framework.EquinoxBundle$EquinoxModule.startWorker(EquinoxBundle.java:257)
> at org.eclipse.osgi.container.Module.doStart(Module.java:556)
> at org.eclipse.osgi.container.Module.start(Module.java:427)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1455)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1438)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1416)
> at org.eclipse.osgi.container.SystemModule.startWorker(SystemModule.java:216)
> at org.eclipse.osgi.container.Module.doStart(Module.java:556)
> at org.eclipse.osgi.container.Module.start(Module.java:427)
> {code}
> 3. If I try same as 2. but with "Running Platform" as target platform - eclipse starts
--
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-12013) Application wizard, Embedding wizard: disallow all non-scalable cartridges for scalable applications
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12013?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-12013:
-------------------------------------
Summary: Application wizard, Embedding wizard: disallow all non-scalable cartridges for scalable applications (was: Application wizard, Embedding wizard: disallow non-scalable cartridges for scalable applications)
> Application wizard, Embedding wizard: disallow all non-scalable cartridges for scalable applications
> ----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-12013
> URL: https://issues.jboss.org/browse/JBIDE-12013
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 3.3.0.Beta3
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Minor
> Fix For: LATER
>
> Attachments: can-only-embed-mysql-and-jenkins.png, can-only-embed-mysql-and-jenkins.png
>
>
> # EXEC: open the *New OpenShift Application* wizard
> # EXEC: check *enable scaling*
> # EXEC: check *phpmysql* embedded cartridge
> # EXEC: hit *Finish*
> Result:
> You get the following error:
> !can-only-embed-mysql-and-jenkins.png!
> Only *mysql*, *mongodb*, *postgres* and *jenkins-client* may be embedded to scalable apps!
> IMHO we should not hardcode any list of allowed embeddable cartridges since this list would get outdated very quickly. The backend should allow us to query such a list. Since there's no cartridge metadata yet, we currently have a local embedding strategy. This should get enhanced to disallow certrain cartridges for scalable applications
--
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-12312) Domain wizard: If domain creation fails because of name that's already used (or forbidden), no info is visible in wizard after you closed the error dialog
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12312?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-12312:
-------------------------------------
Summary: Domain wizard: If domain creation fails because of name that's already used (or forbidden), no info is visible in wizard after you closed the error dialog (was: If domain creation fails because of name that's already used (or forbidden), no info is visible in wizard after you closed the error dialog)
> Domain wizard: If domain creation fails because of name that's already used (or forbidden), no info is visible in wizard after you closed the error dialog
> ----------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-12312
> URL: https://issues.jboss.org/browse/JBIDE-12312
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 3.3.0.Final
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Minor
> Fix For: 4.2.x
>
> Attachments: domain-name-already-used.png, missing-user-guidance.png, no-error.png
>
>
> If you create a new domain on OpenShift, you'll have to provide it's name. This name has to be unique across OpenShift (for all users). If you use a domain name that's already used, you'll get an error dialog that informs you about the name not being unique across OpenShift.
> !domain-name-already-used.png!
> Once you close this dialog, noting is showing this error any more. The name field is not decorated with an error marker.
> steps to reproduce:
> # ASSERT make sure you have an account without a domain
> # EXEC launch the *OpenShift Application* wizard
> # ASSERT you get to the *Domain creation* dialog
> # EXEC supply a valid key and choose a domain name that is *already used* (ex. "domain")
> # ASSERT You get an error dialog that tells you that the domain name is already used
> # EXEC hit *OK*
> Result:
> The domain creation dialog has no information that would tell you what you have to correct.
> !missing-user-guidance.png!
> We should improved this:
> * put an error decoration to the name text field
> * put the cursor into the name text field (eventually select the whole name in it)
> * eventually reach out to #libra to get a way to query the availability of the given name, so that we can validate while typing.
--
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-12013) Application wizard, Embedding wizard: disallow non-scalable cartridges for scalable applications
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12013?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-12013:
-------------------------------------
Summary: Application wizard, Embedding wizard: disallow non-scalable cartridges for scalable applications (was: disallow non-scalable cartridges for scalable applications)
> Application wizard, Embedding wizard: disallow non-scalable cartridges for scalable applications
> ------------------------------------------------------------------------------------------------
>
> Key: JBIDE-12013
> URL: https://issues.jboss.org/browse/JBIDE-12013
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 3.3.0.Beta3
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Minor
> Fix For: 4.2.x
>
> Attachments: can-only-embed-mysql-and-jenkins.png, can-only-embed-mysql-and-jenkins.png
>
>
> # EXEC: open the *New OpenShift Application* wizard
> # EXEC: check *enable scaling*
> # EXEC: check *phpmysql* embedded cartridge
> # EXEC: hit *Finish*
> Result:
> You get the following error:
> !can-only-embed-mysql-and-jenkins.png!
> Only *mysql*, *mongodb*, *postgres* and *jenkins-client* may be embedded to scalable apps!
> IMHO we should not hardcode any list of allowed embeddable cartridges since this list would get outdated very quickly. The backend should allow us to query such a list. Since there's no cartridge metadata yet, we currently have a local embedding strategy. This should get enhanced to disallow certrain cartridges for scalable applications
--
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-12013) Application wizard, Embedding wizard: disallow non-scalable cartridges for scalable applications
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12013?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-12013:
-------------------------------------
Fix Version/s: LATER
(was: 4.2.x)
> Application wizard, Embedding wizard: disallow non-scalable cartridges for scalable applications
> ------------------------------------------------------------------------------------------------
>
> Key: JBIDE-12013
> URL: https://issues.jboss.org/browse/JBIDE-12013
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 3.3.0.Beta3
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Minor
> Fix For: LATER
>
> Attachments: can-only-embed-mysql-and-jenkins.png, can-only-embed-mysql-and-jenkins.png
>
>
> # EXEC: open the *New OpenShift Application* wizard
> # EXEC: check *enable scaling*
> # EXEC: check *phpmysql* embedded cartridge
> # EXEC: hit *Finish*
> Result:
> You get the following error:
> !can-only-embed-mysql-and-jenkins.png!
> Only *mysql*, *mongodb*, *postgres* and *jenkins-client* may be embedded to scalable apps!
> IMHO we should not hardcode any list of allowed embeddable cartridges since this list would get outdated very quickly. The backend should allow us to query such a list. Since there's no cartridge metadata yet, we currently have a local embedding strategy. This should get enhanced to disallow certrain cartridges for scalable applications
--
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-12013) Application wizard, Embedding wizard: disallow non-scalable cartridges for scalable applications
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12013?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-12013:
------------------------------------------
postponing since it is very unlikely that we'll have the time to implement this in the near future.
> Application wizard, Embedding wizard: disallow non-scalable cartridges for scalable applications
> ------------------------------------------------------------------------------------------------
>
> Key: JBIDE-12013
> URL: https://issues.jboss.org/browse/JBIDE-12013
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 3.3.0.Beta3
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Minor
> Fix For: LATER
>
> Attachments: can-only-embed-mysql-and-jenkins.png, can-only-embed-mysql-and-jenkins.png
>
>
> # EXEC: open the *New OpenShift Application* wizard
> # EXEC: check *enable scaling*
> # EXEC: check *phpmysql* embedded cartridge
> # EXEC: hit *Finish*
> Result:
> You get the following error:
> !can-only-embed-mysql-and-jenkins.png!
> Only *mysql*, *mongodb*, *postgres* and *jenkins-client* may be embedded to scalable apps!
> IMHO we should not hardcode any list of allowed embeddable cartridges since this list would get outdated very quickly. The backend should allow us to query such a list. Since there's no cartridge metadata yet, we currently have a local embedding strategy. This should get enhanced to disallow certrain cartridges for scalable applications
--
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-12183) Domain wizard: Domain name is not validated. Has to run into PaaS error to get to know about limitations
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12183?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-12183:
-------------------------------------
Summary: Domain wizard: Domain name is not validated. Has to run into PaaS error to get to know about limitations (was: Domain name is not validated. Has to run into PaaS error to get to know about limitations)
> Domain wizard: Domain name is not validated. Has to run into PaaS error to get to know about limitations
> --------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-12183
> URL: https://issues.jboss.org/browse/JBIDE-12183
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 3.3.0.CR1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Minor
> Fix For: 4.2.x
>
> Attachments: domain-name-must-lt-16chars.png
>
>
> There are 2 limitations:
> * name is limited to 16 alphanumeric characters (resolved in JBIDE-14570)
> * there are forbidden names
> when querying the domain resource (with protocol >= 1.2) one gets the forbidden names:
> {code}
> <invalid-options>
> <invalid-option>amentra</invalid-option>
> <invalid-option>aop</invalid-option>
> <invalid-option>apiviz</invalid-option>
> <invalid-option>arquillian</invalid-option>
> <invalid-option>blacktie</invalid-option>
> <invalid-option>boxgrinder</invalid-option>
> <invalid-option>byteman</invalid-option>
> <invalid-option>cirras</invalid-option>
> <invalid-option>cloud</invalid-option>
> <invalid-option>cloudforms</invalid-option>
> <invalid-option>cygwin</invalid-option>
> <invalid-option>davcache</invalid-option>
> <invalid-option>dogtag</invalid-option>
> <invalid-option>drools</invalid-option>
> <invalid-option>drools</invalid-option>
> <invalid-option>ejb3</invalid-option>
> <invalid-option>errai</invalid-option>
> <invalid-option>esb</invalid-option>
> <invalid-option>fedora</invalid-option>
> <invalid-option>freeipa</invalid-option>
> <invalid-option>gatein</invalid-option>
> <invalid-option>git</invalid-option>
> <invalid-option>gfs</invalid-option>
> <invalid-option>gravel</invalid-option>
> <invalid-option>guvnor</invalid-option>
> <invalid-option>hibernate</invalid-option>
> <invalid-option>hornetq</invalid-option>
> <invalid-option>iiop</invalid-option>
> <invalid-option>infinispan</invalid-option>
> <invalid-option>ironjacamar</invalid-option>
> <invalid-option>javassist</invalid-option>
> <invalid-option>jbcaa</invalid-option>
> <invalid-option>jbcd</invalid-option>
> <invalid-option>jboss</invalid-option>
> <invalid-option>jbpm</invalid-option>
> <invalid-option>jdcom</invalid-option>
> <invalid-option>jgroups</invalid-option>
> <invalid-option>jmx</invalid-option>
> <invalid-option>jopr</invalid-option>
> <invalid-option>jrunit</invalid-option>
> <invalid-option>jsfunit</invalid-option>
> <invalid-option>kosmos</invalid-option>
> <invalid-option>liberation</invalid-option>
> <invalid-option>makara</invalid-option>
> <invalid-option>mass</invalid-option>
> <invalid-option>maven</invalid-option>
> <invalid-option>metajizer</invalid-option>
> <invalid-option>metamatrix</invalid-option>
> <invalid-option>mobicents</invalid-option>
> <invalid-option>mod_cluster</invalid-option>
> <invalid-option>modeshape</invalid-option>
> <invalid-option>mugshot</invalid-option>
> <invalid-option>mysql</invalid-option>
> <invalid-option>netty</invalid-option>
> <invalid-option>openshift</invalid-option>
> <invalid-option>osgi</invalid-option>
> <invalid-option>overlord</invalid-option>
> <invalid-option>ovirt</invalid-option>
> <invalid-option>penrose</invalid-option>
> <invalid-option>picketbox</invalid-option>
> <invalid-option>picketlink</invalid-option>
> <invalid-option>portletbridge</invalid-option>
> <invalid-option>portletswap</invalid-option>
> <invalid-option>posse</invalid-option>
> <invalid-option>pressgang</invalid-option>
> <invalid-option>qumranet</invalid-option>
> <invalid-option>railo</invalid-option>
> <invalid-option>redhat</invalid-option>
> <invalid-option>resteasy</invalid-option>
> <invalid-option>rhca</invalid-option>
> <invalid-option>rhcds</invalid-option>
> <invalid-option>rhce</invalid-option>
> <invalid-option>rhcsa</invalid-option>
> <invalid-option>rhcss</invalid-option>
> <invalid-option>rhct</invalid-option>
> <invalid-option>rhcva</invalid-option>
> <invalid-option>rhel</invalid-option>
> <invalid-option>rhev</invalid-option>
> <invalid-option>rhq</invalid-option>
> <invalid-option>rhx</invalid-option>
> <invalid-option>richfaces</invalid-option>
> <invalid-option>riftsaw</invalid-option>
> <invalid-option>savara</invalid-option>
> <invalid-option>scribble</invalid-option>
> <invalid-option>seam</invalid-option>
> <invalid-option>shadowman</invalid-option>
> <invalid-option>shotoku</invalid-option>
> <invalid-option>shrinkwrap</invalid-option>
> <invalid-option>snowdrop</invalid-option>
> <invalid-option>solidice</invalid-option>
> <invalid-option>spacewalk</invalid-option>
> <invalid-option>spice</invalid-option>
> <invalid-option>steamcannon</invalid-option>
> <invalid-option>stormgrind</invalid-option>
> <invalid-option>switchyard</invalid-option>
> <invalid-option>tattletale</invalid-option>
> <invalid-option>teiid</invalid-option>
> <invalid-option>tohu</invalid-option>
> <invalid-option>torquebox</invalid-option>
> <invalid-option>weld</invalid-option>
> <invalid-option>wise</invalid-option>
> <invalid-option>xnio</invalid-option>
> </invalid-options>
> {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, 4 months