August 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-6100) Unambiguous hibernate configuration values in hibernate console

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-6100?page=com.atlassian.jira.plugin... ] Koen Aers updated JBIDE-6100: ----------------------------- Sprint: devex #119 August 2016 > Unambiguous hibernate configuration values in hibernate console > --------------------------------------------------------------- > > Key: JBIDE-6100 > URL: https://issues.jboss.org/browse/JBIDE-6100 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: hibernate > Affects Versions: 3.1.0.GA > Reporter: Jiri Peterka > Assignee: Koen Aers > Priority: Minor > Labels: new_and_noteworthy > Fix For: 4.2.x > > > There are some situations where hibernate console setting can be uncertain. It should be improved, for example: > Hibernate dialect is defined in hibernate.cfg.xml file and in options tab. Which value has priority? Such values should be active only on one place and should be unambiguous. Same for other duplicate values. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-6423) Launch Hibernate Code generation as external process functionality

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-6423?page=com.atlassian.jira.plugin... ] Koen Aers updated JBIDE-6423: ----------------------------- Sprint: (was: devex #119 August 2016) > Launch Hibernate Code generation as external process functionality > ------------------------------------------------------------------ > > Key: JBIDE-6423 > URL: https://issues.jboss.org/browse/JBIDE-6423 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: hibernate > Affects Versions: 3.2.0.Final > Reporter: Vitali Yemialyanchyk > Assignee: Koen Aers > Priority: Minor > Labels: new_and_noteworthy > Fix For: 4.0.x > > Attachments: JBIDE-6423_20100720.zip, JBIDE-6423_20100721.zip, JBIDE-6423_20100722.zip, JBIDE-6423_20100723.zip, screenshot-1.jpg > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22749) Improve the automatic finishing of FreeMarker constructs

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22749?page=com.atlassian.jira.plugi... ] Ondrej Dockal closed JBIDE-22749. --------------------------------- Verifired on Version: 10.1.0.AM3 Build id: AM3-v20160812-1839-B5760, closing. > Improve the automatic finishing of FreeMarker constructs > -------------------------------------------------------- > > Key: JBIDE-22749 > URL: https://issues.jboss.org/browse/JBIDE-22749 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: freemarker > Reporter: Daniel Dekany > Assignee: Alexey Kazakov > Labels: new_and_noteworthy > Fix For: 4.4.1.AM3 > > > Currently, when I type {{<#}} or {{<@}}, the editor automatically adds the closing {{>}}. It should also close {{</#}}, {{</@}}, {{${}}, and {{#{}} and {{<#--}}. Furthermore the way it auto-closes what it does is technically awkward, as it only inserts the {{>}} after the inserted {{#}} was shown and the resulting syntax highlighting was done, instead of inserting both characters in a single step. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22916) Deploy Docker Wizard: Deploying a docker image from OpenShift explorer does not fetch metadata

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22916?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-22916: ---------------------------------- Assignee: Jeff MAURY > Deploy Docker Wizard: Deploying a docker image from OpenShift explorer does not fetch metadata > ---------------------------------------------------------------------------------------------- > > Key: JBIDE-22916 > URL: https://issues.jboss.org/browse/JBIDE-22916 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Marián Labuda > Assignee: Jeff MAURY > Labels: deploy_docker_wizard, openshift_v3 > > When I am trying to deploy a docker image from context menu of a project in OpenShift explorer view and I paste image name (e.g. docker.io/openshift/hello-openshift), image metadata are not fetched/processed and thus there are no environment variables in the wizard and routing (routing wizard page is empty and cannot finish dialog - requires manual entry). This force user to enter the details manually, otherwise he would get deployed not working pod. This is happening only in case when user provide an image without any tag and thus there is/supposed to be assumed tag "latest". > You can observe that it works when using tag v1.2.1. Difference between images with tag v1.2.1 and latest is that v1.2.1 contains exposed ports also in container config, not just in general config of the image. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22916) Deploy Docker Wizard: Deploying a docker image from OpenShift explorer does not fetch metadata

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22916?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-22916: ------------------------------- Story Points: 8 > Deploy Docker Wizard: Deploying a docker image from OpenShift explorer does not fetch metadata > ---------------------------------------------------------------------------------------------- > > Key: JBIDE-22916 > URL: https://issues.jboss.org/browse/JBIDE-22916 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Marián Labuda > Labels: deploy_docker_wizard, openshift_v3 > > When I am trying to deploy a docker image from context menu of a project in OpenShift explorer view and I paste image name (e.g. docker.io/openshift/hello-openshift), image metadata are not fetched/processed and thus there are no environment variables in the wizard and routing (routing wizard page is empty and cannot finish dialog - requires manual entry). This force user to enter the details manually, otherwise he would get deployed not working pod. This is happening only in case when user provide an image without any tag and thus there is/supposed to be assumed tag "latest". > You can observe that it works when using tag v1.2.1. Difference between images with tag v1.2.1 and latest is that v1.2.1 contains exposed ports also in container config, not just in general config of the image. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-6096) Hibernate Code Generation Configuration in standard Run Configuration list

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-6096?page=com.atlassian.jira.plugin... ] Koen Aers resolved JBIDE-6096. ------------------------------ Resolution: Won't Fix What [~maxandersen] said. > Hibernate Code Generation Configuration in standard Run Configuration list > -------------------------------------------------------------------------- > > Key: JBIDE-6096 > URL: https://issues.jboss.org/browse/JBIDE-6096 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: hibernate > Affects Versions: 3.1.0.GA > Reporter: Jiri Peterka > Assignee: Koen Aers > Priority: Optional > Labels: new_and_noteworthy > Fix For: 4.3.x > > Attachments: screenshot-1.jpg > > > Hibernate Code generation configuration is separated from other run configuration. I can't see any reason why it's not part of other standard run configurations. It should be moved there. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-6096) Hibernate Code Generation Configuration in standard Run Configuration list

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-6096?page=com.atlassian.jira.plugin... ] Koen Aers closed JBIDE-6096. ---------------------------- Resolution: Rejected > Hibernate Code Generation Configuration in standard Run Configuration list > -------------------------------------------------------------------------- > > Key: JBIDE-6096 > URL: https://issues.jboss.org/browse/JBIDE-6096 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: hibernate > Affects Versions: 3.1.0.GA > Reporter: Jiri Peterka > Assignee: Koen Aers > Priority: Optional > Labels: new_and_noteworthy > Fix For: 4.3.x > > Attachments: screenshot-1.jpg > > > Hibernate Code generation configuration is separated from other run configuration. I can't see any reason why it's not part of other standard run configurations. It should be moved there. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22708) NullPointerException in AbstractKiePropertyPage.getResourceHandler

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22708?page=com.atlassian.jira.plugi... ] Koen Aers closed JBIDE-22708. ----------------------------- Resolution: Won't Fix The old jBPM tools are retired. > NullPointerException in AbstractKiePropertyPage.getResourceHandler > ------------------------------------------------------------------ > > Key: JBIDE-22708 > URL: https://issues.jboss.org/browse/JBIDE-22708 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jbpm > Reporter: Automated Error Reporting Bot > Assignee: Koen Aers > > The following problem was reported via the automated error reporting: > Message: HIDDEN > {noformat} > java.lang.NullPointerException: null > at org.kie.eclipse.navigator.preferences.AbstractKiePropertyPage.getResourceHandler(AbstractKiePropertyPage.java:85) > at org.kie.eclipse.navigator.preferences.ServerPropertyPage.createFieldEditors(ServerPropertyPage.java:31) > at org.kie.eclipse.navigator.preferences.FieldEditorPropertyPage.createContents(FieldEditorPropertyPage.java:183) > at org.kie.eclipse.navigator.preferences.AbstractKiePropertyPage.createContents(AbstractKiePropertyPage.java:47) > at org.eclipse.jface.preference.PreferencePage.createControl(PreferencePage.java:241) > at org.eclipse.jface.preference.PreferenceDialog.createPageControl(PreferenceDialog.java:1450) > at org.eclipse.jface.preference.PreferenceDialog$13.run(PreferenceDialog.java:1217) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50) > at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:173) > at org.eclipse.jface.preference.PreferenceDialog.showPage(PreferenceDialog.java:1209) > at org.eclipse.ui.internal.dialogs.FilteredPreferenceDialog.showPage(FilteredPreferenceDialog.java:608) > at org.eclipse.jface.preference.PreferenceDialog$9$1.run(PreferenceDialog.java:675) > at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) > at org.eclipse.jface.preference.PreferenceDialog$9.selectionChanged(PreferenceDialog.java:670) > at org.eclipse.jface.viewers.StructuredViewer$3.run(StructuredViewer.java:877) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50) > at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:173) > at org.eclipse.jface.viewers.StructuredViewer.firePostSelectionChanged(StructuredViewer.java:874) > at org.eclipse.jface.viewers.StructuredViewer.handlePostSelect(StructuredViewer.java:1243) > at org.eclipse.jface.viewers.StructuredViewer$5.widgetSelected(StructuredViewer.java:1269) > at org.eclipse.jface.util.OpenStrategy.firePostSelectionEvent(OpenStrategy.java:265) > at org.eclipse.jface.util.OpenStrategy.access$5(OpenStrategy.java:259) > at org.eclipse.jface.util.OpenStrategy$1$2.run(OpenStrategy.java:440) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3794) > {noformat} > Bundles: > | org.eclipse.core.runtime | 3.11.1.v20150903-1804 | 3.11.1.v20150903-1804 | > | org.eclipse.jface | 3.11.1.v20160128-1644 | 3.11.1.v20160128-1644 | > | org.eclipse.swt | 3.104.2.v20160212-1350 | 3.104.2.v20160212-1350 | > | org.eclipse.ui | 3.107.0.v20150507-1945 | 3.107.0.v20150507-1945 | > | org.kie.eclipse.navigator | 6.4.0.201601201107 | 6.4.1.Final-v20160503-1355-B205 | > Operating Systems: > | Linux | 2.6.32.1 | 4.4.0 | > | MacOSX | 10.11.5 | 10.11.5 | > | Windows | 6.2.0 | 10.0.0 | > The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/571952bee4b0cd449c...] for the latest data. > Thank you for your assistance. > Your friendly error-reports-inbox. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4002) OpenJDK detection does not work for build 1.8.0_101

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4002?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4002: -------------------------------- Sprint: devex #118 July 2016 > OpenJDK detection does not work for build 1.8.0_101 > --------------------------------------------------- > > Key: JBDS-4002 > URL: https://issues.jboss.org/browse/JBDS-4002 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.1.0.GA > Reporter: Denis Golovin > Assignee: Denis Golovin > > Because of changed format for version console output, installer cannot detect installed JVM. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4002) OpenJDK detection does not work for build 1.8.0_101

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4002?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4002: -------------------------------- Story Points: 1 > OpenJDK detection does not work for build 1.8.0_101 > --------------------------------------------------- > > Key: JBDS-4002 > URL: https://issues.jboss.org/browse/JBDS-4002 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.1.0.GA > Reporter: Denis Golovin > Assignee: Denis Golovin > > Because of changed format for version console output, installer cannot detect installed JVM. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 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 August 2016