[JBoss JIRA] (JBIDE-19755) Implement ServerPort portion of wst.servertools API
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19755?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-19755.
---------------------------------
I verified that this works as described in the blog in JBDS 9.0.0.Beta1 B50 and also JBoss Tools Beta1. On one occasion after I started a manually added monitor for 8080 and then started a server, I got the popup saying that a server is already running - I thought it might be connected to that - the startup poller might in fact poll the monitor local port instead of the real port. But I couldn't reproduce in several more attempts, so I'm not sure what it was.
Anyway, after that first glitch everything worked as it should. I even tried using launch bar to deploy a dynamic web project to a server and that still honored the port monitor so the internal browser was open with the local port of the monitor (not 8080).
> Implement ServerPort portion of wst.servertools API
> ---------------------------------------------------
>
> Key: JBIDE-19755
> URL: https://issues.jboss.org/browse/JBIDE-19755
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server, upstream
> Affects Versions: 4.3.0.Alpha2
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Labels: new_and_noteworthy
> Fix For: 4.3.0.Beta1
>
>
> WTP has support for port monitoring in it. This is a piece of code that I've neglected to implement for, oh, 9 years. I think now's the time, since [~bbrodt] has been asking about it.
> Unfortunately, I've been hit by an upstream bug that hinders my progress:
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=466109
> To be clear, I have a proposed patch which works for HTTP monitoring but simply doesn't function for monitoring the management port due to an upstream bug.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBDS-3440) Consider using TestNG 6.9.4.201505110455 in JBDS 9
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3440?page=com.atlassian.jira.plugin.... ]
Nick Boldt reassigned JBDS-3440:
--------------------------------
Assignee: Nick Boldt (was: Len DiMaggio)
> Consider using TestNG 6.9.4.201505110455 in JBDS 9
> --------------------------------------------------
>
> Key: JBDS-3440
> URL: https://issues.jboss.org/browse/JBDS-3440
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: 3rd-party-certification, 3rd-party-dependencies, installer, upstream
> Affects Versions: 9.0.0.Beta1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 9.0.0.Beta2
>
>
> We currently include TestNG 6.8.6.20141201_2240.
> But the latest available is 6.9.4.201505110455.
> Do we want something newer?
> You can try the latest from here:
> http://beust.com/eclipse/
> If we decide we want something newer, I can pull a mirror and add it to the Beta1 target platform (JBIDE-19776) already in progress.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBDS-3440) Consider using TestNG 6.9.4.201505110455 in JBDS 9
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3440?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3440:
-----------------------------
Component/s: central
discovery
> Consider using TestNG 6.9.4.201505110455 in JBDS 9
> --------------------------------------------------
>
> Key: JBDS-3440
> URL: https://issues.jboss.org/browse/JBDS-3440
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: 3rd-party-certification, 3rd-party-dependencies, central, discovery, installer, upstream
> Affects Versions: 9.0.0.Beta1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 9.0.0.Beta2
>
>
> We currently include TestNG 6.8.6.20141201_2240.
> But the latest available is 6.9.4.201505110455.
> Do we want something newer?
> You can try the latest from here:
> http://beust.com/eclipse/
> If we decide we want something newer, I can pull a mirror and add it to the Beta1 target platform (JBIDE-19776) already in progress.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBDS-3440) Consider using TestNG 6.9.4.201505110455 in JBDS 9
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3440?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-3440:
----------------------------------
Yes, we can add this for Beta2.
Did you test *6.9.4* (from last month), or the latest, *6.9.5.201506120235* ? Assuming the latest.
> Consider using TestNG 6.9.4.201505110455 in JBDS 9
> --------------------------------------------------
>
> Key: JBDS-3440
> URL: https://issues.jboss.org/browse/JBDS-3440
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: 3rd-party-certification, 3rd-party-dependencies, installer, upstream
> Affects Versions: 9.0.0.Beta1
> Reporter: Nick Boldt
> Assignee: Len DiMaggio
> Fix For: 9.0.0.Beta2
>
>
> We currently include TestNG 6.8.6.20141201_2240.
> But the latest available is 6.9.4.201505110455.
> Do we want something newer?
> You can try the latest from here:
> http://beust.com/eclipse/
> If we decide we want something newer, I can pull a mirror and add it to the Beta1 target platform (JBIDE-19776) already in progress.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19760) Add route support to OpenShift explorer
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19760?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-19760:
-------------------------------------
Labels: explorer new_and_noteworthy (was: )
> Add route support to OpenShift explorer
> ---------------------------------------
>
> Key: JBIDE-19760
> URL: https://issues.jboss.org/browse/JBIDE-19760
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Jeff Cantrill
> Assignee: Jeff Cantrill
> Labels: explorer, new_and_noteworthy
> Fix For: 4.3.0.Beta1
>
> Attachments: route.png
>
>
> Add support for viewing routes in OpenShiftExplorer and property pane
> steps to verify:
> # ASSERT: have openshift origin cloned and available in your openshift server
> # EXEC: in openshift server, cd to <origin>/examples/sample-app and do:
> {code}osc process -f application-template-custombuild.json | osc create -f - -n test{code}
> # EXEC: once the build is finished: open up OpenShift explorer
> # ASSERT: you should see an entry: "OpenShift 3 Sample"
> # EXEC: unfold "OpenShift 3 Sample"
> # ASSERT: have a child entry "Routes" with an entry "route-edge"
> # ASSERT: make sure you have properties view opened
> # ASSERT: the properties view is displaying properties for the selected route "route-edge"
> !route.png!
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19760) Add route support to OpenShift explorer
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19760?page=com.atlassian.jira.plugi... ]
Andre Dietisheim closed JBIDE-19760.
------------------------------------
Resolution: Done
re-closing
> Add route support to OpenShift explorer
> ---------------------------------------
>
> Key: JBIDE-19760
> URL: https://issues.jboss.org/browse/JBIDE-19760
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Jeff Cantrill
> Assignee: Jeff Cantrill
> Labels: explorer, new_and_noteworthy
> Fix For: 4.3.0.Beta1
>
> Attachments: route.png
>
>
> Add support for viewing routes in OpenShiftExplorer and property pane
> steps to verify:
> # ASSERT: have openshift origin cloned and available in your openshift server
> # EXEC: in openshift server, cd to <origin>/examples/sample-app and do:
> {code}osc process -f application-template-custombuild.json | osc create -f - -n test{code}
> # EXEC: once the build is finished: open up OpenShift explorer
> # ASSERT: you should see an entry: "OpenShift 3 Sample"
> # EXEC: unfold "OpenShift 3 Sample"
> # ASSERT: have a child entry "Routes" with an entry "route-edge"
> # ASSERT: make sure you have properties view opened
> # ASSERT: the properties view is displaying properties for the selected route "route-edge"
> !route.png!
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months