September 2019 - jbosstools-issues

[JBoss JIRA] (JBIDE-26863) Make sure jbosstools-quarkus is integrated

by Jeff MAURY (Jira)

Jeff MAURY created JBIDE-26863: ---------------------------------- Summary: Make sure jbosstools-quarkus is integrated Key: JBIDE-26863 URL: https://issues.jboss.org/browse/JBIDE-26863 Project: Tools (JBoss Tools) Issue Type: Task Components: build Affects Versions: 4.13.0.Final Reporter: Jeff MAURY Assignee: stephane bouchet Fix For: 4.14.0.AM1 Once 12.13.0.Final is released, we should make sure jbosstools-quarkus is integrated into our release engineering. This includes: * disabling/enabling jbosstools-quarkus_master * aggregating jbosstools-quarkus P2 site * integrating jbosstools-quarkus repo into the parent POM update job * adding jbosstools quarkus feature to the list of included features for CodeReady Studio -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26475) Update lucene version in target platform

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26475?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26475: ------------------------------- Fix Version/s: 4.13.0.Final (was: 4.13.0.AM1) > Update lucene version in target platform > ---------------------------------------- > > Key: JBIDE-26475 > URL: https://issues.jboss.org/browse/JBIDE-26475 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build, target-platform > Affects Versions: 4.10.0.AM1 > Reporter: Josef Kopriva > Priority: Major > Fix For: 4.13.0.Final > > > Investigate and identify why do we multiple version of org.apache.lucene.8 packages in target plaform(e.g. in eclipse TP is version 7.5, but in target platform is 7.1). > It would be also nice, if comments would be added in target file to know why we have different versions. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26464) Relabel fabric8 analytics as dependency analytics in Central discovery

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26464?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26464: ------------------------------- Fix Version/s: 4.13.0.Final (was: 4.13.0.AM1) > Relabel fabric8 analytics as dependency analytics in Central discovery > ---------------------------------------------------------------------- > > Key: JBIDE-26464 > URL: https://issues.jboss.org/browse/JBIDE-26464 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central-update > Affects Versions: 4.10.0.AM1 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.13.0.Final > > > Per discussion w/ Mickael Istria Bob Davis and Jeff MAURY, we should rename the Central connector for fabric8 analytics to match the new connector in Eclipse Marketplace (JBIDE-26463). -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 12 months

1
0
0 / 0

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

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26463?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26463: ------------------------------- Fix Version/s: 4.13.0.Final (was: 4.13.0.AM1) > Create Eclipse Marketplace entry for Dependency Analytics (fabric8 plugin) > -------------------------------------------------------------------------- > > Key: JBIDE-26463 > URL: https://issues.jboss.org/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.13.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)

4 years, 12 months

1
0
0 / 0

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

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26458?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26458: ------------------------------- Fix Version/s: 4.13.0.Final (was: 4.13.0.AM1) > Import Entities from DB with ManyToMany relationships doesn't manage mappedBy > ----------------------------------------------------------------------------- > > Key: JBIDE-26458 > URL: https://issues.jboss.org/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.13.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)

4 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26405) JSF New and Noteworthy for 4.10.0.AM1

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26405?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26405: ------------------------------- Fix Version/s: 4.13.0.Final (was: 4.13.0.AM1) > JSF New and Noteworthy for 4.10.0.AM1 > ---------------------------------------------------- > > Key: JBIDE-26405 > URL: https://issues.jboss.org/browse/JBIDE-26405 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: jsf, jsp/jsf/xml/html-source-editing > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Critical > Labels: task > Fix For: 4.13.0.Final > > > Jeff MAURY, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed JSF JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for JSF, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for JSF by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form... {code}JBIDE-26391 #comment Create N&N for JSF 4.10.0.AM1 #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for JSF for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26404) OpenShift New and Noteworthy for 4.10.0.AM1

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26404?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26404: ------------------------------- Fix Version/s: 4.13.0.Final (was: 4.13.0.AM1) > OpenShift New and Noteworthy for 4.10.0.AM1 > ---------------------------------------------------- > > Key: JBIDE-26404 > URL: https://issues.jboss.org/browse/JBIDE-26404 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: cdk, openshift > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Critical > Labels: task > Fix For: 4.13.0.Final > > > Andre Dietisheim, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed OpenShift JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for OpenShift, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for OpenShift by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form... {code}JBIDE-26391 #comment Create N&N for OpenShift 4.10.0.AM1 #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for OpenShift for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26403) Base New and Noteworthy for 4.10.0.AM1

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26403?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26403: ------------------------------- Fix Version/s: 4.13.0.Final (was: 4.13.0.AM1) > Base New and Noteworthy for 4.10.0.AM1 > ---------------------------------------------------- > > Key: JBIDE-26403 > URL: https://issues.jboss.org/browse/JBIDE-26403 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: common, foundation, usage > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Critical > Labels: task > Fix For: 4.13.0.Final > > > Jeff MAURY, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Base JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for Base, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Base by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form... {code}JBIDE-26391 #comment Create N&N for Base 4.10.0.AM1 #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for Base for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26402) Server New and Noteworthy for 4.10.0.AM1

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26402?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26402: ------------------------------- Fix Version/s: 4.13.0.Final (was: 4.13.0.AM1) > Server New and Noteworthy for 4.10.0.AM1 > ---------------------------------------------------- > > Key: JBIDE-26402 > URL: https://issues.jboss.org/browse/JBIDE-26402 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: archives, jmx, server > Reporter: Jeff MAURY > Assignee: Rob Stryker > Priority: Critical > Labels: task > Fix For: 4.13.0.Final > > > Rob Stryker, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Server JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for Server, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Server by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form... {code}JBIDE-26391 #comment Create N&N for Server 4.10.0.AM1 #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for Server for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26401) Batch New and Noteworthy for 4.10.0.AM1

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26401?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26401: ------------------------------- Fix Version/s: 4.13.0.Final (was: 4.13.0.AM1) > Batch New and Noteworthy for 4.10.0.AM1 > ---------------------------------------------------- > > Key: JBIDE-26401 > URL: https://issues.jboss.org/browse/JBIDE-26401 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: batch > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Critical > Labels: task > Fix For: 4.13.0.Final > > > Jeff MAURY, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Batch JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for Batch, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Batch by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form... {code}JBIDE-26391 #comment Create N&N for Batch 4.10.0.AM1 #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for Batch for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 12 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues September 2019