October 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-26437) Make the Hibernate Tools work with Java 10 and 11

by Koen Aers (Jira)

[ https://issues.jboss.org/browse/JBIDE-26437?page=com.atlassian.jira.plugi... ] Koen Aers reassigned JBIDE-26437: --------------------------------- Assignee: Koen Aers > Make the Hibernate Tools work with Java 10 and 11 > ------------------------------------------------- > > Key: JBIDE-26437 > URL: https://issues.jboss.org/browse/JBIDE-26437 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Affects Versions: 4.9.0.Final > Reporter: Koen Aers > Assignee: Koen Aers > Priority: Major > Fix For: 4.10.0.AM1 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26437) Make the Hibernate Tools work with Java 10 and 11

by Koen Aers (Jira)

[ https://issues.jboss.org/browse/JBIDE-26437?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-26437: ------------------------------ Fix Version/s: 4.10.0.AM1 > Make the Hibernate Tools work with Java 10 and 11 > ------------------------------------------------- > > Key: JBIDE-26437 > URL: https://issues.jboss.org/browse/JBIDE-26437 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Affects Versions: 4.9.0.Final > Reporter: Koen Aers > Assignee: Koen Aers > Priority: Major > Fix For: 4.10.0.AM1 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26389) NPE while "Searching Runtimes"

by Andre Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBIDE-26389?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-26389: ------------------------------------------ [~odockal] ok, thx! I can reproduce it. Seen like this, this seems like an edge case. Still worth fixing, NPE's should be avoided, no doubt about it. > NPE while "Searching Runtimes" > ------------------------------ > > Key: JBIDE-26389 > URL: https://issues.jboss.org/browse/JBIDE-26389 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, runtime-detection > Affects Versions: 4.9.0.Final > Reporter: Ondrej Dockal > Assignee: Rob Stryker > Priority: Major > Fix For: 4.10.0.AM1 > > > {code} > eclipse.buildId=12.9.0.GA-v20180928-1629-B3448 > java.version=1.8.0_181 > java.vendor=Oracle Corporation > BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US > Framework arguments: -product com.jboss.devstudio.core.product > Command-line arguments: -data file:/home/odockal/workspace1290GA/ -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product > org.eclipse.core.jobs > Error > Sun Sep 30 20:56:59 CEST 2018 > An internal error occurred during: "Searching runtimes...". > java.lang.NullPointerException > at org.jboss.tools.openshift.internal.cdk.server.core.detection.UnifiedMinishiftRuntimeDetector.folderWhiteListBin(UnifiedMinishiftRuntimeDetector.java:150) > at org.jboss.tools.openshift.internal.cdk.server.core.detection.UnifiedMinishiftRuntimeDetector.getMinishiftBinary(UnifiedMinishiftRuntimeDetector.java:139) > at org.jboss.tools.openshift.internal.cdk.server.core.detection.UnifiedMinishiftRuntimeDetector.folderContainsMinishiftBinary(UnifiedMinishiftRuntimeDetector.java:144) > at org.jboss.tools.openshift.internal.cdk.server.core.detection.UnifiedMinishiftRuntimeDetector.minishiftHomeMatches(UnifiedMinishiftRuntimeDetector.java:180) > at org.jboss.tools.openshift.internal.cdk.server.core.detection.UnifiedMinishiftRuntimeDetector.matches(UnifiedMinishiftRuntimeDetector.java:171) > at org.jboss.tools.openshift.internal.cdk.server.core.detection.AbstractCDKRuntimeDetector.exists(AbstractCDKRuntimeDetector.java:111) > at org.jboss.tools.runtime.core.internal.RuntimeDetector.exists(RuntimeDetector.java:68) > at org.jboss.tools.runtime.core.util.RuntimeModelUtil.verifyRuntimeDefinitionCreated(RuntimeModelUtil.java:131) > at org.jboss.tools.runtime.core.util.RuntimeModelUtil.verifyRuntimeDefinitionCreated(RuntimeModelUtil.java:122) > at org.jboss.tools.runtime.core.util.RuntimeModelUtil.verifyRuntimeDefinitionCreated(RuntimeModelUtil.java:118) > at org.jboss.tools.runtime.ui.internal.startup.RuntimeScanner.wouldOpenSearchRuntimePathDialog(RuntimeScanner.java:152) > at org.jboss.tools.runtime.ui.internal.startup.RuntimeScanner.access$0(RuntimeScanner.java:129) > at org.jboss.tools.runtime.ui.internal.startup.RuntimeScanner$1.run(RuntimeScanner.java:81) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63) > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26436) Add WF14 in ITest suite

by Josef Kopriva (Jira)

Josef Kopriva created JBIDE-26436: ------------------------------------- Summary: Add WF14 in ITest suite Key: JBIDE-26436 URL: https://issues.jboss.org/browse/JBIDE-26436 Project: Tools (JBoss Tools) Issue Type: Task Components: integration-tests, server Affects Versions: 4.10.0.AM1 Environment: jenkins Reporter: Josef Kopriva Assignee: Josef Kopriva Add WF 14 in ITest suite for testing server -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26388) TP: create target platform based on Eclipse 4.10 (Simrel 2018-12)

by Nick Boldt (Jira)

[ https://issues.jboss.org/browse/JBIDE-26388?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-26388: ------------------------------------ Disabled: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... Need to update TP w/ newer version of Mylyn: {code} 16:30:32 [p2.dir] Only one of the following can be installed at once: 16:30:32 [p2.dir] Mylyn Context Connector: Plug-in Development 3.24.2.v20180905-0014 (org.eclipse.mylyn.pde_feature.feature.jar 3.24.2.v20180905-0014) 16:30:32 [p2.dir] Mylyn Context Connector: Plug-in Development 3.24.1.v20180619-2131 (org.eclipse.mylyn.pde_feature.feature.jar 3.24.1.v20180619-2131) {code} > TP: create target platform based on Eclipse 4.10 (Simrel 2018-12) > ----------------------------------------------------------------- > > Key: JBIDE-26388 > URL: https://issues.jboss.org/browse/JBIDE-26388 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform, upstream > Affects Versions: 4.10.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Major > Labels: releasework > Fix For: 4.10.0.AM1, 4.10.0.Final > > > In order to start Eclipse 4.10-based builds, we need an updated target platform. > Note that Eclipse 4.10 drops support for win32 and lin32 platforms, so poms will need to be updated accordingly. 32-bit is dead, long live 64-bit! > For sprint 156 / AM1: simrel M1 > For sprint 157 / AM1: simrel M2 > For sprint 158 / GA: simrel M3/RC1 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26435) Hibernate JPA Model Generator and Java 11

by Cody Lerum (Jira)

Cody Lerum created JBIDE-26435: ---------------------------------- Summary: Hibernate JPA Model Generator and Java 11 Key: JBIDE-26435 URL: https://issues.jboss.org/browse/JBIDE-26435 Project: Tools (JBoss Tools) Issue Type: Bug Components: maven Affects Versions: 4.9.0.Final Reporter: Cody Lerum Not sure if this ends up being related to Jboss tools or just the Eclipse JDT But on 2018-09 with 4.9.Final a project cannot be cleanly built using the org.hibernate:hibernate-jpamodelgen Everything builds and then at the end it seems to delete the generated sources. This only occurs it the Java 11 support plugin is installed. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26433) For JBIDE 4.10.0.AM1: Prepare for 4.10.0.AM1 / 12.10.0.AM1 [updatesite]

by Nick Boldt (Jira)

[ https://issues.jboss.org/browse/JBIDE-26433?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-26433: ------------------------------------ bump up to parent pom version = 4.10.0.AM1-SNAPSHOT > For JBIDE 4.10.0.AM1: Prepare for 4.10.0.AM1 / 12.10.0.AM1 [updatesite] > ----------------------------------------------------------------------- > > Key: JBIDE-26433 > URL: https://issues.jboss.org/browse/JBIDE-26433 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: updatesite > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.10.0.AM1 > > > For JBIDE 4.10.0.AM1 [updatesite]: Please perform the following tasks: > > 1. Check out your existing *{color:orange}master{color}* branch: > > {code} > git checkout master > {code} > > 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.10.0.AM1-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.10.0.AM1-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.10.0.AM1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > > > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.9.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.9.0.Final-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.9.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.9.0.Final-SNAPSHOT > {code} > > 5. Close (do not resolve) this JIRA when done. > > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for updatesite task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26433) For JBIDE 4.10.0.AM1: Prepare for 4.10.0.AM1 / 12.10.0.AM1 [updatesite]

by Nick Boldt (Jira)

[ https://issues.jboss.org/browse/JBIDE-26433?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-26433. ------------------------------ Resolution: Done > For JBIDE 4.10.0.AM1: Prepare for 4.10.0.AM1 / 12.10.0.AM1 [updatesite] > ----------------------------------------------------------------------- > > Key: JBIDE-26433 > URL: https://issues.jboss.org/browse/JBIDE-26433 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: updatesite > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.10.0.AM1 > > > For JBIDE 4.10.0.AM1 [updatesite]: Please perform the following tasks: > > 1. Check out your existing *{color:orange}master{color}* branch: > > {code} > git checkout master > {code} > > 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.10.0.AM1-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.10.0.AM1-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.10.0.AM1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > > > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.9.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.9.0.Final-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.9.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.9.0.Final-SNAPSHOT > {code} > > 5. Close (do not resolve) this JIRA when done. > > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for updatesite task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26434) For JBIDE 4.10.0.AM1: Prepare for 4.10.0.AM1 / 12.10.0.AM1 [central-update]

by Nick Boldt (Jira)

Nick Boldt created JBIDE-26434: ---------------------------------- Summary: For JBIDE 4.10.0.AM1: Prepare for 4.10.0.AM1 / 12.10.0.AM1 [central-update] Key: JBIDE-26434 URL: https://issues.jboss.org/browse/JBIDE-26434 Project: Tools (JBoss Tools) Issue Type: Task Components: central-update Reporter: Nick Boldt Fix For: 4.10.0.AM1 For JBIDE 4.10.0.AM1 [central-update]: Please perform the following tasks: 1. Check out your existing *{color:orange}master{color}* branch: {code} git checkout master {code} 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.10.0.AM1-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.10.0.AM1-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: * *{color:orange}4.10.0.AM1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. {code} mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT {code} 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.9.0.Final-SNAPSHOT {code} mvn clean verify -Dtpc.version=4.9.0.Final-SNAPSHOT {code} 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.9.0.Final-SNAPSHOT {code} mvn clean verify -Dtpc.version=4.9.0.Final-SNAPSHOT {code} 5. Close (do not resolve) this JIRA when done. 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for central-update task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26434) For JBIDE 4.10.0.AM1: Prepare for 4.10.0.AM1 / 12.10.0.AM1 [central-update]

by Nick Boldt (Jira)

[ https://issues.jboss.org/browse/JBIDE-26434?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-26434: ---------------------------------- Assignee: Nick Boldt > For JBIDE 4.10.0.AM1: Prepare for 4.10.0.AM1 / 12.10.0.AM1 [central-update] > --------------------------------------------------------------------------- > > Key: JBIDE-26434 > URL: https://issues.jboss.org/browse/JBIDE-26434 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: central-update > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.10.0.AM1 > > > For JBIDE 4.10.0.AM1 [central-update]: Please perform the following tasks: > > 1. Check out your existing *{color:orange}master{color}* branch: > > {code} > git checkout master > {code} > > 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.10.0.AM1-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.10.0.AM1-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.10.0.AM1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > > > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.9.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.9.0.Final-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.9.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.9.0.Final-SNAPSHOT > {code} > > 5. Close (do not resolve) this JIRA when done. > > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for central-update task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian Jira (v7.12.1#712002)

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