August 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-26180) TP: create target platform based on Eclipse 4.9 (Simrel 2018-09)

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26180?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-26180: -------------------------------- Description: In order to start Eclipse 4.9-based builds, we need an updated target platform. For sprint 152 / AM1: simrel M1 For sprint 153 / AM2: simrel M2 For sprint 154 / AM3: simrel M3 For sprint 155 / GA: simrel RC2/GA Coming in the next update, some orbit changes: * batik, icu4j, platform, felix gogo, httpclient (due 27 Aug) Also: * reddeer 2.3 * m2e http://download.eclipse.org/technology/m2e/milestones/1.9/1.9.1.20180822-... was: In order to start Eclipse 4.9-based builds, we need an updated target platform. For sprint 152 / AM1: simrel M1 For sprint 153 / AM2: simrel M2 For sprint 154 / AM3: simrel M3 For sprint 155 / GA: simrel RC2/GA Coming in the next update, some orbit changes: * batik, icu4j, platform, felix gogo, httpclient (due 27 Aug) Also: * reddeer 2.3 * m2e http://download.eclipse.org/technology/m2e/milestones/1.9/1.9.1.20180821-... > TP: create target platform based on Eclipse 4.9 (Simrel 2018-09) > ---------------------------------------------------------------- > > Key: JBIDE-26180 > URL: https://issues.jboss.org/browse/JBIDE-26180 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform, upstream > Affects Versions: 4.9.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.9.0.AM3, 4.9.0.Final, 4.9.x > > Attachments: am1-vs-am2.p2diff.txt > > > In order to start Eclipse 4.9-based builds, we need an updated target platform. > For sprint 152 / AM1: simrel M1 > For sprint 153 / AM2: simrel M2 > For sprint 154 / AM3: simrel M3 > For sprint 155 / GA: simrel RC2/GA > Coming in the next update, some orbit changes: > * batik, icu4j, platform, felix gogo, httpclient (due 27 Aug) > Also: > * reddeer 2.3 > * m2e http://download.eclipse.org/technology/m2e/milestones/1.9/1.9.1.20180822-... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ERT-662) Work on EclipseCon talk

by Eric Williams (JIRA)

Eric Williams created ERT-662: --------------------------------- Summary: Work on EclipseCon talk Key: ERT-662 URL: https://issues.jboss.org/browse/ERT-662 Project: Eclipse Release Train Issue Type: Task Reporter: Eric Williams Assignee: Eric Williams -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ERT-659) Clean up "attributes-changed" accessibility warning

by Eric Williams (JIRA)

[ https://issues.jboss.org/browse/ERT-659?page=com.atlassian.jira.plugin.sy... ] Eric Williams resolved ERT-659. ------------------------------- Resolution: Done > Clean up "attributes-changed" accessibility warning > --------------------------------------------------- > > Key: ERT-659 > URL: https://issues.jboss.org/browse/ERT-659 > Project: Eclipse Release Train > Issue Type: Task > Reporter: Eric Williams > Assignee: Eric Williams > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ERT-658) Fix BrowserFunction

by Eric Williams (JIRA)

[ https://issues.jboss.org/browse/ERT-658?page=com.atlassian.jira.plugin.sy... ] Eric Williams resolved ERT-658. ------------------------------- Resolution: Done > Fix BrowserFunction > ------------------- > > Key: ERT-658 > URL: https://issues.jboss.org/browse/ERT-658 > Project: Eclipse Release Train > Issue Type: Task > Reporter: Eric Williams > Assignee: Eric Williams > > Bug 536141: [Webkit2][Gtk] BrowserFunction lost after page reload on Linux/GTK -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23732) Implement new batch integration ui tests for content assist features in job.xml file.

by Mohit Suman (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23732?page=com.atlassian.jira.plugi... ] Mohit Suman updated JBIDE-23732: -------------------------------- Story Points: 5 (was: 12) > Implement new batch integration ui tests for content assist features in job.xml file. > -------------------------------------------------------------------------------------- > > Key: JBIDE-23732 > URL: https://issues.jboss.org/browse/JBIDE-23732 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: integration-tests, qa > Affects Versions: 4.4.2.AM1 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Labels: batch, integration_tests > Fix For: 4.9.0.AM3 > > > These tests covers both view tabs where content assist feature is used (design and source view). Test: > 1. Offered batch artifacts in content assist menu for ref attribute > 2. Offered element's id for id attribute with correct level of context > 3. Fully qualified names of exceptions used in class attribute of include/exclude tag > 4. Properties from both property definition in job.xml and from batch artifact with @BatchProperty annotation > 5. Proper list of element's id referred from next, to attributes and/or restart attributes -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26160) Server Adapter: erroneously stays in [Debugging] when you kill the pod

by Mohit Suman (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26160?page=com.atlassian.jira.plugi... ] Mohit Suman updated JBIDE-26160: -------------------------------- Story Points: 3 (was: 4) > Server Adapter: erroneously stays in [Debugging] when you kill the pod > ---------------------------------------------------------------------- > > Key: JBIDE-26160 > URL: https://issues.jboss.org/browse/JBIDE-26160 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.6.0.AM3 > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Labels: server_adapter > Fix For: 4.9.x > > > steps: > # EXEC: create an application (via ex. nodejs-mongo-persistent template), import the project and create a server adapter for it > # ASSERT: server adapter is created > # EXEC: start the server adapter in Debugging > # ASSERT: sever adapter is in *[Debugging, Synchronized]* state > # ASSERT: select pod and pick "Port Forwarding..." and it states that the forwarding is started > # EXEC: in Explorer: select the pod for your service and pick "Delete" > # ASSERT: pod gets deleted and recreated > # ASSERT: select pod and pick "Port Forwarding..." and it states that the forwarding is stopped > Result: > The server adapter still says that is is *[Debugging, Synchronized]*, but debugging is not working any more. The new pod is not running in debug (dev-) mode any more. To have it running again you need to restart the server adapter into debug, which will re-create a new pod in debug-mode. > Expected result: > Server adapter should get out of debugging and back into normal run mode *[Started, Synchronized]*. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26231) Implement state persistence

by Mohit Suman (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26231?page=com.atlassian.jira.plugi... ] Mohit Suman updated JBIDE-26231: -------------------------------- Story Points: 5 > Implement state persistence > --------------------------- > > Key: JBIDE-26231 > URL: https://issues.jboss.org/browse/JBIDE-26231 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: runtime-server-protocol > Affects Versions: 4.9.0.AM1 > Reporter: Jeff MAURY > Assignee: Dmitrii Bocharov > Fix For: 4.9.x > > > Server definitions and search pathes should be persistent so that users don't loose their work -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26159) Server adapter: debugging is not stopped if you delete the pod

by Mohit Suman (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26159?page=com.atlassian.jira.plugi... ] Mohit Suman updated JBIDE-26159: -------------------------------- Story Points: 5 (was: 4) > Server adapter: debugging is not stopped if you delete the pod > -------------------------------------------------------------- > > Key: JBIDE-26159 > URL: https://issues.jboss.org/browse/JBIDE-26159 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.6.0.AM3 > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Priority: Minor > Labels: port_forwarding, server_adapter > Fix For: 4.9.x > > > steps: > Screencast: https://youtu.be/XMA--S9zj6s > # EXEC: create an application (via ex. nodejs-mongo-persistent template) > # ASSERT: pod for service is running > # EXEC: select pod and pick "Port Forwarding..." and start the forwarding > # ASSERT: forwarding is running > # EXEC: verify on the cmd-line that the forwarding is running > {code} > $ ps ax | grep oc > 47793 ?? S 0:00.25 /Users/adietish/Downloads/oc_341 port-forward --token=XXXXX --server=https://open.paas.redhat.com --insecure-skip-tls-verify=true -n jbide25000 -p nodejs-mongo-persistent-7-rsmlr 5858:5858 8080:8080 > {code} > # EXEC: in Explorer: select the pod for your service and pick "Delete" > # ASSERT: pod gets deleted and recreated > # EXEC: verify on the cmd-line that the forwarding is running > {code} > $ ps ax | grep oc > 47793 ?? S 0:00.25 /Users/adietish/Downloads/oc_341 port-forward --token=XXXXX --server=https://open.paas.redhat.com --insecure-skip-tls-verify=true -n jbide25000 -p nodejs-mongo-persistent-7-rsmlr 5858:5858 8080:8080 > {code} > Result: > The port forwarding is still running. > In Eclipse there's no way for you to see this since you have to select the new pod and pick "Port Forwarding..." on this new pod. It'll then tell you that the port forwarding is *NOT* running, since we're asking about port-forwarding for the new pod (not the old one that was killed). > PS. it looks like there's a timeout somewhere, oc stops port-forwarding at some point (many minutes later) and the process disappears. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26259) Clicking the HTML5 Project in central does nothing

by Mohit Suman (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26259?page=com.atlassian.jira.plugi... ] Mohit Suman updated JBIDE-26259: -------------------------------- Story Points: 8 > Clicking the HTML5 Project in central does nothing > -------------------------------------------------- > > Key: JBIDE-26259 > URL: https://issues.jboss.org/browse/JBIDE-26259 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.9.0.AM1 > Reporter: Martin Malina > Assignee: Dmitrii Bocharov > > In order to test the PR for JBIDE-26256 I installed JBT into Eclipse Photon. Now I wanted to create the HTML5 Project from Central. But when I click it, it only displays the Operation in progress window for a moment and then it disappears and nothing happens. The same applies for the Java EE Web Project. Other projects from Central work. I tried opening and closing Central and even restarting Eclipse, neither of those helped. Note that this worked ok in devstudio. I only experienced this today in Eclipse Photon + JBT 4.9.0.AM1 abridged. > I'm on Mac and I installed JBT from http://download.jboss.org/jbosstools/photon/staging/updates/ which currently contains the 4.9.0.AM1 bits. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26259) Clicking the HTML5 Project in central does nothing

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26259?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-26259: ------------------------------------- Sprint: devex #154 September 2018 (was: devex #153 August 2018) > Clicking the HTML5 Project in central does nothing > -------------------------------------------------- > > Key: JBIDE-26259 > URL: https://issues.jboss.org/browse/JBIDE-26259 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.9.0.AM1 > Reporter: Martin Malina > Assignee: Dmitrii Bocharov > > In order to test the PR for JBIDE-26256 I installed JBT into Eclipse Photon. Now I wanted to create the HTML5 Project from Central. But when I click it, it only displays the Operation in progress window for a moment and then it disappears and nothing happens. The same applies for the Java EE Web Project. Other projects from Central work. I tried opening and closing Central and even restarting Eclipse, neither of those helped. Note that this worked ok in devstudio. I only experienced this today in Eclipse Photon + JBT 4.9.0.AM1 abridged. > I'm on Mac and I installed JBT from http://download.jboss.org/jbosstools/photon/staging/updates/ which currently contains the 4.9.0.AM1 bits. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues August 2018