January 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-25483) Maven New and Noteworthy for 4.5.2.AM3

by Jeff MAURY (JIRA)

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

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25477) CDI New and Noteworthy for 4.5.2.AM3

by Jeff MAURY (JIRA)

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

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25478) Hibernate New and Noteworthy for 4.5.2.AM3

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25478?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-25478. ------------------------------ Resolution: Rejected > Hibernate New and Noteworthy for 4.5.2.AM3 > --------------------------------------------------- > > Key: JBIDE-25478 > URL: https://issues.jboss.org/browse/JBIDE-25478 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: hibernate > Reporter: Jeff MAURY > Assignee: Koen Aers > Priority: Critical > Labels: task > Fix For: 4.5.2.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-25476 #comment Create N&N for Hibernate 4.5.2.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)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25480) Usage Analytics New and Noteworthy for 4.5.2.AM3

by Jeff MAURY (JIRA)

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

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25481) Forge New and Noteworthy for 4.5.2.AM3

by Jeff MAURY (JIRA)

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

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4638) Failing tests for quickstarts [jts][ejb-security-interceptors] on WildFly-11

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBDS-4638?page=com.atlassian.jira.plugin.... ] Josef Kopriva reassigned JBDS-4638: ----------------------------------- Assignee: Vojtech Prusa > Failing tests for quickstarts [jts][ejb-security-interceptors] on WildFly-11 > ---------------------------------------------------------------------------- > > Key: JBDS-4638 > URL: https://issues.jboss.org/browse/JBDS-4638 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: project-examples > Affects Versions: 11.2.0.AM2 > Environment: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/examples... > Server: WF11 > Quickstart: 11.x > Reporter: Vojtech Prusa > Assignee: Vojtech Prusa > Attachments: jts.errors.txt > > > Automation fails because of error (manually tested in attachment) for this quickstart. > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/examples... > and > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/examples... > I suppose this error is duplicate to: > https://bugzilla.redhat.com/show_bug.cgi?id=1192591 > Using mentioned workaround I get: > Description Resource Path Location Type > Referenced file contains errors (jar:file:~/ws/devstudio-11.2.0.AM2-v20171210-2039-B1746/studio/plugins/org.jboss.tools.as.catalog_3.5.2.v20171114-2016.jar!/schema/xsd/jboss-ejb3-spec-2_0.xsd). For more information, right click on the message in the Problems View and select "Show Details..." jboss-ejb3.xml /jts-application-component-2/src/main/resources/META-INF line 1 XML Problem > What I did to get rid of this error message was removing from xsi:schemaLocation string "http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-2_0.xsd" > thought i think this is wrong approach and i did not deploy this quickstart yet. > Please make a comment > [~wolfc] [~rob.stryker] [~sgilda] > Thank you. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4636) Failing tests for quickstart [spring-petclinic] on WildFly-11

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBDS-4636?page=com.atlassian.jira.plugin.... ] Josef Kopriva reassigned JBDS-4636: ----------------------------------- Assignee: Vojtech Prusa > Failing tests for quickstart [spring-petclinic] on WildFly-11 > ------------------------------------------------------------- > > Key: JBDS-4636 > URL: https://issues.jboss.org/browse/JBDS-4636 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: project-examples > Affects Versions: 11.2.0.AM2 > Environment: jdk=jdk1.8,label=fedora26 > jdk=jdk1.8,label=ubuntu1704 > jdk=openjdk-1.8,label=fedora26 > jdk=openjdk-1.8,label=win10 > Server: WF11 > Quickstarts: 11.x > Reporter: Vojtech Prusa > Assignee: Vojtech Prusa > Attachments: spring-petclinic.errors.txt > > > There are JavaScript related errors in JBDS for which automation fails. > Related test reports: > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/examples... > Test results: > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/examples... > I think there may be some other configuration for JavaScript support necessary. > I was successful at deploying this quickstart. > Errors bothering me most are: > ')' expected intro.js /spring-petclinic/src/main/webapp/vendors/jquery/src line 20 > and > The element type "meta" must be terminated by the matching end-tag "</meta>". > I have added Spring IDE plugin to JBDS but I still get same errors. > Please comment [~n1hility] [~ctomc] [~trepel] [~sgilda] > Thank you. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ERT-536) [Gtk3][Webkit2] Port clearSessions(), getCookie() and setCookie() to webkit2. [EBZ#522181]

by Roland Grunberg (JIRA)

[ https://issues.jboss.org/browse/ERT-536?page=com.atlassian.jira.plugin.sy... ] Roland Grunberg closed ERT-536. ------------------------------- Resolution: Done Let's just close this for now and file newer bugs as needed for this. With https://trac.webkit.org/changeset/225054/webkit it seems we just need to wait for a release and see what we have to work with. > [Gtk3][Webkit2] Port clearSessions(), getCookie() and setCookie() to webkit2. [EBZ#522181] > ------------------------------------------------------------------------------------------ > > Key: ERT-536 > URL: https://issues.jboss.org/browse/ERT-536 > Project: Eclipse Release Train > Issue Type: Task > Components: Platform > Reporter: Friendly Jira Robot > Assignee: Roland Grunberg > Labels: SWT, bzira > > Created attachment 270164 > hs_err_pid20835.log > Build ID: 20170907-1650_eclipse-cpp-oxygen-1-RC3-linux.gtk.x86_64.tar.gz > Host: Ubuntu 16.04.2 on Virtualbox 5.1.26, 3D acceleration + guest utilities on > GTK: libwebkit2gtk-4.0-37:amd64 2.16.6-0ubuntu0.16.04.1 > Eclipse crashed hard on me with attached hs_err_pid20835.log , here are the top frames from the stack: > Java frames: (J=compiled Java code, j=interpreted, Vv=VM code) > j org.eclipse.swt.internal.webkit.WebKitGTK._webkit_get_default_session()J+0 > j org.eclipse.swt.internal.webkit.WebKitGTK.webkit_get_default_session()J+7 > j org.eclipse.swt.browser.WebKit.lambda$0()V+7 > j org.eclipse.swt.browser.WebKit$$Lambda$328.run()V+0 > j org.eclipse.swt.browser.WebBrowser.clearSessions()V+9 > j org.eclipse.swt.browser.Browser.clearSessions()V+0 > j org.eclipse.oomph.ui.HelpSupport.setHelpPath(Ljava/lang/String;)V+31 > j org.eclipse.oomph.ui.HelpSupport.updateHelp()V+11 > The issue is not reproducible, but here's the steps I had performed: > 1. Launch Eclipse, close the welcome screen (Note: Welcome screen is empty) > 2. Import a C/C++ project, allow it to be fully indexed > 3. Launch a GDB debug session > 4. Window > Preferences, enable the Oomph Preference Recorder > 5. Preferences:Filter:GDB, Enable "GDB Traces", click "Apply and Close" > --> The Oomph confirmation dialog briefly appeared > --> Then an Ubuntu dialog said "WebKitNetworkProcess died" and Eclipse was gone -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-964) Confusing versions of BPMN2 features

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-964?page=com.atlassian.jira.plugin.... ] Paul Leacu closed JBTIS-964. ---------------------------- Resolution: Rejected Hey Andrej - There are actually two bpmn2 modeling tooling repos. Currently we're using: http://download.eclipse.org/modeling/mdt/bpmn2/updates/oxygen/1.4.0 and http://download.eclipse.org/bpmn2-modeler/updates/oxygen/1.4.2/ I'd have merged the 'Model Development Tools' with the "Modeling Editor' by now but it is what it is... > Confusing versions of BPMN2 features > ------------------------------------ > > Key: JBTIS-964 > URL: https://issues.jboss.org/browse/JBTIS-964 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: BPMN2, distribution > Affects Versions: 10.0.0.GA > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > > Devstudio IS 10.0.0.CR1 contains the following BPMN2 bundles > - org.eclipse.bpmn2.feature_1.3.1.Final-v20160927-2047-B56.jar > - org.eclipse.bpmn2.modeler.examples_1.3.2.Final-v20161020-1541-B59.jar > - org.eclipse.bpmn2.modeler.runtime.jboss_1.3.2.Final-v20161020-1541-B59.jar > - org.eclipse.bpmn2.modeler_1.3.2.Final-v20161020-1541-B59.jar > As you can see there are two versions which is very confusing. For example, DevstudioIS 10.0.0.Alpha1 contains BPMN2 versions 1.3.0.Final-v20160119-1832 and 1.3.1.Final-v20160831-1132-B55, so how can customer specify correct version in case of reporting an issue? > I don't think there are two standalone projects of BPMN2, so there is no reason to use 2 versions. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-964) Confusing versions of BPMN2 features

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-964?page=com.atlassian.jira.plugin.... ] Paul Leacu reassigned JBTIS-964: -------------------------------- Assignee: Paul Leacu (was: Robert (Bob) Brodt) > Confusing versions of BPMN2 features > ------------------------------------ > > Key: JBTIS-964 > URL: https://issues.jboss.org/browse/JBTIS-964 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: BPMN2, distribution > Affects Versions: 10.0.0.GA > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > > Devstudio IS 10.0.0.CR1 contains the following BPMN2 bundles > - org.eclipse.bpmn2.feature_1.3.1.Final-v20160927-2047-B56.jar > - org.eclipse.bpmn2.modeler.examples_1.3.2.Final-v20161020-1541-B59.jar > - org.eclipse.bpmn2.modeler.runtime.jboss_1.3.2.Final-v20161020-1541-B59.jar > - org.eclipse.bpmn2.modeler_1.3.2.Final-v20161020-1541-B59.jar > As you can see there are two versions which is very confusing. For example, DevstudioIS 10.0.0.Alpha1 contains BPMN2 versions 1.3.0.Final-v20160119-1832 and 1.3.1.Final-v20160831-1132-B55, so how can customer specify correct version in case of reporting an issue? > I don't think there are two standalone projects of BPMN2, so there is no reason to use 2 versions. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 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 January 2018