October 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-23324) Properties: should set selection to child context

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23324?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-23324: ------------------------------------- Story Points: 8 > Properties: should set selection to child context > ------------------------------------------------- > > Key: JBIDE-23324 > URL: https://issues.jboss.org/browse/JBIDE-23324 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.2.AM2 > Reporter: Dmitry Bocharov > Assignee: Dmitrii Bocharov > Labels: openshift_v3, properties > Fix For: 4.4.2.AM3 > > > (copied from https://issues.jboss.org/browse/JBIDE-23182?focusedCommentId=13306362&pag...): > We need to update EvaluationContext in OpenShiftResourcePropertySection class for example like this: > {code} > table.addSelectionChangedListener(new ISelectionChangedListener() { > > @Override > public void selectionChanged(SelectionChangedEvent event) { > IHandlerService service = (IHandlerService) page.getSite().getService(IHandlerService.class); > service.getCurrentState().addVariable(ISources.ACTIVE_CURRENT_SELECTION_NAME, table.getSelection()); > > } > }); > {code} > But this made no sense, because in the example above i'm trying to update the global evaluation context from getter. Nothing just happens. So the way to solve it is to define a child evaluation context, which will be used then in Handlers too. > I think it's a much bigger refactoring, than the one that Slava made. I think we should merge it. > However, i might have missed some possibilities and maybe someone has more experience with updating the evaluation context. That is the thing that should be done for Properties view similarly to what i offered above, because it's a "peculiar" view. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23324) Properties: should set selection to child context

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23324?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov reassigned JBIDE-23324: ---------------------------------------- Assignee: Dmitrii Bocharov > Properties: should set selection to child context > ------------------------------------------------- > > Key: JBIDE-23324 > URL: https://issues.jboss.org/browse/JBIDE-23324 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.2.AM2 > Reporter: Dmitry Bocharov > Assignee: Dmitrii Bocharov > Labels: openshift_v3, properties > Fix For: 4.4.2.AM3 > > > (copied from https://issues.jboss.org/browse/JBIDE-23182?focusedCommentId=13306362&pag...): > We need to update EvaluationContext in OpenShiftResourcePropertySection class for example like this: > {code} > table.addSelectionChangedListener(new ISelectionChangedListener() { > > @Override > public void selectionChanged(SelectionChangedEvent event) { > IHandlerService service = (IHandlerService) page.getSite().getService(IHandlerService.class); > service.getCurrentState().addVariable(ISources.ACTIVE_CURRENT_SELECTION_NAME, table.getSelection()); > > } > }); > {code} > But this made no sense, because in the example above i'm trying to update the global evaluation context from getter. Nothing just happens. So the way to solve it is to define a child evaluation context, which will be used then in Handlers too. > I think it's a much bigger refactoring, than the one that Slava made. I think we should merge it. > However, i might have missed some possibilities and maybe someone has more experience with updating the evaluation context. That is the thing that should be done for Properties view similarly to what i offered above, because it's a "peculiar" view. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4095) unparseable date in o.j.t.foundation.checkup

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBDS-4095?page=com.atlassian.jira.plugin.... ] Dmitrii Bocharov updated JBDS-4095: ----------------------------------- Story Points: 4 Sprint: devex #122 October 2016 > unparseable date in o.j.t.foundation.checkup > -------------------------------------------- > > Key: JBDS-4095 > URL: https://issues.jboss.org/browse/JBDS-4095 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: foundation > Affects Versions: 10.2.0.AM1 > Environment: {code} > Red Hat JBoss Developer Studio > Version: 10.2.0.AM1 > Build id: AM1-v20160923-1714-B6096 > Build date: 20160923-1714 > $➔ uname -a > Linux t540p-f24-vm01 4.7.4-200.fc24.x86_64 #1 SMP Thu Sep 15 18:42:09 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux > [14:00:12] nboldt@t540p-f24-vm01:~/devstudio-10.2.0.AM1 > $➔ java -version > openjdk version "1.8.0_65" > OpenJDK Runtime Environment (build 1.8.0_65-b17) > OpenJDK 64-Bit Server VM (build 25.65-b01, mixed mode) > {code} > Reporter: Nick Boldt > Assignee: Dmitrii Bocharov > Attachments: unparesable-date.png > > > Just started up devstudio 10.2.0.AM1-v20160923-1714-B6096 and got this error: > {code} > Unparseable date: "Thu Oct 06 13:55:38 EDT 2016" > java.text.ParseException: Unparseable date: "Thu Oct 06 13:55:38 EDT 2016" > at java.text.DateFormat.parse(DateFormat.java:366) > at org.jboss.tools.foundation.checkup.JVMProblemDetector.getSessionDate(JVMProblemDetector.java:677) > at org.jboss.tools.foundation.checkup.JVMProblemDetector.scanLine(JVMProblemDetector.java:240) > at org.jboss.tools.foundation.checkup.JVMProblemDetector.readLogFile(JVMProblemDetector.java:186) > at org.jboss.tools.foundation.checkup.JVMProblemDetector.earlyStartup(JVMProblemDetector.java:118) > at org.eclipse.ui.internal.EarlyStartupRunnable.runEarlyStartup(EarlyStartupRunnable.java:77) > at org.eclipse.ui.internal.EarlyStartupRunnable.run(EarlyStartupRunnable.java:53) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.ui.internal.Workbench$55.run(Workbench.java:2829) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23015) Application wizard: Creating a route should have a default port

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23015?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23015: ------------------------------------- Summary: Application wizard: Creating a route should have a default port (was: Creating a route should have a default port) > Application wizard: Creating a route should have a default port > --------------------------------------------------------------- > > Key: JBIDE-23015 > URL: https://issues.jboss.org/browse/JBIDE-23015 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Fred Bricon > Assignee: Jeff MAURY > Labels: new_and_noteworthy, openshift, openshift_v3 > Fix For: 4.4.2.AM2 > > > When deploying a docker image, in the Services and Routing settings, when "Add route" is checked, if there are multiple ports exposed, then openshift will round-robin the route to any of the ports. So if you have 3 exposed ports, 1 of them is for the web app, then 2/3 of the http connections to the service will fail. > There should be a new column, in the ports table, with 1 checkbox checkable at the time: checking 1 box will uncheck the others. > The lowest port should be selected by default (that's what the oc client does apparently, but deserve confirmation) > To reproduce: > - git clone https://github.com/redhat-helloworld-msa/aloha > - mvn package > - build docker image from Dockerfile, to CDK docker connection > - deploy docker image to openshift -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23349) LiveReload New and Noteworthy for 4.4.2.AM2

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23349?page=com.atlassian.jira.plugi... ] Xavier Coulon closed JBIDE-23349. --------------------------------- Resolution: Rejected No N&N. > LiveReload New and Noteworthy for 4.4.2.AM2 > --------------------------------------------------- > > Key: JBIDE-23349 > URL: https://issues.jboss.org/browse/JBIDE-23349 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: livereload > Reporter: Jeff MAURY > Assignee: Xavier Coulon > Priority: Critical > Fix For: 4.4.2.AM2 > > > Search for your component's New and Noteworthy issues: > Queries: > * [Completed LiveReload JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for LiveReload, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for LiveReload by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form 'JBIDE-56789 #comment Create N&N for LiveReload4.4.2.AM2 #close', and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for LiveReload for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23339) Webservices / Rest New and Noteworthy for 4.4.2.AM2

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23339?page=com.atlassian.jira.plugi... ] Xavier Coulon closed JBIDE-23339. --------------------------------- Resolution: Rejected No N&N. > Webservices / Rest New and Noteworthy for 4.4.2.AM2 > --------------------------------------------------- > > Key: JBIDE-23339 > URL: https://issues.jboss.org/browse/JBIDE-23339 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: webservices > Reporter: Jeff MAURY > Assignee: Xavier Coulon > Priority: Critical > Fix For: 4.4.2.AM2 > > > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Webservices / Rest JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for Webservices / Rest, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Webservices / Rest by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form 'JBIDE-56789 #comment Create N&N for Webservices / Rest4.4.2.AM2 #close', and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for Webservices / Rest for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23328) Docker New and Noteworthy for 4.4.2.AM2

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23328?page=com.atlassian.jira.plugi... ] Xavier Coulon closed JBIDE-23328. --------------------------------- Resolution: Rejected No N&N. > Docker New and Noteworthy for 4.4.2.AM2 > --------------------------------------------------- > > Key: JBIDE-23328 > URL: https://issues.jboss.org/browse/JBIDE-23328 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: docker > Reporter: Jeff MAURY > Assignee: Xavier Coulon > Priority: Critical > Fix For: 4.4.2.AM2 > > > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Docker JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for Docker, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Docker by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form 'JBIDE-56789 #comment Create N&N for Docker4.4.2.AM2 #close', and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for Docker for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23055) Repeated toggling of JAX-RS support on project does not cause it to rebuild

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23055?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-23055: ---------------------------------- Fix Version/s: 4.4.2.AM3 (was: 4.4.2.AM2) > Repeated toggling of JAX-RS support on project does not cause it to rebuild > --------------------------------------------------------------------------- > > Key: JBIDE-23055 > URL: https://issues.jboss.org/browse/JBIDE-23055 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.4.1.AM3 > Reporter: Jan Richter > Assignee: Xavier Coulon > Fix For: 4.4.2.AM3 > > > When JAX-RS support is toggled in a project's preferences, clicking Apply will rebuild the project and JAX-RS services will (dis)/appear and validation is enabled/disabled. > But if without closing the preferences I toggle JAX-RS support again and press Apply, nothing happens - the project is not built with the new settings. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23346) Batch New and Noteworthy for 4.4.2.AM2

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23346?page=com.atlassian.jira.plugi... ] Alexey Kazakov closed JBIDE-23346. ---------------------------------- Resolution: Rejected No N&N > Batch New and Noteworthy for 4.4.2.AM2 > --------------------------------------------------- > > Key: JBIDE-23346 > URL: https://issues.jboss.org/browse/JBIDE-23346 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: batch > Reporter: Jeff MAURY > Assignee: Alexey Kazakov > Priority: Critical > Fix For: 4.4.2.AM2 > > > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Batch JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for Batch, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Batch by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form 'JBIDE-56789 #comment Create N&N for Batch4.4.2.AM2 #close', and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for Batch for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23344) Freemarker New and Noteworthy for 4.4.2.AM2

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23344?page=com.atlassian.jira.plugi... ] Alexey Kazakov closed JBIDE-23344. ---------------------------------- Resolution: Rejected No N&N AFAIK > Freemarker New and Noteworthy for 4.4.2.AM2 > --------------------------------------------------- > > Key: JBIDE-23344 > URL: https://issues.jboss.org/browse/JBIDE-23344 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: freemarker > Reporter: Jeff MAURY > Assignee: Daniel Dekany > Priority: Critical > Fix For: 4.4.2.AM2 > > > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Freemarker JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for Freemarker, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Freemarker by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form 'JBIDE-56789 #comment Create N&N for Freemarker4.4.2.AM2 #close', and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for Freemarker for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues October 2016