June 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-26048) Webservices / Rest New and Noteworthy for 4.6.0.AM3

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26048?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-26048. ------------------------------ Resolution: Done > Webservices / Rest New and Noteworthy for 4.6.0.AM3 > --------------------------------------------------- > > Key: JBIDE-26048 > URL: https://issues.jboss.org/browse/JBIDE-26048 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: webservices > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Critical > Labels: task > Fix For: 4.6.0.AM3 > > > Jeff MAURY, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Webservices / Rest 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 Webservices / Rest, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Webservices / Rest 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-26045 #comment Create N&N for Webservices / Rest 4.6.0.AM3 #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 Webservices / Rest for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26050) Hibernate New and Noteworthy for 4.6.0.AM3

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26050?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-26050. ------------------------------ Resolution: Rejected > Hibernate New and Noteworthy for 4.6.0.AM3 > --------------------------------------------------- > > Key: JBIDE-26050 > URL: https://issues.jboss.org/browse/JBIDE-26050 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: hibernate > Reporter: Jeff MAURY > Assignee: Koen Aers > Priority: Critical > Labels: task > Fix For: 4.6.0.AM3 > > > Koen Aers, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Hibernate 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 Hibernate, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Hibernate 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-26045 #comment Create N&N for Hibernate 4.6.0.AM3 #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 Hibernate for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26069) Spring Boot Project configurator: Creating child module for main project fails

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26069?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-26069: ------------------------------------ See https://issues.jboss.org/browse/JBIDE-25504?focusedCommentId=13593949&pag... > Spring Boot Project configurator: Creating child module for main project fails > ------------------------------------------------------------------------------- > > Key: JBIDE-26069 > URL: https://issues.jboss.org/browse/JBIDE-26069 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.6.0.AM2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Critical > Labels: project_configurator, springboot > Fix For: 4.6.0.Final > > Attachments: image-2018-05-30-22-31-37-635.png > > > steps: > # ASSERT: We dont know for now, really. We can only reproduce this on [~jeffmaury]'s machine (happens to him in Windows and Linux - doesn't for others in Linux nor Mac). > # EXEC: import the 2 maven projects that are attached to JBIDE-25504 (camel-ose-springboot-xml and penguins > # EXEC: in project properties for project *camel-ose-springboot-xml*: pick "Deployment Assembly" > # ASSERT: verify that *penguins* is defined as child module > Result: > !image-2018-05-30-22-31-37-635.png! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26128) For JBIDE 4.6.0.Final: Prepare for 4.6.0.Final / 12.0.0.GA [jst]

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26128?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-26128. ------------------------------ Resolution: Done > For JBIDE 4.6.0.Final: Prepare for 4.6.0.Final / 12.0.0.GA [jst] > ---------------------------------------------------------------- > > Key: JBIDE-26128 > URL: https://issues.jboss.org/browse/JBIDE-26128 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: jst > Reporter: Nick Boldt > Assignee: Jeff MAURY > Priority: Blocker > Labels: task > Fix For: 4.6.0.Final > > > For JBIDE 4.6.0.Final [jst]: 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.6.0.Final-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.6.0.Final-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.6.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.80.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.80.0.Final-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.80.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.80.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 jst task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26122) For JBIDE 4.6.0.Final: Prepare for 4.6.0.Final / 12.0.0.GA [central]

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26122?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-26122. ------------------------------ Resolution: Done > For JBIDE 4.6.0.Final: Prepare for 4.6.0.Final / 12.0.0.GA [central] > -------------------------------------------------------------------- > > Key: JBIDE-26122 > URL: https://issues.jboss.org/browse/JBIDE-26122 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: central > Reporter: Nick Boldt > Assignee: Jeff MAURY > Priority: Blocker > Labels: task > Fix For: 4.6.0.Final > > > For JBIDE 4.6.0.Final [central]: 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.6.0.Final-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.6.0.Final-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.6.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.80.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.80.0.Final-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.80.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.80.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 task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26129) For JBIDE 4.6.0.Final: Prepare for 4.6.0.Final / 12.0.0.GA [livereload]

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26129?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-26129. ------------------------------ Resolution: Done > For JBIDE 4.6.0.Final: Prepare for 4.6.0.Final / 12.0.0.GA [livereload] > ----------------------------------------------------------------------- > > Key: JBIDE-26129 > URL: https://issues.jboss.org/browse/JBIDE-26129 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: livereload > Reporter: Nick Boldt > Assignee: Jeff MAURY > Priority: Blocker > Labels: task > Fix For: 4.6.0.Final > > > For JBIDE 4.6.0.Final [livereload]: 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.6.0.Final-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.6.0.Final-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.6.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.80.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.80.0.Final-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.80.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.80.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 livereload task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26127) For JBIDE 4.6.0.Final: Prepare for 4.6.0.Final / 12.0.0.GA [jsf]

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26127?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-26127. ------------------------------ Resolution: Done > For JBIDE 4.6.0.Final: Prepare for 4.6.0.Final / 12.0.0.GA [jsf] > ---------------------------------------------------------------- > > Key: JBIDE-26127 > URL: https://issues.jboss.org/browse/JBIDE-26127 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: jsf > Reporter: Nick Boldt > Assignee: Jeff MAURY > Priority: Blocker > Labels: task > Fix For: 4.6.0.Final > > > For JBIDE 4.6.0.Final [jsf]: 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.6.0.Final-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.6.0.Final-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.6.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.80.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.80.0.Final-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.80.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.80.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 jsf task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26030) VPE tests times out due to SWT on GTK 2.x: nsIWebBrowser is not available

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26030?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26030: ------------------------------- Fix Version/s: 4.6.0.AM3 (was: 4.6.0.Final) > VPE tests times out due to SWT on GTK 2.x: nsIWebBrowser is not available > ------------------------------------------------------------------------- > > Key: JBIDE-26030 > URL: https://issues.jboss.org/browse/JBIDE-26030 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core, visual-page-editor-templates > Affects Versions: 4.6.0.AM1 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Priority: Blocker > Fix For: 4.6.0.AM3 > > Attachments: Screenshot_2018-05-22_16-58-14.png, Screenshot_2018-05-22_17-06-17.png, Screenshot_2018-05-23_10-33-11.png, Screenshot_2018-05-23_10-46-44.png, dialog-wrong-engine.png > > > We've been having this problem for a while now with the VPE builds: > {code} > !MESSAGE Could not open the Visual Page Editor: > No more handles because no underlying browser available. > SWT on GTK 2.x detected. It is reccomended to use SWT on GTK 3.x and Webkit2 API. > !STACK 0 > org.eclipse.swt.SWTError: No more handles because no underlying browser available. > SWT on GTK 2.x detected. It is reccomended to use SWT on GTK 3.x and Webkit2 API. > at org.eclipse.swt.SWT.error(SWT.java:4578) > at org.eclipse.swt.browser.Browser.<init>(Browser.java:125) > at org.jboss.tools.vpe.xulrunner.browser.XulRunnerBrowser.<init>(XulRunnerBrowser.java:123) > at org.jboss.tools.vpe.xulrunner.editor.XulRunnerEditor.<init>(XulRunnerEditor.java:128){code} > from https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > or https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > or https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26040) Error for JAX-RS 2.1 @Context types

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26040?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26040: ------------------------------- Fix Version/s: 4.6.0.AM3 (was: 4.6.x) > Error for JAX-RS 2.1 @Context types > ----------------------------------- > > Key: JBIDE-26040 > URL: https://issues.jboss.org/browse/JBIDE-26040 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.5.3.Final > Reporter: Rich DiCroce > Assignee: Jeff MAURY > Fix For: 4.6.0.AM3 > > > JAX-RS 2.1 adds some new types that can be injected into methods using the Context annotation, e.g. Sse and SseEventSink. Currently, JBoss Tools flags these with an error: > {quote} > @Context annotation is only allowed on method parameters of type '[javax.ws.rs.core.HttpHeaders, javax.ws.rs.core.UriInfo, javax.ws.rs.core.Request, javax.servlet.http.HttpServletRequest, javax.servlet.http.HttpServletResponse, javax.servlet.ServletConfig, javax.servlet.ServletContext, javax.ws.rs.core.SecurityContext]'. > {quote} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26043) Two paths to OC client in properties view for OpenShift connection

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26043?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26043: ------------------------------- Fix Version/s: 4.6.0.Final (was: 4.6.x) > Two paths to OC client in properties view for OpenShift connection > ------------------------------------------------------------------ > > Key: JBIDE-26043 > URL: https://issues.jboss.org/browse/JBIDE-26043 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.6.0.AM2 > Reporter: Josef Kopriva > Assignee: Jeff MAURY > Priority: Minor > Labels: oc_binary, properties > Fix For: 4.6.0.Final > > Attachments: image-2018-05-28-14-48-08-877.png, screenshot-1.png, screenshot-2.png, screenshot-3.png, screenshot-4.png > > > !image-2018-05-28-14-48-08-877.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 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 2018