July 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-18654) run jdeps on our jars to see how dependent we are on api that might go away in Java 9, 10, 11

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18654?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-18654: ------------------------------- Fix Version/s: 4.9.0.AM1 > run jdeps on our jars to see how dependent we are on api that might go away in Java 9, 10, 11 > --------------------------------------------------------------------------------------------- > > Key: JBIDE-18654 > URL: https://issues.jboss.org/browse/JBIDE-18654 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.2.0.Final > Reporter: Max Rydahl Andersen > Assignee: Jeff MAURY > Fix For: 4.9.0.AM1, 4.9.x > > > Java 9 JDK team have been pinging various teams to check if they got depedency on API that is scheduled to disappear in Java 9. > There is a tool called jdeps that we can use to check for this using the -jdkinternals flag. > https://wiki.openjdk.java.net/display/JDK8/Java+Dependency+Analysis+Tool > The sooner the better we get this done as it is feedback to the Java 9 team. > If we can we should try run it on *all* jars, even eclipse ones to see what will be affected - but first of all jboss tools plugins. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25553) Cannot create Hibernate Console Configuration for projects with java 9

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25553?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-25553: ------------------------------------ Tests are passing now. !hibernate-jdk9.png|thumbnail! Resolving. > Cannot create Hibernate Console Configuration for projects with java 9 > ---------------------------------------------------------------------- > > Key: JBIDE-25553 > URL: https://issues.jboss.org/browse/JBIDE-25553 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.5.2.AM2 > Reporter: Rastislav Wagner > Assignee: Koen Aers > Priority: Critical > Fix For: 4.6.0.Final > > Attachments: hibernate-jdk9.png > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25553) Cannot create Hibernate Console Configuration for projects with java 9

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25553?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25553: ------------------------------- Attachment: hibernate-jdk9.png > Cannot create Hibernate Console Configuration for projects with java 9 > ---------------------------------------------------------------------- > > Key: JBIDE-25553 > URL: https://issues.jboss.org/browse/JBIDE-25553 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.5.2.AM2 > Reporter: Rastislav Wagner > Assignee: Koen Aers > Priority: Critical > Fix For: 4.6.0.Final > > Attachments: hibernate-jdk9.png > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

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

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26180?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-26180: ------------------------------- Fix Version/s: 4.9.0.AM1 4.9.0.AM2 4.9.0.AM3 4.9.0.Final > 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.AM1, 4.9.0.AM2, 4.9.0.AM3, 4.9.0.Final > > > 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 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

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

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-26180: ---------------------------------- Summary: 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 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 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

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

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26180?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-26180: ------------------------------- Story Points: 42 (was: 6969) > 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 > > 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 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

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

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26180?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-26180: ---------------------------------- Assignee: Nick Boldt > 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 > > 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 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26178) Stacks errors when creating new server

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26178?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-26178: --------------------------------------- [~nickboldt], are you sure? Wouldn't that need to be {code}System.getProperty("URL_PROPERTY_STACKS"){code} instead? As it is in the code now, it simply refers to the constants at the top of the java file, no? Anyway, Rob just merged the fix, so it's fine now. > Stacks errors when creating new server > -------------------------------------- > > Key: JBIDE-26178 > URL: https://issues.jboss.org/browse/JBIDE-26178 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.6.0.Final > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.6.0.Final > > Attachments: missing-commas.png, parse-errors.png > > > When you try to create a server for the first time, stacks.yaml (and pre-stacks.yaml) is downloaded and currently it's invalid yaml, so there are errors thrown in the Error Log view. > !parse-errors.png! > One example: > {code} > Can't access or parse https://raw.githubusercontent.com/jboss-developer/jboss-stacks/1.0.0.Fina... > {code} > {code} > while parsing a flow mapping > in "<reader>", line 201, column 12: > labels: { > ^ > expected ',' or '}', but got Value > in "<reader>", line 206, column 25: > wtp-runtime-type: org.jboss.ide.eclipse.as.runti ... > ^ > at org.yaml.snakeyaml.parser.ParserImpl$ParseFlowMappingKey.produce(ParserImpl.java:734) > at org.yaml.snakeyaml.parser.ParserImpl.peekEvent(ParserImpl.java:160) > at org.yaml.snakeyaml.parser.ParserImpl.checkEvent(ParserImpl.java:145) > at org.yaml.snakeyaml.composer.Composer.composeMappingNode(Composer.java:230) > at org.yaml.snakeyaml.composer.Composer.composeNode(Composer.java:159) > at org.yaml.snakeyaml.composer.Composer.composeMappingNode(Composer.java:237) > at org.yaml.snakeyaml.composer.Composer.composeNode(Composer.java:159) > at org.yaml.snakeyaml.composer.Composer.composeSequenceNode(Composer.java:204) > at org.yaml.snakeyaml.composer.Composer.composeNode(Composer.java:157) > at org.yaml.snakeyaml.composer.Composer.composeMappingNode(Composer.java:237) > at org.yaml.snakeyaml.composer.Composer.composeNode(Composer.java:159) > at org.yaml.snakeyaml.composer.Composer.composeDocument(Composer.java:122) > at org.yaml.snakeyaml.composer.Composer.getSingleNode(Composer.java:105) > at org.yaml.snakeyaml.constructor.BaseConstructor.getSingleData(BaseConstructor.java:120) > at org.yaml.snakeyaml.Yaml.loadFromReader(Yaml.java:480) > at org.yaml.snakeyaml.Yaml.load(Yaml.java:411) > at org.jboss.jdf.stacks.parser.Parser.parse(Parser.java:55) > at org.jboss.tools.stacks.core.model.StacksManager.getStacksFromFile(StacksManager.java:177) > at org.jboss.tools.stacks.core.model.StacksManager.getStacksFromURL(StacksManager.java:163) > at org.jboss.tools.stacks.core.model.StacksManager.getStacks(StacksManager.java:154) > at org.jboss.tools.stacks.core.model.StacksManager.getStacks(StacksManager.java:141) > at org.jboss.tools.stacks.core.model.StacksManager.getStacks(StacksManager.java:106) > at org.fusesource.ide.server.fuse.core.runtime.integration.FuseDownloadRuntimesProvider.getStacks(FuseDownloadRuntimesProvider.java:29) > at org.fusesource.ide.server.karaf.core.runtime.integration.AbstractStacksDownloadRuntimesProvider.loadDownloadableRuntimes(AbstractStacksDownloadRuntimesProvider.java:66) > at org.fusesource.ide.server.karaf.core.runtime.integration.AbstractStacksDownloadRuntimesProvider.getDownloadableRuntimes(AbstractStacksDownloadRuntimesProvider.java:50) > at org.jboss.tools.runtime.core.internal.RuntimeExtensionManager.loadDownloadableRuntimesFromProviders(RuntimeExtensionManager.java:273) > at org.jboss.tools.runtime.core.internal.RuntimeExtensionManager.loadDownloadRuntimes(RuntimeExtensionManager.java:257) > at org.jboss.tools.runtime.core.internal.RuntimeExtensionManager.getDownloadRuntimes(RuntimeExtensionManager.java:199) > at org.jboss.tools.runtime.core.internal.RuntimeExtensionManager.getDownloadRuntimes(RuntimeExtensionManager.java:187) > at org.jboss.tools.runtime.core.RuntimeCoreActivator.getDownloadRuntimes(RuntimeCoreActivator.java:136) > at org.jboss.tools.as.runtimes.integration.util.DownloadRuntimeServerUtil.getDownloadRuntimes(DownloadRuntimeServerUtil.java:41) > at org.jboss.tools.as.runtimes.integration.ui.composites.DownloadRuntimeHyperlinkComposite$1.run(DownloadRuntimeHyperlinkComposite.java:169) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:60) > {code} > Apparently [~rob.stryker] broke the file 14 hours ago with this commit: > https://github.com/jboss-developer/jboss-stacks/commit/48ff290ca4c3f8e901... > See the missing commas here: > !missing-commas.png! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26178) Stacks errors when creating new server

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26178?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-26178: ------------------------------------ Based on this: {code:title=jbosstools-base/stacks/plugins/org.jboss.tools.stacks.core/src/org/jboss/tools/stacks/core/model/StacksManager.java} STACKS_URL = System.getProperty(URL_PROPERTY_STACKS, System.getProperty(STACKS_URL_PROPERTY, System.getProperty(StacksClientConfiguration.REPO_PROPERTY, getStacksDefaultUrlFromJar()))); PRESTACKS_URL = System.getProperty(URL_PROPERTY_PRESTACKS, System.getProperty("jdf.prestacks.client.repo", getPreStacksDefaultUrlFromJar())); {code} I'd try setting these system properties before launching devstudio: {code} export URL_PROPERTY_STACKS=https://raw.githubusercontent.com/mmalina/jdf-stack/J... export URL_PROPERTY_PRESTACKS=https://raw.githubusercontent.com/mmalina/jdf-stac... {code} > Stacks errors when creating new server > -------------------------------------- > > Key: JBIDE-26178 > URL: https://issues.jboss.org/browse/JBIDE-26178 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.6.0.Final > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.6.0.Final > > Attachments: missing-commas.png, parse-errors.png > > > When you try to create a server for the first time, stacks.yaml (and pre-stacks.yaml) is downloaded and currently it's invalid yaml, so there are errors thrown in the Error Log view. > !parse-errors.png! > One example: > {code} > Can't access or parse https://raw.githubusercontent.com/jboss-developer/jboss-stacks/1.0.0.Fina... > {code} > {code} > while parsing a flow mapping > in "<reader>", line 201, column 12: > labels: { > ^ > expected ',' or '}', but got Value > in "<reader>", line 206, column 25: > wtp-runtime-type: org.jboss.ide.eclipse.as.runti ... > ^ > at org.yaml.snakeyaml.parser.ParserImpl$ParseFlowMappingKey.produce(ParserImpl.java:734) > at org.yaml.snakeyaml.parser.ParserImpl.peekEvent(ParserImpl.java:160) > at org.yaml.snakeyaml.parser.ParserImpl.checkEvent(ParserImpl.java:145) > at org.yaml.snakeyaml.composer.Composer.composeMappingNode(Composer.java:230) > at org.yaml.snakeyaml.composer.Composer.composeNode(Composer.java:159) > at org.yaml.snakeyaml.composer.Composer.composeMappingNode(Composer.java:237) > at org.yaml.snakeyaml.composer.Composer.composeNode(Composer.java:159) > at org.yaml.snakeyaml.composer.Composer.composeSequenceNode(Composer.java:204) > at org.yaml.snakeyaml.composer.Composer.composeNode(Composer.java:157) > at org.yaml.snakeyaml.composer.Composer.composeMappingNode(Composer.java:237) > at org.yaml.snakeyaml.composer.Composer.composeNode(Composer.java:159) > at org.yaml.snakeyaml.composer.Composer.composeDocument(Composer.java:122) > at org.yaml.snakeyaml.composer.Composer.getSingleNode(Composer.java:105) > at org.yaml.snakeyaml.constructor.BaseConstructor.getSingleData(BaseConstructor.java:120) > at org.yaml.snakeyaml.Yaml.loadFromReader(Yaml.java:480) > at org.yaml.snakeyaml.Yaml.load(Yaml.java:411) > at org.jboss.jdf.stacks.parser.Parser.parse(Parser.java:55) > at org.jboss.tools.stacks.core.model.StacksManager.getStacksFromFile(StacksManager.java:177) > at org.jboss.tools.stacks.core.model.StacksManager.getStacksFromURL(StacksManager.java:163) > at org.jboss.tools.stacks.core.model.StacksManager.getStacks(StacksManager.java:154) > at org.jboss.tools.stacks.core.model.StacksManager.getStacks(StacksManager.java:141) > at org.jboss.tools.stacks.core.model.StacksManager.getStacks(StacksManager.java:106) > at org.fusesource.ide.server.fuse.core.runtime.integration.FuseDownloadRuntimesProvider.getStacks(FuseDownloadRuntimesProvider.java:29) > at org.fusesource.ide.server.karaf.core.runtime.integration.AbstractStacksDownloadRuntimesProvider.loadDownloadableRuntimes(AbstractStacksDownloadRuntimesProvider.java:66) > at org.fusesource.ide.server.karaf.core.runtime.integration.AbstractStacksDownloadRuntimesProvider.getDownloadableRuntimes(AbstractStacksDownloadRuntimesProvider.java:50) > at org.jboss.tools.runtime.core.internal.RuntimeExtensionManager.loadDownloadableRuntimesFromProviders(RuntimeExtensionManager.java:273) > at org.jboss.tools.runtime.core.internal.RuntimeExtensionManager.loadDownloadRuntimes(RuntimeExtensionManager.java:257) > at org.jboss.tools.runtime.core.internal.RuntimeExtensionManager.getDownloadRuntimes(RuntimeExtensionManager.java:199) > at org.jboss.tools.runtime.core.internal.RuntimeExtensionManager.getDownloadRuntimes(RuntimeExtensionManager.java:187) > at org.jboss.tools.runtime.core.RuntimeCoreActivator.getDownloadRuntimes(RuntimeCoreActivator.java:136) > at org.jboss.tools.as.runtimes.integration.util.DownloadRuntimeServerUtil.getDownloadRuntimes(DownloadRuntimeServerUtil.java:41) > at org.jboss.tools.as.runtimes.integration.ui.composites.DownloadRuntimeHyperlinkComposite$1.run(DownloadRuntimeHyperlinkComposite.java:169) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:60) > {code} > Apparently [~rob.stryker] broke the file 14 hours ago with this commit: > https://github.com/jboss-developer/jboss-stacks/commit/48ff290ca4c3f8e901... > See the missing commas here: > !missing-commas.png! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26170) Define JAVAxx and OPENJDKxx for new JDKs and OpenJDKs installed

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26170?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-26170: ---------------------------------- Sprint: devex #152 July 2018 > Define JAVAxx and OPENJDKxx for new JDKs and OpenJDKs installed > --------------------------------------------------------------- > > Key: JBIDE-26170 > URL: https://issues.jboss.org/browse/JBIDE-26170 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.6.0.Final > Reporter: Jeff MAURY > Assignee: Martin Malina > Fix For: 4.9.0.AM1 > > > The JBoss Tools JDK9+ jobs rely on JAVAxx and OPENJDKxx variables through the toolchains.xml file. As we want to move those jobs to Java10 and Java11, we need those variables to be defined -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 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 2018