July 2019 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-17510) JBT 4.2.0.Beta2 on Fedora 18 x64 crashes with SIGSEGV

by Ondrej Dockal (Jira)

[ https://issues.jboss.org/browse/JBIDE-17510?page=com.atlassian.jira.plugi... ] Ondrej Dockal commented on JBIDE-17510: --------------------------------------- No idea... how can I find out? webkitgtk package does not even exist in fedora 29. Since we run some set of tests on fedora 29 and 30 on jdk 1.8 and java 11 and not such error report exist, I think we are fine. > JBT 4.2.0.Beta2 on Fedora 18 x64 crashes with SIGSEGV > ----------------------------------------------------- > > Key: JBIDE-17510 > URL: https://issues.jboss.org/browse/JBIDE-17510 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream, xulrunner > Affects Versions: 4.2.0.Beta2 > Environment: JBT 4.2.0.Beta2 (not respin-a) > Fedora 18 x64 > $➔ uname -a > Linux thunk 3.11.9-100.fc18.x86_64 #1 SMP Wed Nov 20 21:22:39 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux > $➔ java -version > java version "1.8.0" > Java(TM) SE Runtime Environment (build 1.8.0-b132) > Java HotSpot(TM) 64-Bit Server VM (build 25.0-b70, mixed mode) > Reporter: Nick Boldt > Assignee: Snjezana Peco > Priority: Critical > Fix For: 4.2.x > > > On Fedora 18 x64 w/ JDK 1.8.0, I get fairly frequent crashes. Sample Eclipse console log showing the crash and SIGSEGV: > https://issues.jboss.org/secure/attachment/12382836/12382836_eclipse.log.... -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26713) Installation of JBT 4.12.0.Final from Update Site Cannot Complete as Requested

by Ondrej Dockal (Jira)

[ https://issues.jboss.org/browse/JBIDE-26713?page=com.atlassian.jira.plugi... ] Ondrej Dockal commented on JBIDE-26713: --------------------------------------- [~koen.aers] Thanks for report. May I know why are you trying to install "only" from update/core/4.12.0.Final url? And what is the issue and what remediation or other errors are? I am installing tools from [1] into [2] and it all went fine... [1]: http://download.jboss.org/jbosstools/photon/staging/updates/ [2]: https://www.eclipse.org/downloads/packages/release/2019-06/r/eclipse-ide-... > Installation of JBT 4.12.0.Final from Update Site Cannot Complete as Requested > ------------------------------------------------------------------------------ > > Key: JBIDE-26713 > URL: https://issues.jboss.org/browse/JBIDE-26713 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: updatesite > Affects Versions: 4.12.0.Final > Reporter: Koen Aers > Assignee: Jeff MAURY > Priority: Critical > Fix For: 4.13.x > > Attachments: JBIDE-26568.mov > > > While installing JBT from the update site at http://download.jboss.org/jbosstools/photon/staging/updates/core/4.12.0.F... in a fresh Eclipse JEE installation the installation does not finish as requested. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26694) Server adapter: should be able to freely set a war name

by Mohit Suman (Jira)

[ https://issues.jboss.org/browse/JBIDE-26694?page=com.atlassian.jira.plugi... ] Mohit Suman updated JBIDE-26694: -------------------------------- Story Points: 21 (was: 34) > Server adapter: should be able to freely set a war name > ------------------------------------------------------- > > Key: JBIDE-26694 > URL: https://issues.jboss.org/browse/JBIDE-26694 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.12.0.AM1 > Reporter: André Dietisheim > Assignee: André Dietisheim > Priority: Major > Labels: server_adapter > Fix For: 4.13.0.AM1 > > Attachments: console-output-1.png, console-output-2.png, server-adapter-configuration.png, switch-location.png > > > For the server adapters in tools/as we have UI that allows a user to set the name of the deployment archive. We're missing this feature for the OpenShift server adapters currently. We're asked to add it. > Steps: > # EXEC: create a new app by using the *jboss-webserver31-tomcat8-openshift:1.2* builder image > # ASSERT: *websocket-chat* application is imported into your workspace > # ASSERT: server adapter *jboss-webserver31-tomcat* is created > # ASSERT: In OpenShift explorer, below the service jboss-webserver31-tomcat*, you have the running pod (build is finished, pod running) > # EXEC: start the server adapter > # ASSERT: RSync is executed and the output is visible in the "Console" > Result: > If you look closely at the output you see that the project is synced to the pod in a folder called *websocket-chat.jar* > !console-output-1.png! > Expected result: > I should be able to set the output folder to anything I want. Ex. we have a customer that wants the application war to be synced up into a folder *ROOT* (without the extension *.war*). > Currently, to achieve this I have to do the following: > # EXEC: create the following xml snippet (notice the *outputName* property for the module) > and make sure it reads as follows: > {code} > <?xml version="1.0" encoding="UTF-8"?> > <deployment> > <local> > <module id="org.eclipse.jst.jee.server:websocket-chat"> > <property key="tempLocation" value="" /> > <property key="location" value="" /> > <property key="outputName" value="ROOT" /> > </module> > </local> > </deployment> > {code} > # EXEC: html-encode, join it into a single line and copy it (into the clipboard) > # EXEC: open the properties for the server adapter and hit "Switch Location" > !switch-location.png! > # ASSERT: in my workspace, a new project *Servers* is created. It contains the configuration for my server adapter. > !server-adapter-configuration.png! > # EXEC: open the file with the *XML Editor* > # EXEC: in your *XML Editor*: go to the end of the line *<server auto-publish-setting="2"* and insert your html-encoded xml as a value to the attribute *org.jboss.ide.eclipse.as.core.util.deploymentPreferenceKey="* > {code} > <?xml version="1.0" encoding="UTF-8" standalone="no"?> > <server auto-publish-setting="2" auto-publish-time="2" hostname="jboss-webserver31-tomcat-test.192.168.64.76.nip.io" id="test@jboss-webserver31-tomcat" id-set="true" name="jboss-webserver31-tomcat (Service) at OpenShift 3 (192.168.64.76)" org.jboss.ide.eclipse.as.core.server.IGNORE_LAUNCH_COMMANDS="true" org.jboss.ide.eclipse.as.core.server.deployDirectoryType="custom" org.jboss.ide.eclipse.as.core.server.serverMode="openshift3" org.jboss.ide.eclipse.as.core.server.webPort="80" org.jboss.ide.eclipse.as.core.server.webPortAutoDetect="false" org.jboss.ide.eclipse.as.core.server.zipDeploymentsPreference="true" org.jboss.tools.openshift.Connection="https://developer@192.168.64.76:8443" org.jboss.tools.openshift.DeployProject="websocket-chat" org.jboss.tools.openshift.PodPath="/opt/webserver/webapps" org.jboss.tools.openshift.SERVER_START_ON_CREATION="false" org.jboss.tools.openshift.Service="test@jboss-webserver31-tomcat" org.jboss.tools.openshift.SourcePath="${workspace_loc:/websocket-chat}" port="80" runtime-id="test@jboss-webserver31-tomcat" server-type="org.jboss.tools.openshift.server.type" server-type-id="org.jboss.tools.openshift.server.type" start-timeout="450" stop-timeout="450" timestamp="2" org.jboss.ide.eclipse.as.core.util.deploymentPreferenceKey="<?xml version="1.0" encoding="UTF-8"?> <deployment> <local> <module id="org.eclipse.jst.jee.server:websocket-chat"> <property key="tempLocation" value="" /> <property key="location" value="" /> <property key="outputName" value="ROOT" /> </module> </local> </deployment>"> > <list key="modules" value0="websocket-chat::org.eclipse.jst.jee.server:websocket-chat::jst.web::3.0"/> > </server> > {code} > # EXEC: Save the editor and restart the server > Result: > Syncing now happens into a folder *ROOT* > !console-output-2.png! -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26700) Get A rating on https://observatory.mozilla.org for tools.jboss.org

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26700?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26700: ------------------------------- Story Points: 5 > Get A rating on https://observatory.mozilla.org for tools.jboss.org > ------------------------------------------------------------------- > > Key: JBIDE-26700 > URL: https://issues.jboss.org/browse/JBIDE-26700 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: website > Affects Versions: 4.12.0.Final > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.13.0.AM1 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26716) Fix builds for TP based on 2019-09.M1

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26716?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26716: ------------------------------- Story Points: 10 > Fix builds for TP based on 2019-09.M1 > ------------------------------------- > > Key: JBIDE-26716 > URL: https://issues.jboss.org/browse/JBIDE-26716 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.13.0.AM1 > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.13.0.AM1 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26716) Fix builds for TP based on 2019-09.M1

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26716?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26716: ------------------------------- Story Points: 5 (was: 10) > Fix builds for TP based on 2019-09.M1 > ------------------------------------- > > Key: JBIDE-26716 > URL: https://issues.jboss.org/browse/JBIDE-26716 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.13.0.AM1 > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.13.0.AM1 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26715) Update 4.13.0.AM1 Target Platform (Docker tooling, ...) for 2019-09.M1

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26715?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26715: ------------------------------- Story Points: 10 > Update 4.13.0.AM1 Target Platform (Docker tooling, ...) for 2019-09.M1 > ---------------------------------------------------------------------- > > Key: JBIDE-26715 > URL: https://issues.jboss.org/browse/JBIDE-26715 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.12.0.Final > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.13.0.AM1 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26714) Change all occurences of OpenShift 3 by OpenShift

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26714?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26714: ------------------------------- Story Points: 5 > Change all occurences of OpenShift 3 by OpenShift > ------------------------------------------------- > > Key: JBIDE-26714 > URL: https://issues.jboss.org/browse/JBIDE-26714 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.12.0.Final > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.13.0.AM1 > > > Now that JBoss Tools supports OCP4 in the same way that OCP3, we should replace all occurence of OpenShift 3 by OpenShift -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26709) Remove openshift.io bundles

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26709?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26709: ------------------------------- Story Points: 5 > Remove openshift.io bundles > --------------------------- > > Key: JBIDE-26709 > URL: https://issues.jboss.org/browse/JBIDE-26709 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.12.0.Final > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.13.0.AM1 > > > openshift.io being sunset, the related bundles should be removed. Checking the Dependency Analytics plugin is also required -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26709) Remove openshift.io bundles

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26709?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26709: ------------------------------- Sprint: devex #170 Aug 2019 (was: devex #169 July 2019) > Remove openshift.io bundles > --------------------------- > > Key: JBIDE-26709 > URL: https://issues.jboss.org/browse/JBIDE-26709 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.12.0.Final > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.13.0.AM1 > > > openshift.io being sunset, the related bundles should be removed. Checking the Dependency Analytics plugin is also required -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 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 July 2019