July 2019 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-26719) jbosstools-base_master build is failing due to "Invalid value of default.version = 4.12.0.Final for parent = 4.13.0.AM1-SNAPSHOT !"

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26719?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26719: ------------------------------- Sprint: devex #169 July 2019 > jbosstools-base_master build is failing due to "Invalid value of default.version = 4.12.0.Final for parent = 4.13.0.AM1-SNAPSHOT !" > ----------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-26719 > URL: https://issues.jboss.org/browse/JBIDE-26719 > Project: Tools (JBoss Tools) > Issue Type: Bug > Affects Versions: 4.13.0.AM1 > Reporter: Aurélien Pupier > Assignee: Jeff MAURY > Priority: Blocker > > 07:48:11 [INFO] --- maven-enforcer-plugin:1.4.1:enforce (foundation-core-default-version-check) @ org.jboss.tools.foundation.core --- > 07:48:11 [WARNING] Rule 0: org.jboss.tools.releng.FoundationCoreVersionMatchesParentPom failed with message: > 07:48:11 > 07:48:11 [ERROR] Invalid value of default.version = 4.12.0.Final for parent = 4.13.0.AM1-SNAPSHOT ! > 07:48:11 > 07:48:11 Must set default.version = 4.13.0.Final (or = 4.13.0.AM1) in this file: > 07:48:11 > 07:48:11 /mnt/hudson_workspace/workspace/jbosstools-base_master/sources/foundation/plugins/org.jboss.tools.foundation.core/src/org/jboss/tools/foundation/core/properties/internal/currentversion.properties -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26720) forge does not build following release

by Jeff MAURY (Jira)

Jeff MAURY created JBIDE-26720: ---------------------------------- Summary: forge does not build following release Key: JBIDE-26720 URL: https://issues.jboss.org/browse/JBIDE-26720 Project: Tools (JBoss Tools) Issue Type: Bug Components: forge Affects Versions: 4.12.0.Final Reporter: Jeff MAURY Assignee: Jeff MAURY Fix For: 4.13.0.AM1 Bump jbosstools-forge -- 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 André Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBIDE-26694?page=com.atlassian.jira.plugi... ] André Dietisheim commented on JBIDE-26694: ------------------------------------------ [~rob.stryker] can you please provider pointers to what needs to be migrated over? > 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-26719) jbosstools-base_master build is failing due to "Invalid value of default.version = 4.12.0.Final for parent = 4.13.0.AM1-SNAPSHOT !"

by Aurélien Pupier (Jira)

[ https://issues.jboss.org/browse/JBIDE-26719?page=com.atlassian.jira.plugi... ] Aurélien Pupier commented on JBIDE-26719: ----------------------------------------- after modifying the mentioned file in error, it is failing with updates of versioning to do. i don't know by heart which version to put next and all places to modify so abandoning change on it for now. Not planning to work on it soon. > jbosstools-base_master build is failing due to "Invalid value of default.version = 4.12.0.Final for parent = 4.13.0.AM1-SNAPSHOT !" > ----------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-26719 > URL: https://issues.jboss.org/browse/JBIDE-26719 > Project: Tools (JBoss Tools) > Issue Type: Bug > Affects Versions: 4.13.0.AM1 > Reporter: Aurélien Pupier > Priority: Blocker > > 07:48:11 [INFO] --- maven-enforcer-plugin:1.4.1:enforce (foundation-core-default-version-check) @ org.jboss.tools.foundation.core --- > 07:48:11 [WARNING] Rule 0: org.jboss.tools.releng.FoundationCoreVersionMatchesParentPom failed with message: > 07:48:11 > 07:48:11 [ERROR] Invalid value of default.version = 4.12.0.Final for parent = 4.13.0.AM1-SNAPSHOT ! > 07:48:11 > 07:48:11 Must set default.version = 4.13.0.Final (or = 4.13.0.AM1) in this file: > 07:48:11 > 07:48:11 /mnt/hudson_workspace/workspace/jbosstools-base_master/sources/foundation/plugins/org.jboss.tools.foundation.core/src/org/jboss/tools/foundation/core/properties/internal/currentversion.properties -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26719) jbosstools-base_master build is failing due to "Invalid value of default.version = 4.12.0.Final for parent = 4.13.0.AM1-SNAPSHOT !"

by Aurélien Pupier (Jira)

[ https://issues.jboss.org/browse/JBIDE-26719?page=com.atlassian.jira.plugi... ] Aurélien Pupier reassigned JBIDE-26719: --------------------------------------- Assignee: (was: Aurélien Pupier) > jbosstools-base_master build is failing due to "Invalid value of default.version = 4.12.0.Final for parent = 4.13.0.AM1-SNAPSHOT !" > ----------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-26719 > URL: https://issues.jboss.org/browse/JBIDE-26719 > Project: Tools (JBoss Tools) > Issue Type: Bug > Affects Versions: 4.13.0.AM1 > Reporter: Aurélien Pupier > Priority: Blocker > > 07:48:11 [INFO] --- maven-enforcer-plugin:1.4.1:enforce (foundation-core-default-version-check) @ org.jboss.tools.foundation.core --- > 07:48:11 [WARNING] Rule 0: org.jboss.tools.releng.FoundationCoreVersionMatchesParentPom failed with message: > 07:48:11 > 07:48:11 [ERROR] Invalid value of default.version = 4.12.0.Final for parent = 4.13.0.AM1-SNAPSHOT ! > 07:48:11 > 07:48:11 Must set default.version = 4.13.0.Final (or = 4.13.0.AM1) in this file: > 07:48:11 > 07:48:11 /mnt/hudson_workspace/workspace/jbosstools-base_master/sources/foundation/plugins/org.jboss.tools.foundation.core/src/org/jboss/tools/foundation/core/properties/internal/currentversion.properties -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26719) jbosstools-base_master build is failing due to "Invalid value of default.version = 4.12.0.Final for parent = 4.13.0.AM1-SNAPSHOT !"

by Aurélien Pupier (Jira)

Aurélien Pupier created JBIDE-26719: --------------------------------------- Summary: jbosstools-base_master build is failing due to "Invalid value of default.version = 4.12.0.Final for parent = 4.13.0.AM1-SNAPSHOT !" Key: JBIDE-26719 URL: https://issues.jboss.org/browse/JBIDE-26719 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 4.13.0.AM1 Reporter: Aurélien Pupier 07:48:11 [INFO] --- maven-enforcer-plugin:1.4.1:enforce (foundation-core-default-version-check) @ org.jboss.tools.foundation.core --- 07:48:11 [WARNING] Rule 0: org.jboss.tools.releng.FoundationCoreVersionMatchesParentPom failed with message: 07:48:11 07:48:11 [ERROR] Invalid value of default.version = 4.12.0.Final for parent = 4.13.0.AM1-SNAPSHOT ! 07:48:11 07:48:11 Must set default.version = 4.13.0.Final (or = 4.13.0.AM1) in this file: 07:48:11 07:48:11 /mnt/hudson_workspace/workspace/jbosstools-base_master/sources/foundation/plugins/org.jboss.tools.foundation.core/src/org/jboss/tools/foundation/core/properties/internal/currentversion.properties -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26719) jbosstools-base_master build is failing due to "Invalid value of default.version = 4.12.0.Final for parent = 4.13.0.AM1-SNAPSHOT !"

by Aurélien Pupier (Jira)

[ https://issues.jboss.org/browse/JBIDE-26719?page=com.atlassian.jira.plugi... ] Aurélien Pupier reassigned JBIDE-26719: --------------------------------------- Assignee: Aurélien Pupier > jbosstools-base_master build is failing due to "Invalid value of default.version = 4.12.0.Final for parent = 4.13.0.AM1-SNAPSHOT !" > ----------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-26719 > URL: https://issues.jboss.org/browse/JBIDE-26719 > Project: Tools (JBoss Tools) > Issue Type: Bug > Affects Versions: 4.13.0.AM1 > Reporter: Aurélien Pupier > Assignee: Aurélien Pupier > Priority: Blocker > > 07:48:11 [INFO] --- maven-enforcer-plugin:1.4.1:enforce (foundation-core-default-version-check) @ org.jboss.tools.foundation.core --- > 07:48:11 [WARNING] Rule 0: org.jboss.tools.releng.FoundationCoreVersionMatchesParentPom failed with message: > 07:48:11 > 07:48:11 [ERROR] Invalid value of default.version = 4.12.0.Final for parent = 4.13.0.AM1-SNAPSHOT ! > 07:48:11 > 07:48:11 Must set default.version = 4.13.0.Final (or = 4.13.0.AM1) in this file: > 07:48:11 > 07:48:11 /mnt/hudson_workspace/workspace/jbosstools-base_master/sources/foundation/plugins/org.jboss.tools.foundation.core/src/org/jboss/tools/foundation/core/properties/internal/currentversion.properties -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26668) Prepare image RHEL 7.7 Snapshot3 for testing

by Josef Kopriva (Jira)

[ https://issues.jboss.org/browse/JBIDE-26668?page=com.atlassian.jira.plugi... ] Josef Kopriva commented on JBIDE-26668: --------------------------------------- [~zcervink] this has been resolved last sprint, or are there any opened issues? > Prepare image RHEL 7.7 Snapshot3 for testing > -------------------------------------------- > > Key: JBIDE-26668 > URL: https://issues.jboss.org/browse/JBIDE-26668 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests > Affects Versions: 4.12.0.Final > Reporter: Josef Kopriva > Assignee: Zbyněk Červinka > Priority: Major > Fix For: 4.12.0.Final > > > Prepare image for rhel 7.7 snapshot3 when its available. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26659) Server: Cannot download WF17 via new runtime dialog

by Josef Kopriva (Jira)

[ https://issues.jboss.org/browse/JBIDE-26659?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-26659. --------------------------------- > Server: Cannot download WF17 via new runtime dialog > --------------------------------------------------- > > Key: JBIDE-26659 > URL: https://issues.jboss.org/browse/JBIDE-26659 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.12.0.AM1 > Reporter: Josef Kopriva > Assignee: André Dietisheim > Priority: Major > Fix For: 4.12.0.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

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

by Josef Kopriva (Jira)

[ https://issues.jboss.org/browse/JBIDE-17510?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-17510. --------------------------------- > 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: André Dietisheim > Priority: Critical > Fix For: 4.2.x, 4.12.0.Final > > > 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

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