July 2019 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24963) Create CDI 2 integration tests

by Zbyněk Červinka (Jira)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26698) Hibernate 3.5 - Can’t open connection

by Juan Marchionatto (Jira)

[ https://issues.jboss.org/browse/JBIDE-26698?page=com.atlassian.jira.plugi... ] Juan Marchionatto commented on JBIDE-26698: ------------------------------------------- Thank you [~koen.aers]. Just installed snapshot and works well. > Hibernate 3.5 - Can’t open connection > ------------------------------------- > > Key: JBIDE-26698 > URL: https://issues.jboss.org/browse/JBIDE-26698 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.12.0.Final > Reporter: Josef Kopriva > Assignee: Koen Aers > Priority: Major > Fix For: 4.13.0.AM1 > > Attachments: missed_dependency.png > > > From https://developer.jboss.org/people/jrmarchio from thread https://developer.jboss.org/message/989820?et=watches.email.thread#989820 > {code:java} > Hi, I have a problem with Hibernate Tools 5.4.4.v20190328-1505 > > I am trying to make Hibernate Console work on my new eclipse installation (Version: 2019-03 (4.11.0)). > > Exception is: org.hibernate.exception.JDBCConnectionException: Cannot open connection > … > Caused by: java.sql.SQLException: No suitable driver found for jdbc:jtds:sqlserver://hidden-hostname:1433/hidden-db-name > > > Now, the driver is in the connection classpath, and I know it is OK, because if I only change the hibernate version to 4.3 or later, it works. With 4.0 or less, same exception. > > I can’t just use it with version 4.3, because in my real configuration (many more mappings) I have all mapping files with 3.5 DTD and other characteristics not supported after 3.5 (LONG definitions, etc). > > I have used hibernate console since long ago. I have had little struggle to make configuration work on other plugin installations, but this time I am getting out of ideas.. > > Previous working combination was not much older: eclipse Mars. 2 Release (4.5.2), same hibernate (3.5) Hibernate tools 5.0.1.Final-v20160331-1852-B88 > > Can anybody help me to find out what could be generating the problem? > > Any information about some important changes between 5.0.1 and 5.0.4? > > Thank you in advance > --- > Juan > {code} > {code:java} > Trying to debug the code, I found that no matter which hibernate target version is selected, code always calls a SessionFactoryImpl from hibernate 4.0-Final, which could be the reason why queries start working selecting hibernate version 4.3 or higher (4.3 is the lowest selectable version higher than 4.0). > > Could anybody who knows this project check this? > > Thank you > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ERT-740) [GTK] Improve accuracy of Color.get[Red|Blue|Green] methods [EBZ#549181]

by Eric Williams (Jira)

[ https://issues.jboss.org/browse/ERT-740?page=com.atlassian.jira.plugin.sy... ] Eric Williams resolved ERT-740. ------------------------------- Resolution: Done > [GTK] Improve accuracy of Color.get[Red|Blue|Green] methods [EBZ#549181] > ------------------------------------------------------------------------ > > Key: ERT-740 > URL: https://issues.jboss.org/browse/ERT-740 > Project: Eclipse Release Train > Issue Type: Task > Components: Platform > Reporter: Friendly Jira Robot > Assignee: Eric Williams > Priority: Major > Labels: SWT, bzira > > As discussed in bug 549101, the Color.getRed(), getBlue(), and getGreen() methods need to be adjusted for better accuracy. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26744) Server adapter: "Clean" required after changing the war name

by André Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBIDE-26744?page=com.atlassian.jira.plugi... ] André Dietisheim commented on JBIDE-26744: ------------------------------------------ Turns out that changing the deployment name in the deployment page ends up in nothing being published by Eclipse/WTP. Rsync thus has no new artifacts to sync. I implemented a workaround where I trigger a full deploy when the "Deployment" page in the server editor is saved. > Server adapter: "Clean" required after changing the war name > ------------------------------------------------------------ > > Key: JBIDE-26744 > URL: https://issues.jboss.org/browse/JBIDE-26744 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.13.0.AM1 > Reporter: André Dietisheim > Assignee: André Dietisheim > Priority: Major > Labels: server_adapter > Fix For: 4.13.0.AM1 > > > *Steps*: > # EXEC: create a new app by using the *jboss-webserver31-tomcat8-openshift:1.2* builder image > # ASSERT: *websocket-chat* application is imported into your workspace > # ASSERT: server adapter *jboss-webserver31-tomcat* is created > # ASSERT: In OpenShift explorer, below the service jboss-webserver31-tomcat*, you have the running pod (build is finished, pod running) > # EXEC: start the server adapter > # EXEC: open the server adapter editor and switch to "Deployment" Tag > # EXEC: edit "Deployment Location" > *Result*: > Server adapter is syncing, but in the "Console" you dont see new files being transferred > *Expected Result*: > As soon as a new deployment location is set, the new destination should be synced to the pod. > *Workaround*: > "Clean" the server adapter. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24963) Create CDI 2 integration tests

by Zbyněk Červinka (Jira)

[ https://issues.jboss.org/browse/JBIDE-24963?page=com.atlassian.jira.plugi... ] Zbyněk Červinka commented on JBIDE-24963: ----------------------------------------- 4. PR created, waiting for comments/merge. > Create CDI 2 integration tests > ------------------------------ > > Key: JBIDE-24963 > URL: https://issues.jboss.org/browse/JBIDE-24963 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: cdi, integration-tests > Affects Versions: 4.5.1.AM2 > Reporter: Lukáš Valach > Assignee: Zbyněk Červinka > Priority: Major > Fix For: 4.13.x > > > The support for CDI 2.0 has been added recently, see JBIDE-24949. > Spec: > http://docs.jboss.org/cdi/spec/2.0/cdi-spec.html > Change log: > https://issues.jboss.org/secure/ReleaseNote.jspa?version=12325406&styleNa... -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24963) Create CDI 2 integration tests

by Zbyněk Červinka (Jira)

[ https://issues.jboss.org/browse/JBIDE-24963?page=com.atlassian.jira.plugi... ] Zbyněk Červinka updated JBIDE-24963: ------------------------------------ Git Pull Request: https://github.com/jbosstools/jbosstools-integration-tests/pull/1947, https://github.com/jbosstools/jbosstools-integration-tests/pull/1949, https://github.com/jbosstools/jbosstools-integration-tests/pull/1954, https://github.com/jbosstools/jbosstools-integration-tests/pull/1957 (was: https://github.com/jbosstools/jbosstools-integration-tests/pull/1947, https://github.com/jbosstools/jbosstools-integration-tests/pull/1949, https://github.com/jbosstools/jbosstools-integration-tests/pull/1954) > Create CDI 2 integration tests > ------------------------------ > > Key: JBIDE-24963 > URL: https://issues.jboss.org/browse/JBIDE-24963 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: cdi, integration-tests > Affects Versions: 4.5.1.AM2 > Reporter: Lukáš Valach > Assignee: Zbyněk Červinka > Priority: Major > Fix For: 4.13.x > > > The support for CDI 2.0 has been added recently, see JBIDE-24949. > Spec: > http://docs.jboss.org/cdi/spec/2.0/cdi-spec.html > Change log: > https://issues.jboss.org/secure/ReleaseNote.jspa?version=12325406&styleNa... -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26399) Fuse Tools New and Noteworthy for 4.10.0.AM1

by Aurélien Pupier (Jira)

[ https://issues.jboss.org/browse/JBIDE-26399?page=com.atlassian.jira.plugi... ] Aurélien Pupier resolved JBIDE-26399. ------------------------------------- Resolution: Done done only maintenance, nothing new and noteworthy > Fuse Tools New and Noteworthy for 4.10.0.AM1 > ---------------------------------------------------- > > Key: JBIDE-26399 > URL: https://issues.jboss.org/browse/JBIDE-26399 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: fusetools, fusetools-extras > Reporter: Jeff MAURY > Assignee: Aurélien Pupier > Priority: Critical > Labels: task > Fix For: 4.13.0.AM1 > > > Lars Heinemann, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Fuse Tools 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 Fuse Tools, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Fuse Tools 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 Fuse Tools 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 Fuse Tools for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26744) Server adapter: "Clean" required after changing the war name

by André Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBIDE-26744?page=com.atlassian.jira.plugi... ] André Dietisheim updated JBIDE-26744: ------------------------------------- Description: *Steps*: # EXEC: create a new app by using the *jboss-webserver31-tomcat8-openshift:1.2* builder image # ASSERT: *websocket-chat* application is imported into your workspace # ASSERT: server adapter *jboss-webserver31-tomcat* is created # ASSERT: In OpenShift explorer, below the service jboss-webserver31-tomcat*, you have the running pod (build is finished, pod running) # EXEC: start the server adapter # EXEC: open the server adapter editor and switch to "Deployment" Tag # EXEC: edit "Deployment Location" *Result*: Server adapter is syncing, but in the "Console" you dont see new files being transferred *Expected Result*: As soon as a new deployment location is set, the new destination should be synced to the pod. *Workaround*: "Clean" the server adapter. was: *Steps*: # EXEC: create a new app by using the *jboss-webserver31-tomcat8-openshift:1.2* builder image # ASSERT: *websocket-chat* application is imported into your workspace # ASSERT: server adapter *jboss-webserver31-tomcat* is created # ASSERT: In OpenShift explorer, below the service jboss-webserver31-tomcat*, you have the running pod (build is finished, pod running) # EXEC: start the server adapter # EXEC: open the server adapter editor and switch to "Deployment" Tag # EXEC: edit "Deployment Location" Result: Server adapter is syncing, but in the "Console" you dont see new files being transferred Expected Result: As soon as a new deployment location is set, the new destination should be synced to the pod. Workaround: "Clean" the server adapter. > Server adapter: "Clean" required after changing the war name > ------------------------------------------------------------ > > Key: JBIDE-26744 > URL: https://issues.jboss.org/browse/JBIDE-26744 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.13.0.AM1 > Reporter: André Dietisheim > Priority: Major > Labels: server_adapter > Fix For: 4.13.0.AM1 > > > *Steps*: > # EXEC: create a new app by using the *jboss-webserver31-tomcat8-openshift:1.2* builder image > # ASSERT: *websocket-chat* application is imported into your workspace > # ASSERT: server adapter *jboss-webserver31-tomcat* is created > # ASSERT: In OpenShift explorer, below the service jboss-webserver31-tomcat*, you have the running pod (build is finished, pod running) > # EXEC: start the server adapter > # EXEC: open the server adapter editor and switch to "Deployment" Tag > # EXEC: edit "Deployment Location" > *Result*: > Server adapter is syncing, but in the "Console" you dont see new files being transferred > *Expected Result*: > As soon as a new deployment location is set, the new destination should be synced to the pod. > *Workaround*: > "Clean" the server adapter. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26744) Server adapter: "Clean" required after changing the war name

by André Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBIDE-26744?page=com.atlassian.jira.plugi... ] André Dietisheim reassigned JBIDE-26744: ---------------------------------------- Workaround Description: "Clean" the server adapter. Assignee: André Dietisheim > Server adapter: "Clean" required after changing the war name > ------------------------------------------------------------ > > Key: JBIDE-26744 > URL: https://issues.jboss.org/browse/JBIDE-26744 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.13.0.AM1 > Reporter: André Dietisheim > Assignee: André Dietisheim > Priority: Major > Labels: server_adapter > Fix For: 4.13.0.AM1 > > > *Steps*: > # EXEC: create a new app by using the *jboss-webserver31-tomcat8-openshift:1.2* builder image > # ASSERT: *websocket-chat* application is imported into your workspace > # ASSERT: server adapter *jboss-webserver31-tomcat* is created > # ASSERT: In OpenShift explorer, below the service jboss-webserver31-tomcat*, you have the running pod (build is finished, pod running) > # EXEC: start the server adapter > # EXEC: open the server adapter editor and switch to "Deployment" Tag > # EXEC: edit "Deployment Location" > *Result*: > Server adapter is syncing, but in the "Console" you dont see new files being transferred > *Expected Result*: > As soon as a new deployment location is set, the new destination should be synced to the pod. > *Workaround*: > "Clean" the server adapter. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26694) Server adapter: should be able to freely set a war name

by André Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBIDE-26694?page=com.atlassian.jira.plugi... ] André Dietisheim commented on JBIDE-26694: ------------------------------------------ Filed the issue where "clean" is required to JBIDE-26744. > Server adapter: should be able to freely set a war name > ------------------------------------------------------- > > Key: JBIDE-26694 > URL: https://issues.jboss.org/browse/JBIDE-26694 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.12.0.AM1 > Reporter: André Dietisheim > Assignee: André Dietisheim > Priority: Major > Labels: server_adapter > Fix For: 4.13.0.AM1 > > Attachments: console-output-1.png, console-output-2.png, deployment-page-edit-war-name.png, server-adapter-configuration.png, switch-location.png > > > For the server adapters in tools/as we have UI that allows a user to set the name of the deployment archive. We're missing this feature for the OpenShift server adapters currently. We're asked to add it. > Steps: > # EXEC: create a new app by using the *jboss-webserver31-tomcat8-openshift:1.2* builder image > # ASSERT: *websocket-chat* application is imported into your workspace > # ASSERT: server adapter *jboss-webserver31-tomcat* is created > # ASSERT: In OpenShift explorer, below the service jboss-webserver31-tomcat*, you have the running pod (build is finished, pod running) > # EXEC: start the server adapter > # ASSERT: RSync is executed and the output is visible in the "Console" > Result: > If you look closely at the output you see that the project is synced to the pod in a folder called *websocket-chat.jar* > !console-output-1.png! > Expected result: > I should be able to set the output folder to anything I want. Ex. we have a customer that wants the application war to be synced up into a folder *ROOT* (without the extension *.war*). > Currently, to achieve this I have to do the following: > # EXEC: create the following xml snippet (notice the *outputName* property for the module) > and make sure it reads as follows: > {code} > <?xml version="1.0" encoding="UTF-8"?> > <deployment> > <local> > <module id="org.eclipse.jst.jee.server:websocket-chat"> > <property key="tempLocation" value="" /> > <property key="location" value="" /> > <property key="outputName" value="ROOT" /> > </module> > </local> > </deployment> > {code} > # EXEC: html-encode, join it into a single line and copy it (into the clipboard) > # EXEC: open the properties for the server adapter and hit "Switch Location" > !switch-location.png! > # ASSERT: in my workspace, a new project *Servers* is created. It contains the configuration for my server adapter. > !server-adapter-configuration.png! > # EXEC: open the file with the *XML Editor* > # EXEC: in your *XML Editor*: go to the end of the line *<server auto-publish-setting="2"* and insert your html-encoded xml as a value to the attribute *org.jboss.ide.eclipse.as.core.util.deploymentPreferenceKey="* > {code} > <?xml version="1.0" encoding="UTF-8" standalone="no"?> > <server auto-publish-setting="2" auto-publish-time="2" hostname="jboss-webserver31-tomcat-test.192.168.64.76.nip.io" id="test@jboss-webserver31-tomcat" id-set="true" name="jboss-webserver31-tomcat (Service) at OpenShift 3 (192.168.64.76)" org.jboss.ide.eclipse.as.core.server.IGNORE_LAUNCH_COMMANDS="true" org.jboss.ide.eclipse.as.core.server.deployDirectoryType="custom" org.jboss.ide.eclipse.as.core.server.serverMode="openshift3" org.jboss.ide.eclipse.as.core.server.webPort="80" org.jboss.ide.eclipse.as.core.server.webPortAutoDetect="false" org.jboss.ide.eclipse.as.core.server.zipDeploymentsPreference="true" org.jboss.tools.openshift.Connection="https://developer@192.168.64.76:8443" org.jboss.tools.openshift.DeployProject="websocket-chat" org.jboss.tools.openshift.PodPath="/opt/webserver/webapps" org.jboss.tools.openshift.SERVER_START_ON_CREATION="false" org.jboss.tools.openshift.Service="test@jboss-webserver31-tomcat" org.jboss.tools.openshift.SourcePath="${workspace_loc:/websocket-chat}" port="80" runtime-id="test@jboss-webserver31-tomcat" server-type="org.jboss.tools.openshift.server.type" server-type-id="org.jboss.tools.openshift.server.type" start-timeout="450" stop-timeout="450" timestamp="2" org.jboss.ide.eclipse.as.core.util.deploymentPreferenceKey="<?xml version="1.0" encoding="UTF-8"?> <deployment> <local> <module id="org.eclipse.jst.jee.server:websocket-chat"> <property key="tempLocation" value="" /> <property key="location" value="" /> <property key="outputName" value="ROOT" /> </module> </local> </deployment>"> > <list key="modules" value0="websocket-chat::org.eclipse.jst.jee.server:websocket-chat::jst.web::3.0"/> > </server> > {code} > # EXEC: Save the editor and restart the server > Result: > Syncing now happens into a folder *ROOT* > !console-output-2.png! -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 8 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 July 2019