February 2019 - jbosstools-issues

[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.11.0.Final (was: 4.11.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.11.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.12.1#712002)

5 years, 3 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.11.0.Final (was: 4.11.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.11.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.12.1#712002)

5 years, 3 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.11.0.Final (was: 4.11.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.11.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.12.1#712002)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26452) Explore existing proxy server set up solutions outside RH - proxy requirements definition

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26452?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26452: ------------------------------- Fix Version/s: 4.11.0.Final (was: 4.11.0.AM1) > Explore existing proxy server set up solutions outside RH - proxy requirements definition > ----------------------------------------------------------------------------------------- > > Key: JBIDE-26452 > URL: https://issues.jboss.org/browse/JBIDE-26452 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, qa > Affects Versions: 4.10.0.AM1 > Environment: Linux > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Major > Labels: quality > Fix For: 4.11.0.Final > > > Explore existing solutions for proxy configuration that could be done at one step without requiring deep user knowledge. > Existing docker images with squid (other?) proxy. Licensing, usage within RH intranet. Is there an open source code? > Requirements for proxy solution: > * Supports HTTP and HTTPS protocols > * Clear and configurable logging and other tools > * runs on linux > * Open Source solution > * License usable "in house" (can be use for profit = in enterprise environment) > * Project is alive/maintained - or we would must maintain our own fork? > * Community > * Code on github - preferably > * uses issue tracking system > Requirements for putting proxy into action: > * easy to deploy solution > * does not require user knowledge of proxy configuration - minimalist config > * can be updated at place > * RH certificate can be used -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26456) Provision Rhel 8 image with JBDS labels and add it to jenkins

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26456?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26456: ------------------------------- Fix Version/s: 4.11.0.Final (was: 4.11.0.AM1) > Provision Rhel 8 image with JBDS labels and add it to jenkins > ------------------------------------------------------------- > > Key: JBIDE-26456 > URL: https://issues.jboss.org/browse/JBIDE-26456 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, qa > Affects Versions: 4.10.0.AM1 > Environment: Linux > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Major > Labels: jenkins, openstack > Fix For: 4.11.0.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 3 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.11.0.Final (was: 4.11.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: Matt B > Assignee: Koen Aers > Priority: Major > Fix For: 4.11.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.12.1#712002)

5 years, 3 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.11.0.Final (was: 4.11.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.11.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.12.1#712002)

5 years, 3 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.11.0.Final (was: 4.11.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.11.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.12.1#712002)

5 years, 3 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.11.0.Final (was: 4.11.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.11.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.12.1#712002)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26477) Update 4.11.0.AM1 TP (Docker tooling, ...)

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26477?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26477: ------------------------------- Fix Version/s: 4.11.0.Final (was: 4.11.0.AM1) > Update 4.11.0.AM1 TP (Docker tooling, ...) > ------------------------------------------ > > Key: JBIDE-26477 > URL: https://issues.jboss.org/browse/JBIDE-26477 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build, target-platform > Affects Versions: 4.10.0.AM1 > Reporter: Josef Kopriva > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.11.0.Final > > Attachments: jbtcentraltarget.p2diff.txt, p2diff_4.11.0.AM1-4.10.0.AM1.txt, p2diff_4.11.0.AM1-4.11.0.AM1-previous.txt, p2diff_4.11.0.AM1-cameltooling-1.0.0.201812030843.txt, p2diff_4.11.0.AM1-m2e-1.10.txt > > > We should update docker tooling on TP, there is a fix for JDK 11: https://bugs.eclipse.org/bugs/show_bug.cgi?id=539483 -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 3 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 February 2019