June 2020 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-27330) For JBIDE 4.16.0.Final: Prepare for 4.16.0.Final / 12.16.0.GA [forge]

by Stephane Bouchet (Jira)

Stephane Bouchet created JBIDE-27330: ---------------------------------------- Summary: For JBIDE 4.16.0.Final: Prepare for 4.16.0.Final / 12.16.0.GA [forge] Key: JBIDE-27330 URL: https://issues.redhat.com/browse/JBIDE-27330 Project: Tools (JBoss Tools) Issue Type: Task Components: forge Reporter: Stephane Bouchet Fix For: 4.16.0.Final For JBIDE 4.16.0.Final [forge]: 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.16.0.Final-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.16.0.Final-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: * *{color:orange}4.16.0.Final-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.16.0.AM1-SNAPSHOT {code} mvn clean verify -Dtpc.version=4.16.0.AM1-SNAPSHOT {code} 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.16.0.AM1-SNAPSHOT {code} mvn clean verify -Dtpc.version=4.16.0.AM1-SNAPSHOT {code} 5. Close (do not resolve) this JIRA when done. 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.redhat.com/issues/?jql=%28%28project%20%3D%20%22JBID...] to do, please complete them next. [Search for all task JIRA|https://issues.redhat.com/issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for forge task JIRA|https://issues.redhat.com/issues/?jql=%28%28project+in+%28JBDS%29+an...] -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-27328) For JBIDE 4.16.0.Final: Prepare for 4.16.0.Final / 12.16.0.GA [foundation]

by Stephane Bouchet (Jira)

Stephane Bouchet created JBIDE-27328: ---------------------------------------- Summary: For JBIDE 4.16.0.Final: Prepare for 4.16.0.Final / 12.16.0.GA [foundation] Key: JBIDE-27328 URL: https://issues.redhat.com/browse/JBIDE-27328 Project: Tools (JBoss Tools) Issue Type: Task Components: foundation Reporter: Stephane Bouchet Fix For: 4.16.0.Final For JBIDE 4.16.0.Final [foundation]: 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.16.0.Final-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.16.0.Final-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: * *{color:orange}4.16.0.Final-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.16.0.AM1-SNAPSHOT {code} mvn clean verify -Dtpc.version=4.16.0.AM1-SNAPSHOT {code} 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.16.0.AM1-SNAPSHOT {code} mvn clean verify -Dtpc.version=4.16.0.AM1-SNAPSHOT {code} 5. Close (do not resolve) this JIRA when done. 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.redhat.com/issues/?jql=%28%28project%20%3D%20%22JBID...] to do, please complete them next. [Search for all task JIRA|https://issues.redhat.com/issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for foundation task JIRA|https://issues.redhat.com/issues/?jql=%28%28project+in+%28JBDS%29+an...] -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-27328) For JBIDE 4.16.0.Final: Prepare for 4.16.0.Final / 12.16.0.GA [foundation]

by Stephane Bouchet (Jira)

[ https://issues.redhat.com/browse/JBIDE-27328?page=com.atlassian.jira.plug... ] Stephane Bouchet reassigned JBIDE-27328: ---------------------------------------- Assignee: Rob Stryker > For JBIDE 4.16.0.Final: Prepare for 4.16.0.Final / 12.16.0.GA [foundation] > -------------------------------------------------------------------------- > > Key: JBIDE-27328 > URL: https://issues.redhat.com/browse/JBIDE-27328 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: foundation > Reporter: Stephane Bouchet > Assignee: Rob Stryker > Priority: Blocker > Labels: task > Fix For: 4.16.0.Final > > > For JBIDE 4.16.0.Final [foundation]: 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.16.0.Final-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.16.0.Final-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.16.0.Final-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.16.0.AM1-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.16.0.AM1-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.16.0.AM1-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.16.0.AM1-SNAPSHOT > {code} > > 5. Close (do not resolve) this JIRA when done. > > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.redhat.com/issues/?jql=%28%28project%20%3D%20%22JBID...] to do, please complete them next. > > [Search for all task JIRA|https://issues.redhat.com/issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for foundation task JIRA|https://issues.redhat.com/issues/?jql=%28%28project+in+%28JBDS%29+an...] -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-27327) Update 4.16.0.Final Target Platform for 2020-06 GA

by Stephane Bouchet (Jira)

Stephane Bouchet created JBIDE-27327: ---------------------------------------- Summary: Update 4.16.0.Final Target Platform for 2020-06 GA Key: JBIDE-27327 URL: https://issues.redhat.com/browse/JBIDE-27327 Project: Tools (JBoss Tools) Issue Type: Task Components: target-platform Affects Versions: 4.16.0.AM1 Reporter: Stephane Bouchet Assignee: Stephane Bouchet Fix For: 4.16.0.Final Update TP with : wildwebdeveloper 0.10.0 linuxtools ( see JBIDE-27318 ) springide -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26463) Create Eclipse Marketplace entry for Dependency Analytics (fabric8 plugin)

by Stephane Bouchet (Jira)

[ https://issues.redhat.com/browse/JBIDE-26463?page=com.atlassian.jira.plug... ] Stephane Bouchet updated JBIDE-26463: ------------------------------------- Fix Version/s: 4.16.0.Final (was: 4.16.0.AM1) > Create Eclipse Marketplace entry for Dependency Analytics (fabric8 plugin) > -------------------------------------------------------------------------- > > Key: JBIDE-26463 > URL: https://issues.redhat.com/browse/JBIDE-26463 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: marketplace, updatesite > Affects Versions: 4.10.0.AM1 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.16.0.Final > > > Per discussion w/ [~mickael_istria] [~rpdavis] and [~jeffmaury], we should create a new Eclipse Marketplace entry for the fabric8 analytics plugin. > This will require that the plugin & feature have its own dedicated update site, unless we plan to just point the entry at the latest devstudio or jbosstools site. > Will also need to determine how to describe the plugin, provide an icon and/or screenshot, etc. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26458) Import Entities from DB with ManyToMany relationships doesn't manage mappedBy

by Stephane Bouchet (Jira)

[ https://issues.redhat.com/browse/JBIDE-26458?page=com.atlassian.jira.plug... ] Stephane Bouchet updated JBIDE-26458: ------------------------------------- Fix Version/s: 4.16.0.Final (was: 4.16.0.AM1) > Import Entities from DB with ManyToMany relationships doesn't manage mappedBy > ----------------------------------------------------------------------------- > > Key: JBIDE-26458 > URL: https://issues.redhat.com/browse/JBIDE-26458 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.6.0.Final > Environment: Eclipse: Oxygen.3a Release (4.7.3a) Build id: 20180405-1200 > DBMS: Sql Anywhere 17.0.9.4857 > Annotations jdk 1.5+ > Hibernate Version 5.2 > Reporter: Matteo Barrese > Assignee: Koen Aers > Priority: Major > Fix For: 4.16.0.Final > > > Import from entities tool does not correctly handle the bidirectional ManyToMany relationships because in some cases it does not define mappedBy on one side. > example: > {code:java} > public class SecGroup implements java.io.Serializable { > .... > @ManyToMany(fetch = FetchType.LAZY) > @JoinTable(name = "SecGroupUser", schema = "dbm", joinColumns = { > @JoinColumn(name = "GroupId", nullable = false, updatable = false) }, inverseJoinColumns = { > @JoinColumn(name = "UserId", nullable = false, updatable = false) }) > public Set<SsUsers> getSsUserses() { > return this.ssUserses; > } > .... > } > public class SsUsers implements java.io.Serializable { > ... > @ManyToMany(fetch = FetchType.LAZY) > @JoinTable(name = "SecGroupUser", schema = "dbm", joinColumns = { > @JoinColumn(name = "UserId", nullable = false, updatable = false) }, inverseJoinColumns = { > @JoinColumn(name = "GroupId", nullable = false, updatable = false) }) > public Set<SecGroup> getSecGroups() { > return this.secGroups; > } > ... > } > {code} > It must be for example > {code:java} > public class SecGroup implements java.io.Serializable { > .... > @ManyToMany(fetch = FetchType.LAZY, mappedBy = "secGroups") > public Set<SsUsers> getSsUserses() { > return this.ssUserses; > } > .... > } > public class SsUsers implements java.io.Serializable { > ... > @ManyToMany(fetch = FetchType.LAZY) > @JoinTable(name = "SecGroupUser", schema = "dbm", joinColumns = { > @JoinColumn(name = "UserId", nullable = false, updatable = false) }, inverseJoinColumns = { > @JoinColumn(name = "GroupId", nullable = false, updatable = false) }) > public Set<SecGroup> getSecGroups() { > return this.secGroups; > } > ... > } > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24551) reactivate Sonarcloud.io updates for jbosstools-server

by Stephane Bouchet (Jira)

[ https://issues.redhat.com/browse/JBIDE-24551?page=com.atlassian.jira.plug... ] Stephane Bouchet updated JBIDE-24551: ------------------------------------- Fix Version/s: 4.16.0.Final (was: 4.16.0.AM1) > reactivate Sonarcloud.io updates for jbosstools-server > ------------------------------------------------------ > > Key: JBIDE-24551 > URL: https://issues.redhat.com/browse/JBIDE-24551 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build, server > Reporter: Aurélien Pupier > Assignee: Rob Stryker > Priority: Major > Fix For: 4.16.0.Final > > Attachments: screenshot-1.png, screenshot-2.png > > > last update was the 21 February > !screenshot-1.png|thumbnail! > https://sonarcloud.io/dashboard?id=org.jboss.tools%3Aserver.all -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23066) Generating hbm.xml files always happens using the 3.5 runtime

by Stephane Bouchet (Jira)

[ https://issues.redhat.com/browse/JBIDE-23066?page=com.atlassian.jira.plug... ] Stephane Bouchet updated JBIDE-23066: ------------------------------------- Fix Version/s: 4.16.0.Final (was: 4.16.0.AM1) > Generating hbm.xml files always happens using the 3.5 runtime > ------------------------------------------------------------- > > Key: JBIDE-23066 > URL: https://issues.redhat.com/browse/JBIDE-23066 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.4.1.Final > Reporter: Koen Aers > Assignee: Koen Aers > Priority: Major > Fix For: 4.16.0.Final > > > This issue is related to JBIDE-22997 and JBIDE-23059. After implementing JBIDE-23059 the phenomenon described in JBIDE-22997 disappeared but the hbm.xml files are now always generated using the 3.5 runtime, even when the project is a hibernate project with a console configuration using another version. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26582) Add support for Quarkus based applications

by Stephane Bouchet (Jira)

[ https://issues.redhat.com/browse/JBIDE-26582?page=com.atlassian.jira.plug... ] Stephane Bouchet updated JBIDE-26582: ------------------------------------- Fix Version/s: 4.16.0.Final (was: 4.16.0.AM1) > Add support for Quarkus based applications > ------------------------------------------ > > Key: JBIDE-26582 > URL: https://issues.redhat.com/browse/JBIDE-26582 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.11.0.Final > Reporter: Jeff MAURY > Priority: Major > Labels: e2e > Fix For: 4.16.0.Final > > > We should support JBoss Tools based inner loop for Quarkus based applications. > In the first time support only OpenJDK based deployments as I'm not sure native image based deployments can support inner loop. > That would also probably means an update of the openJDK base image -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26548) Nullpointer when renaming inner class java variables - JSFRenameFieldParticipant

by Stephane Bouchet (Jira)

[ https://issues.redhat.com/browse/JBIDE-26548?page=com.atlassian.jira.plug... ] Stephane Bouchet updated JBIDE-26548: ------------------------------------- Fix Version/s: 4.16.0.Final (was: 4.16.0.AM1) > Nullpointer when renaming inner class java variables - JSFRenameFieldParticipant > -------------------------------------------------------------------------------- > > Key: JBIDE-26548 > URL: https://issues.redhat.com/browse/JBIDE-26548 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsf > Affects Versions: 4.10.0.AM1 > Environment: Linux with Eclipse 2018-12 > Reporter: Thomas Zauner > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.16.0.Final > > > Renaming of inner class java variables leads to an Nullpointer in JSFRenameFieldParticipant. The second rename is working, since the JSFRenameFieldParticipant is removed due to the exception. > {noformat} > !ENTRY org.eclipse.ltk.core.refactoring 4 10009 2019-02-07 08:02:57.183 > !MESSAGE Participant 'org.jboss.tools.jsf.model.handlers.bean.JSFRenameFieldParticipant' removed due to the following exception > !STACK 0 > java.lang.NullPointerException > at org.jboss.tools.jsf.model.pv.JSFProjectsTree.getProjectsRoot(JSFProjectsTree.java:45) > at org.jboss.tools.jsf.model.handlers.bean.JSFRenameFieldHelper.getBeanList(JSFRenameFieldHelper.java:48) > at org.jboss.tools.jsf.model.handlers.bean.JSFRenameFieldParticipant.createChange(JSFRenameFieldParticipant.java:68) > at org.eclipse.ltk.core.refactoring.participants.ProcessorBasedRefactoring.createChange(ProcessorBasedRefactoring.java:309) > at org.eclipse.jdt.internal.ui.refactoring.RefactoringExecutionHelper$Operation.run(RefactoringExecutionHelper.java:102) > at org.eclipse.jdt.internal.core.BatchOperation.executeOperation(BatchOperation.java:41) > at org.eclipse.jdt.internal.core.JavaModelOperation.run(JavaModelOperation.java:736) > at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2295) > at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2322) > at org.eclipse.jdt.core.JavaCore.run(JavaCore.java:5810) > at org.eclipse.jdt.internal.ui.actions.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:108) > at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122) > {noformat} > {code:java} > public class JavaClass { > private boolean first; // rename will work > public class InnerClass { > private boolean second; // rename leads to NPE > } > } > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 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 June 2020