[JBoss JIRA] (JBTIS-652) Adapt SAP tests according to the changes made in new Camel editor
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-652?page=com.atlassian.jira.plugin.... ]
Andrej Podhradsky commented on JBTIS-652:
-----------------------------------------
Also the doOperation is not supported anymore
> Adapt SAP tests according to the changes made in new Camel editor
> -----------------------------------------------------------------
>
> Key: JBTIS-652
> URL: https://issues.jboss.org/browse/JBTIS-652
> Project: JBoss Tools Integration Stack
> Issue Type: Task
> Components: Fuse IDE, QE
> Affects Versions: 9.0.0.CR1
> Reporter: Andrej Podhradsky
> Assignee: Andrej Podhradsky
>
> I'm still getting the following NPE when I try to add a component to the route
> {code}
> java.lang.NullPointerException
> at org.jboss.reddeer.gef.handler.EditPartHandler.getFigure(EditPartHandler.java:83)
> at org.jboss.reddeer.gef.impl.editpart.AbstractEditPart.getFigure(AbstractEditPart.java:89)
> at org.jboss.tools.fuse.reddeer.editor.CamelComponentEditPart.getBounds(CamelComponentEditPart.java:22)
> at org.jboss.tools.fuse.reddeer.editor.CamelEditor.getInEditorCoords(CamelEditor.java:608)
> at org.jboss.tools.fuse.reddeer.editor.CamelEditor.addCamelComponent(CamelEditor.java:150)
> at org.jboss.tools.fuse.ui.bot.test.SAPComponentTest.testSAPTRFCServer(SAPComponentTest.java:194)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at org.jboss.reddeer.junit.internal.runner.statement.RunTestMethod.evaluate(RunTestMethod.java:36)
> at org.jboss.reddeer.junit.internal.runner.statement.RunBefores.evaluate(RunBefores.java:69)
> at org.jboss.reddeer.junit.internal.runner.statement.RunIBeforeTestExtensions.evaluate(RunIBeforeTestExtensions.java:63)
> at org.jboss.reddeer.junit.internal.runner.statement.RunAfters.evaluate(RunAfters.java:58)
> at org.jboss.reddeer.junit.internal.runner.statement.RunIAfterTestExtensions.evaluate(RunIAfterTestExtensions.java:51)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at org.jboss.reddeer.junit.internal.runner.RequirementsRunner.runChild(RequirementsRunner.java:165)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.jboss.reddeer.junit.internal.runner.statement.RunBefores.evaluate(RunBefores.java:69)
> at org.jboss.reddeer.junit.internal.runner.statement.FulfillRequirementsStatement.evaluate(FulfillRequirementsStatement.java:35)
> at org.jboss.reddeer.junit.internal.runner.statement.RunIBeforeClassExtensions.evaluate(RunIBeforeClassExtensions.java:60)
> at org.jboss.reddeer.junit.internal.runner.statement.RunAfters.evaluate(RunAfters.java:58)
> at org.jboss.reddeer.junit.internal.runner.statement.CleanUpRequirementStatement.evaluate(CleanUpRequirementStatement.java:34)
> at org.jboss.reddeer.junit.internal.runner.statement.RunIAfterClassExtensions.evaluate(RunIAfterClassExtensions.java:48)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.jboss.reddeer.junit.internal.runner.RequirementsRunner.run(RequirementsRunner.java:146)
> at org.junit.runners.Suite.runChild(Suite.java:128)
> at org.junit.runners.Suite.runChild(Suite.java:27)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.junit.runners.Suite.runChild(Suite.java:128)
> at org.junit.runners.Suite.runChild(Suite.java:27)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:86)
> at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:675)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382)
> at org.jboss.reddeer.eclipse.core.RemotePluginTestRunner.main(RemotePluginTestRunner.java:58)
> at org.jboss.reddeer.eclipse.core.UITestApplication.runTests(UITestApplication.java:115)
> at org.eclipse.e4.ui.internal.workbench.swt.E4Testable$1.run(E4Testable.java:73)
> at java.lang.Thread.run(Thread.java:745)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22128) Openshift 3 plugin "Server Adapter" doesn't respect openshift maven profile
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22128?page=com.atlassian.jira.plugi... ]
Marián Labuda commented on JBIDE-22128:
---------------------------------------
[~fbricon] How can I verify this one? So far we don't have a mechanism to use builder images to create new applications. Could you please provide some steps how to verify in tooling?
> Openshift 3 plugin "Server Adapter" doesn't respect openshift maven profile
> ---------------------------------------------------------------------------
>
> Key: JBIDE-22128
> URL: https://issues.jboss.org/browse/JBIDE-22128
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Environment: JBoss Developer Studio (Core Features) 9.1.0.GA-v20160403-1700-B477
> Openshift plugin 3.1.0.Final-v20160401-2357-B263
> Reporter: Rafael Benevides
> Assignee: Fred Bricon
> Labels: respin-b
> Fix For: 4.3.1.CR1
>
>
> I have a Java project with an "openshift" maven profile that creates a ROOT.war
> When I create a "Server Adapter", the openshift plugins deploys the name of the project.war
> The plugin should be integrated with M2E in a way that if I select/enable the "openshift" profile on M2E, the Openshift plugin should deploy ROOT.war through "Server Adapter".
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21356) Make OpenShift 3 resource edition more robust
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21356?page=com.atlassian.jira.plugi... ]
Marián Labuda edited comment on JBIDE-21356 at 4/12/16 7:31 AM:
----------------------------------------------------------------
[~fbricon] Could you please provide steps to verify what have been done to make editing more robust?
was (Author: mlabuda):
Could you please provide steps to verify?
> Make OpenShift 3 resource edition more robust
> ---------------------------------------------
>
> Key: JBIDE-21356
> URL: https://issues.jboss.org/browse/JBIDE-21356
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Fred Bricon
> Assignee: Fred Bricon
> Fix For: 4.3.1.CR1
>
>
> Following [~scabanovich]'s comment in JBIDE-20761:
> {quote}
> My concern is that the default editor is called if it is set for .json without a fallback for a case of failure of that unknown editor. We cannot be sure what editor a user may have set to be default for .json. That editor may be expecting some specific instance of editor input object and fail on what is provided. As it is, then json will not be opened at all, neither fancy nor plain text. However, if it is just temporal, till the expected contribution to jsdt, and that editor is going to be hardcoded to be opened, then no problem.
> {quote}
> Until we can rely on Eclipse's upcoming JSON editor (in Neon), we should try to harden editor detection/opening
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21933) [openshift server] Wire up module-restart / republish for hot-code replace
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21933?page=com.atlassian.jira.plugi... ]
Marián Labuda edited comment on JBIDE-21933 at 4/12/16 7:30 AM:
----------------------------------------------------------------
[~rob.stryker] Could you please provide steps how to verify this one in tooling? If there is nothing to verify, please close this issue.
was (Author: mlabuda):
Could you please provide steps how to verify this one?
> [openshift server] Wire up module-restart / republish for hot-code replace
> --------------------------------------------------------------------------
>
> Key: JBIDE-21933
> URL: https://issues.jboss.org/browse/JBIDE-21933
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: openshift, server
> Affects Versions: 4.3.1.CR1
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.3.1.CR1
>
>
> I've made this a subtask because it is related to but not a core piece of enabling module-restart. This jira is for allowing more options on hotcode-replace failure.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22129) Watches should not try to reconnect when a project has been deleted
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22129?page=com.atlassian.jira.plugi... ]
Marián Labuda commented on JBIDE-22129:
---------------------------------------
[~jcantrill] could you please provide steps to verify? If there is nothing visible to verify in tooling, please close this issue.
> Watches should not try to reconnect when a project has been deleted
> -------------------------------------------------------------------
>
> Key: JBIDE-22129
> URL: https://issues.jboss.org/browse/JBIDE-22129
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Fred Bricon
> Assignee: Jeff Cantrill
> Labels: respin-b
> Fix For: 4.3.1.CR1
>
>
> When a project has been deleted from the webconsole, the watchmanager in eclipse is not notified. Each watch that times out tries to reconnect to some of the dead project's urls. Each access is rejected with 403 errors (the project could exist but not be visible to the user).
> After each attempt, the watches will wait a little longer before trying to reconnect, until it eventually stops trying.
> Since the watch manager has access to the projects, it can try to check the project exists before connecting the watch
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3788) Folder selection dialog should consume focus when opened
by Jan Richter (JIRA)
Jan Richter created JBDS-3788:
---------------------------------
Summary: Folder selection dialog should consume focus when opened
Key: JBDS-3788
URL: https://issues.jboss.org/browse/JBDS-3788
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: installer
Affects Versions: 9.1.0.CR1
Reporter: Jan Richter
This is an extension of JBDS-3696. Hitting Browse opens a folder selection dialog. At this point nothing stops me from switching back to the main window and clicking whatever UI element I want.
The trouble is that while these elements do not seem to respond when the browse dialog is shown, all the actions get queued up and execute once the dialog closes.
But wait - it gets better! I can open the dialog and then click a sequence of buttons (like 'continue', 'back' - many times) and it always lands on a different page in the end.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBTIS-616) TP update - Locus .Final and latest 4.3.x (Mars)
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-616?page=com.atlassian.jira.plugin.... ]
Andrej Podhradsky commented on JBTIS-616:
-----------------------------------------
Hey [~pleacu], I don't see any updated locus bundle in the TP (the title says that locus was updated).
> TP update - Locus .Final and latest 4.3.x (Mars)
> ------------------------------------------------
>
> Key: JBTIS-616
> URL: https://issues.jboss.org/browse/JBTIS-616
> Project: JBoss Tools Integration Stack
> Issue Type: Feature Request
> Components: target-platform
> Affects Versions: 4.3.1.Beta1b-TP
> Reporter: Paul Leacu
> Assignee: Paul Leacu
> Fix For: 4.3.1.CR1-TP
>
>
> *Reason:* Update to Locus .Final and latest 4.3.x CR1 bits
> *Project page/sources:* ...
> *Version:* 4.3.1.CR1
> *License and owner:* ...
> *Original p2 repo:*
> *JBoss mirror:*
> *Include Sources:* Yes
> *Affected JBoss Tools components:* Integration Stack
> *Include in JBDS:* Yes (JBDSIS)
> *Type of dependency:* distribution
> *List of bundles added/removed:*
> {code}
> < org.jboss.tools.as.test.core [3.1.1.Beta2-v20160121-0132-B81]
> < org.jboss.tools.common.base.test [3.7.1.Beta2-v20160127-2129-B77]
> < org.jboss.tools.community.project.examples.feature.feature.group [3.0.1.Beta2-v20160121-2329-B74]
> < org.jboss.tools.common.test [3.7.1.Beta2-v20160127-2129-B77]
> < org.jboss.tools.project.examples.feature.feature.group [3.0.1.Beta2-v20160121-2329-B74]
> < org.jboss.tools.tests [3.6.1.Beta2-v20160127-2129-B77]
> < org.jboss.tools.community.central.feature.feature.jar [2.0.1.Beta2-v20160121-2329-B74]
> < org.jboss.tools.community.project.examples.feature.feature.jar [3.0.1.Beta2-v20160121-2329-B74]
> < org.jboss.tools.community.central [2.0.1.Beta2-v20160121-2329-B74]
> < org.jboss.tools.community.project.examples [3.0.1.Beta2-v20160121-2329-B74]
> < org.jboss.tools.community.central.feature.feature.group [2.0.1.Beta2-v20160121-2329-B74]
> < org.jboss.tools.common [3.7.1.Beta2-v20160127-2129-B77]
> < org.jboss.tools.jmx.core.test [1.7.1.Beta2-v20160121-0132-B81]
> < org.jboss.tools.project.examples.feature.feature.jar [3.0.1.Beta2-v20160121-2329-B74]
> < org.jboss.tools.project.examples.cheatsheet [3.0.1.Beta2-v20160121-2329-B74]
> < org.jboss.tools.project.examples [3.0.1.Beta2-v20160121-2329-B74]
> > org.jboss.tools.tests [3.6.1.CR1-v20160324-0436-B104]
> > org.jboss.tools.jmx.core.test [1.7.1.CR1-v20160324-2013-B109]
> > org.jboss.tools.common [3.7.1.CR1-v20160324-0436-B104]
> > org.jboss.tools.project.examples.cheatsheet [3.0.1.CR1-v20160324-1911-B99]
> > org.jboss.tools.project.examples.feature.feature.group [3.0.1.CR1-v20160324-1911-B99]
> > org.jboss.tools.project.examples.feature.feature.jar [3.0.1.CR1-v20160324-1911-B99]
> > org.jboss.tools.community.project.examples.feature.feature.group [3.0.1.CR1-v20160324-1911-B99]
> > org.jboss.tools.community.central.feature.feature.group [2.0.1.CR1-v20160324-1911-B99]
> > org.jboss.tools.project.examples [3.0.1.CR1-v20160324-1911-B99]
> > org.jboss.tools.common.base.test [3.7.1.CR1-v20160324-0436-B104]
> > org.jboss.tools.community.project.examples.feature.feature.jar [3.0.1.CR1-v20160324-1911-B99]
> > org.jboss.tools.community.project.examples [3.0.1.CR1-v20160324-1911-B99]
> > org.jboss.tools.as.test.core [3.1.1.CR1-v20160324-2013-B109]
> > org.jboss.tools.common.test [3.7.1.CR1-v20160324-0436-B104]
> > org.jboss.tools.community.central [2.0.1.CR1-v20160324-1911-B99]
> > org.jboss.tools.community.central.feature.feature.jar [2.0.1.CR1-v20160324-1911-B99]
> === Summary ===
> file:///home/pleacu/git-clone/jbosstools-integration-stack.orig/target-platform/target/target-platform.target.repo contains 16 unique IUs
> file:///home/pleacu/git-clone/jbosstools-integration-stack/target-platform/target/target-platform.target.repo contains 16 unique IUs
> < org.eclipse.uml2.uml.validation [5.0.0.v20160118-1129]
> < org.eclipse.uml2.uml.ecore.exporter [3.0.0.v20160118-1129]
> < org.eclipse.uml2.uml.profile.standard [1.0.100.v20160118-1129]
> < org.eclipse.uml2.uml.ecore.importer [3.0.2.v20160118-1129]
> < org.jboss.tools.project.examples.feature.feature.group [3.0.1.Beta2-v20160121-2329-B74]
> < org.jboss.tools.community.central.feature.feature.group [2.0.1.Beta2-v20160121-2329-B74]
> < org.eclipse.uml2.common.edit.feature.group [2.1.0.v20160118-1129]
> < org.eclipse.emf.ecore.feature.jar [2.11.1.v20150805-0538]
> < org.eclipse.uml2.uml.edit [5.1.1.v20160118-1129]
> < org.eclipse.uml2.uml [5.1.2.v20160118-1129]
> < org.eclipse.uml2.feature.jar [5.1.2.v20160118-1129]
> < org.eclipse.uml2.common.feature.group [2.1.0.v20160118-1129]
> < org.eclipse.emf.codegen.ecore.ui [2.11.1.v20150806-0404]
> < org.eclipse.uml2.common.edit.feature.jar [2.1.0.v20160118-1129]
> < org.eclipse.uml2.uml.feature.group [5.1.2.v20160118-1129]
> < org.eclipse.uml2.feature.group [5.1.2.v20160118-1129]
> < org.jboss.tools.community.central [2.0.1.Beta2-v20160121-2329-B74]
> < org.eclipse.uml2.ant [1.0.0.v20160118-1129]
> < org.eclipse.uml2.uml.edit.feature.group [5.1.1.v20160118-1129]
> < org.eclipse.uml2 [5.0.0.v20160118-1129]
> < org.eclipse.emf.codegen.ecore.ui.feature.jar [2.11.1.v20150806-0404]
> < org.jboss.tools.community.project.examples.feature.feature.group [3.0.1.Beta2-v20160121-2329-B74]
> < org.eclipse.uml2.codegen.ecore [2.1.2.v20160118-1129]
> < org.jboss.tools.community.central.feature.feature.jar [2.0.1.Beta2-v20160121-2329-B74]
> < org.jboss.tools.community.project.examples.feature.feature.jar [3.0.1.Beta2-v20160121-2329-B74]
> < org.eclipse.uml2.uml.feature.jar [5.1.2.v20160118-1129]
> < org.eclipse.emf.codegen.ecore.ui.feature.group [2.11.1.v20150806-0404]
> < org.eclipse.emf.ecore.xmi [2.11.1.v20150805-0538]
> < org.eclipse.uml2.types [2.0.0.v20160118-1129]
> < org.eclipse.uml2.common.edit [2.1.0.v20160118-1129]
> < org.eclipse.emf.ecore.feature.group [2.11.1.v20150805-0538]
> < org.eclipse.uml2.common.feature.jar [2.1.0.v20160118-1129]
> < org.eclipse.emf.ecore [2.11.1.v20150805-0538]
> < org.eclipse.uml2.codegen.ecore.ui.feature.jar [2.1.2.v20160118-1129]
> < org.eclipse.uml2.uml.resources [5.1.0.v20160118-1129]
> < org.eclipse.uml2.uml.edit.feature.jar [5.1.1.v20160118-1129]
> < org.jboss.tools.community.project.examples [3.0.1.Beta2-v20160121-2329-B74]
> < org.eclipse.uml2.codegen.ecore.ui.feature.group [2.1.2.v20160118-1129]
> < org.eclipse.uml2.uml.editor [5.1.0.v20160118-1129]
> < org.eclipse.uml2.common [2.1.0.v20160118-1129]
> < org.eclipse.emf.ecore.change [2.11.0.v20150805-0538]
> < org.eclipse.uml2.codegen.ecore.ui [2.1.0.v20160118-1129]
> < org.jboss.tools.project.examples.feature.feature.jar [3.0.1.Beta2-v20160121-2329-B74]
> < org.jboss.tools.project.examples.cheatsheet [3.0.1.Beta2-v20160121-2329-B74]
> < org.jboss.tools.project.examples [3.0.1.Beta2-v20160121-2329-B74]
> > org.eclipse.uml2.uml.ecore.exporter [3.0.0.v20160201-0816]
> > org.eclipse.uml2.uml.validation [5.0.0.v20160201-0816]
> > org.eclipse.uml2.uml.ecore.importer [3.0.2.v20160201-0816]
> > org.eclipse.uml2.common [2.1.0.v20160201-0816]
> > org.eclipse.emf.ecore.feature.group [2.11.2.v20160208-0816]
> > org.eclipse.uml2.uml.edit.feature.jar [5.1.1.v20160201-0816]
> > org.eclipse.uml2.common.edit.feature.group [2.1.0.v20160201-0816]
> > org.eclipse.uml2.uml.edit [5.1.1.v20160201-0816]
> > org.eclipse.uml2.feature.jar [5.1.2.v20160201-0816]
> > org.eclipse.emf.ecore.xmi [2.11.1.v20160208-0816]
> > org.eclipse.uml2.uml.profile.standard [1.0.100.v20160201-0816]
> > org.eclipse.emf.ecore.feature.jar [2.11.2.v20160208-0816]
> > org.eclipse.emf.codegen.ecore.ui.feature.group [2.11.1.v20160208-0841]
> > org.eclipse.uml2.feature.group [5.1.2.v20160201-0816]
> > org.eclipse.uml2.common.edit.feature.jar [2.1.0.v20160201-0816]
> > org.eclipse.uml2.uml.feature.group [5.1.2.v20160201-0816]
> > org.jboss.tools.project.examples.feature.feature.group [3.0.1.CR1-v20160324-1911-B99]
> > org.jboss.tools.community.central.feature.feature.group [2.0.1.CR1-v20160324-1911-B99]
> > org.eclipse.emf.ecore.change [2.11.0.v20160208-0816]
> > org.jboss.tools.community.project.examples.feature.feature.jar [3.0.1.CR1-v20160324-1911-B99]
> > org.eclipse.uml2.uml.edit.feature.group [5.1.1.v20160201-0816]
> > org.eclipse.uml2.ant [1.0.0.v20160201-0816]
> > org.eclipse.uml2 [5.0.0.v20160201-0816]
> > org.jboss.tools.community.central.feature.feature.jar [2.0.1.CR1-v20160324-1911-B99]
> > org.eclipse.uml2.common.feature.group [2.1.0.v20160201-0816]
> > org.eclipse.uml2.types [2.0.0.v20160201-0816]
> > org.jboss.tools.project.examples [3.0.1.CR1-v20160324-1911-B99]
> > org.jboss.tools.community.project.examples [3.0.1.CR1-v20160324-1911-B99]
> > org.eclipse.uml2.uml.feature.jar [5.1.2.v20160201-0816]
> > org.eclipse.emf.codegen.ecore.ui.feature.jar [2.11.1.v20160208-0841]
> > org.eclipse.uml2.codegen.ecore [2.1.2.v20160201-0816]
> > org.eclipse.uml2.codegen.ecore.ui.feature.jar [2.1.2.v20160201-0816]
> > org.jboss.tools.community.central [2.0.1.CR1-v20160324-1911-B99]
> > org.eclipse.uml2.common.edit [2.1.0.v20160201-0816]
> > org.eclipse.uml2.uml.resources [5.1.0.v20160201-0816]
> > org.eclipse.uml2.uml [5.1.2.v20160201-0816]
> > org.jboss.tools.project.examples.cheatsheet [3.0.1.CR1-v20160324-1911-B99]
> > org.jboss.tools.project.examples.feature.feature.jar [3.0.1.CR1-v20160324-1911-B99]
> > org.jboss.tools.community.project.examples.feature.feature.group [3.0.1.CR1-v20160324-1911-B99]
> > org.eclipse.uml2.common.feature.jar [2.1.0.v20160201-0816]
> > org.eclipse.uml2.uml.editor [5.1.0.v20160201-0816]
> > org.eclipse.emf.codegen.ecore.ui [2.11.1.v20160208-0841]
> > org.eclipse.emf.ecore [2.11.2.v20160208-0816]
> > org.eclipse.uml2.codegen.ecore.ui.feature.group [2.1.2.v20160201-0816]
> > org.eclipse.uml2.codegen.ecore.ui [2.1.0.v20160201-0816]
> === Summary ===
> file:///home/pleacu/git-clone/jbosstools-integration-stack.orig/target-platform/target/target-platform-ea.target.repo contains 45 unique IUs
> file:///home/pleacu/git-clone/jbosstools-integration-stack/target-platform/target/target-platform-ea.target.repo contains 45 unique IUs
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22165) Check "Add Route" checkbox for exposing services of docker image by default
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22165?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-22165:
----------------------------------
Labels: docker openshift_v3 (was: )
> Check "Add Route" checkbox for exposing services of docker image by default
> ---------------------------------------------------------------------------
>
> Key: JBIDE-22165
> URL: https://issues.jboss.org/browse/JBIDE-22165
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Labels: docker, openshift_v3
>
> I think usually users would like to expose their services of a docker image being deployed to OpenShift. In the Deploy Image to OpenShift wizard we have a wizard page where mapping of ports is happening and also exposing of services to routes by checking a checkbox "Add Route" is placed there. By default we have this checkbox unchecked, but maybe we should enable it by default. In my humble opinion in many use case there will be an existing docker image of some application and user would like to deploy it to OpenShift and check application whether it is working or use some features of OpenShift itself...
> At the moment we don't have enabled exposing of OpenShift resources in tooling and therefore if user by accident or intentionally click on Finish button in Deploy Image to OpenShift wizard one page earlier (the one where env. vars, scaling and data volumes are located), it produce a running pod with service, but there is no route and it force user to swich to command line to use oc to expose a service to get a route.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22165) Check "Add Route" checkbox for exposing services of docker image by default
by Marián Labuda (JIRA)
Marián Labuda created JBIDE-22165:
-------------------------------------
Summary: Check "Add Route" checkbox for exposing services of docker image by default
Key: JBIDE-22165
URL: https://issues.jboss.org/browse/JBIDE-22165
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: openshift
Affects Versions: 4.3.1.CR1
Reporter: Marián Labuda
I think usually users would like to expose their services of a docker image being deployed to OpenShift. In the Deploy Image to OpenShift wizard we have a wizard page where mapping of ports is happening and also exposing of services to routes by checking a checkbox "Add Route" is placed there. By default we have this checkbox unchecked, but maybe we should enable it by default. In my humble opinion in many use case there will be an existing docker image of some application and user would like to deploy it to OpenShift and check application whether it is working or use some features of OpenShift itself...
At the moment we don't have enabled exposing of OpenShift resources in tooling and therefore if user by accident or intentionally click on Finish button in Deploy Image to OpenShift wizard one page earlier (the one where env. vars, scaling and data volumes are located), it produce a running pod with service, but there is no route and it force user to swich to command line to use oc to expose a service to get a route.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years