[JBoss JIRA] (JBIDE-22225) Debugging for node.js applications on Openshift
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22225?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-22225:
------------------------------------
p2diff:
{code}$➔ p2diff http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.6... file://`pwd`
< org.eclipse.wst.jsdt.chromium [0.4.0.v201605131737]
> org.eclipse.wst.jsdt.chromium [0.4.0.v201608161838]
< org.eclipse.wst.jsdt.chromium.debug.core [0.4.0.v201605131737]
> org.eclipse.wst.jsdt.chromium.debug.core [0.5.0.v201608251013]
< org.eclipse.wst.jsdt.chromium.debug.feature.feature.group [0.4.0.v201606032110]
> org.eclipse.wst.jsdt.chromium.debug.feature.feature.group [0.4.0.v201609071943]
< org.eclipse.wst.jsdt.chromium.debug.feature.feature.jar [0.4.0.v201606032110]
> org.eclipse.wst.jsdt.chromium.debug.feature.feature.jar [0.4.0.v201609071943]
< org.eclipse.wst.jsdt.chromium.debug.jsdtbridge [0.4.0.v201605131737]
> org.eclipse.wst.jsdt.chromium.debug.jsdtbridge [0.4.0.v201608251013]
< org.eclipse.wst.jsdt.chromium.debug.ui [0.4.0.v201606032110]
> org.eclipse.wst.jsdt.chromium.debug.ui [0.6.0.v201608251013]
< org.eclipse.wst.jsdt.chromium.wipbackend.dev [0.4.0.v201605311527]
> org.eclipse.wst.jsdt.chromium.wipbackend.dev [0.4.0.v201609071943] {code}
and this single new plugin is added:
{code}> org.eclipse.wst.jsdt.chromium.debug.js [0.1.0.v201608311919]
{code}
> Debugging for node.js applications on Openshift
> -----------------------------------------------
>
> Key: JBIDE-22225
> URL: https://issues.jboss.org/browse/JBIDE-22225
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: javascript, openshift
> Reporter: Gorkem Ercan
> Assignee: Ilya Buziuk
> Labels: debugging, openshift_v3
> Fix For: 4.4.2.AM2
>
> Attachments: Screenshot from 2016-07-21 15-29-25.png
>
>
> We should be able to start and connect the new debugger to a node.js application running on Openshift.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBTIS-927) Create test for SQL templates
by stanislav kaleta (JIRA)
stanislav kaleta created JBTIS-927:
--------------------------------------
Summary: Create test for SQL templates
Key: JBTIS-927
URL: https://issues.jboss.org/browse/JBTIS-927
Project: JBoss Tools Integration Stack
Issue Type: Feature Request
Components: QE, teiid
Affects Versions: 4.3.1.Final
Reporter: stanislav kaleta
Assignee: Andrej Podhradsky
Fix For: 4.3.1.Final
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-21668) Fix collection setters in ResourcesUIModel
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21668?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich closed JBIDE-21668.
-----------------------------------------
Resolution: Out of Date
Closing as out-of-date as the class even does not exist any more.
> Fix collection setters in ResourcesUIModel
> ------------------------------------------
>
> Key: JBIDE-21668
> URL: https://issues.jboss.org/browse/JBIDE-21668
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Fix For: 4.4.x
>
>
> Created as follow up to JBIDE-21590.
> Collections setters in ResourcesUIModel, for instance
> {code}
> public void setBuildConfigs(Collection<IResourceUIModel> buildConfigs) {
> firePropertyChange(PROP_BUILD_CONFIGS, resources.get(ResourceKind.BUILD_CONFIG), resources.put(ResourceKind.BUILD_CONFIG, new ArrayList<>(buildConfigs)));
> }
> {code}
> fire incorrect newValue object, because java.util.Map.put(key, value) returns old object associated with the key, not the one just set.
> At this moment, this does not create any bugs, because these setters are still not used, all changes go through ResourcesUIModel.add, ResourcesUIModel.remove, ResourcesUIModel.update that have correct notification. But bugs may appear as soon as collection setters are used, so that they better be fixed, for instance this way :
> {code}
> public void setBuildConfigs(Collection<IResourceUIModel> buildConfigs) {
> setResourcesForKind(buildConfigs, ResourceKind.BUILD_CONFIG);
> }
> private void setResourcesForKind(Collection<IResourceUIModel> list, String kind) {
> List<IResourceUIModel> oldList = resources.get(kind);
> List<IResourceUIModel> newList = new ArrayList<IResourceUIModel>(list);
> resources.put(kind, newList);
> firePropertyChange(getProperty(kind), oldList, newList);
> }
> {code}
> and with use of private setResourcesForKind all other setters will remain one-liners.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-23312) When an OS certificate is accepted, the preference is not always saved
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23312?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-23312:
-----------------------------------------------
[~jeffmaury], I made a pull request, as this solution was used in JBossTools several times when the problem was noticed. There are also many cases when save() is not called after setValue(), it means only that nobody checked the preference after Eclipse restart hard enough, since the problem is not 100% reproducible.
> When an OS certificate is accepted, the preference is not always saved
> ----------------------------------------------------------------------
>
> Key: JBIDE-23312
> URL: https://issues.jboss.org/browse/JBIDE-23312
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.2.AM1
> Reporter: Jeff MAURY
> Labels: openshift, openshift_v3, preferences
> Fix For: 4.4.2.AM3
>
>
> EXEC: clean up Openshift V3 SSL certificates
> EXEC: connect to Openshift
> ASSERT: the certificate dialog should pop up
> EXEC:accept the cerificate and select remember
> EXEC: stop Eclipse
> EXEC: start Eclipse
> EXEC: connect to Openshift
> ASSERT: the certificate dialog popups again
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months