July 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22283) reveng *.java emitter does not escape java keyword 'return' as variable name

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22283?page=com.atlassian.jira.plugi... ] Koen Aers resolved JBIDE-22283. ------------------------------- Resolution: Rejected I was able to reproduce this issue (see https://github.com/hibernate/hibernate-tools/commit/eb564fd1e7bd1b6582fb8...) but I have come to the conclusion that it is a user problem. The use of the 'return' name is a choice of the user and can simply be worked around by naming the property 'return_' instead in the reveng,xml file. So I am going to resolve this issue as rejected. Feel free to put in new arguments if you think this is not correct. > reveng *.java emitter does not escape java keyword 'return' as variable name > ---------------------------------------------------------------------------- > > Key: JBIDE-22283 > URL: https://issues.jboss.org/browse/JBIDE-22283 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.3.x > Environment: Eclipse Mars > Reporter: Darryl Miles > Assignee: Koen Aers > Fix For: 4.4.1.AM2 > > > reveng *.java emitter does not escape java keyword 'return' as variable name > <table name="oc_return_history"> > <foreign-key constraint-name="FK_oc_return_history__return_id" foreign-table="oc_return"> > <column-ref local-column="return_id" foreign-column="return_id"/> >  > <many-to-one property="return"/> > </foreign-key> > </table> > The expected output would be: > private Return _return; > but actual output is: > private Return return; -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22592) Application wizard: Failed even though provided required value to parameters

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22592?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-22592: ---------------------------------------- Assignee: Andre Dietisheim (was: Jeff MAURY) Resolution: Done replaced https://github.com/jbosstools/jbosstools-openshift/pull/1250 by https://github.com/jbosstools/jbosstools-openshift/pull/1261 and applied it to master. > Application wizard: Failed even though provided required value to parameters > ---------------------------------------------------------------------------- > > Key: JBIDE-22592 > URL: https://issues.jboss.org/browse/JBIDE-22592 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Environment: JBoss OpenShift 3 Tools 3.3.0.Final-v20160610-1836-B1369 > JBoss OpenShift 3 Tools Developer Resources 3.3.0.Final-v20160610-1836-B1369 > Eclipse: Neon Milestone 7 (4.6.0M7) > Reporter: Xia Zhao > Assignee: Andre Dietisheim > Labels: application_wizard, openshift_v3 > Fix For: 4.4.1.AM2 > > Attachments: application-template-stibuild.json, fails-even-though-required-value-provided.png, Screenshot from 2016-06-12 01-59-02.png > > > Create app from the local template in attachment,give required value to parameter "xiazhao_checkfail" inside new-app wizard, get error message after clicking on the "Next>" button: > Template "ruby-helloworld-sample" is invalid: template.parameters[5]: Required value: template.parameters[5]: parameter xiazhao_checkfail is required and must be specified > Could not create resource ruby-helloworld-sample in namespace 'xiazhao-1': {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"Template \"ruby-helloworld-sample\" is invalid: template.parameters[5]: Required value: template.parameters[5]: parameter xiazhao_checkfail is required and must be specified","reason":"Invalid","details":{"name":"ruby-helloworld-sample","kind":"Template","causes":[{"reason":"FieldValueRequired","message":"Required value: template.parameters[5]: parameter xiazhao_checkfail is required and must be specified","field":"template.parameters[5]"}]},"code":422} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22761) Connection to local EAP 7 via jmx fails

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22761?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-22761. --------------------------------- Fix Version/s: 4.4.1.AM2 Assignee: Martin Malina Resolution: Cannot Reproduce Bug Radim says his server was somehow broken. Once he deleted it unzipped from scratch, it worked fine. > Connection to local EAP 7 via jmx fails > --------------------------------------- > > Key: JBIDE-22761 > URL: https://issues.jboss.org/browse/JBIDE-22761 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx > Affects Versions: 4.4.1.AM2 > Reporter: Martin Malina > Assignee: Martin Malina > Fix For: 4.4.1.AM2 > > > This was spotted by Radim on linux today - he added EAP 7 via runtime detection, then started it and then tried to connect via jmx and it failed for him. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22690) Project is not refreshed if Ctrl+4 is fired inside an editor and "Link with Editor" is unchecked

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22690?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-22690. --------------------------------- Project is now refreshed after adding New Camel Component. (*validator* camel component has been used for verification) Verified in: Red Hat JBoss Developer Studio Version: 10.0.1.AM2 Build id: AM2-v20160719-2243-B5668 Build date: 20160719-2243 > Project is not refreshed if Ctrl+4 is fired inside an editor and "Link with Editor" is unchecked > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-22690 > URL: https://issues.jboss.org/browse/JBIDE-22690 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.4.0.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 4.4.1.AM2 > > > To reproduce that, follow the steps as described by [~aurelien.pupier] in https://github.com/fabric8io/fabric8-forge/issues/360 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22715) SWTException when setting Console color

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22715?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-22715. --------------------------------- Closing. Cannot reproduce bug. If this bug shows again, please reopen. Verified in: Red Hat JBoss Developer Studio Version: 10.0.1.AM2 Build id: AM2-v20160719-2243-B5668 Build date: 20160719-2243 > SWTException when setting Console color > --------------------------------------- > > Key: JBIDE-22715 > URL: https://issues.jboss.org/browse/JBIDE-22715 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.4.0.Final > Reporter: Automated Error Reporting Bot > Assignee: George Gastaldi > Fix For: 4.4.1.AM2 > > > The following problem was reported via the automated error reporting: > Message: Problems occurred when invoking code from plug-in: "org.eclipse.ui.console". > {noformat} > org.eclipse.swt.SWTException: Invalid thread access > at org.eclipse.swt.SWT.error(SWT.java:4533) > at org.eclipse.swt.SWT.error(SWT.java:4448) > at org.eclipse.swt.SWT.error(SWT.java:4419) > at org.eclipse.swt.widgets.Widget.error(Widget.java:482) > at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:420) > at org.eclipse.swt.widgets.Control.redraw(Control.java:3885) > at org.eclipse.swt.custom.StyledText.redraw(StyledText.java:7539) > at org.eclipse.ui.console.TextConsolePage.propertyChange(TextConsolePage.java:262) > at org.eclipse.ui.console.AbstractConsole$PropertyNotifier.run(AbstractConsole.java:96) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.ui.console.AbstractConsole$PropertyNotifier.notify(AbstractConsole.java:111) > at org.eclipse.ui.console.AbstractConsole.firePropertyChange(AbstractConsole.java:229) > at org.eclipse.ui.console.IOConsoleOutputStream.setColor(IOConsoleOutputStream.java:139) > at org.jboss.tools.forge.ui.internal.ext.provider.ForgeUIProvider.err(ForgeUIProvider.java:85) > at sun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethodAccessorImpl.java:-2) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback$2.call(ClassLoaderAdapterCallback.java:123) > at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42) > at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.invoke(ClassLoaderAdapterCallback.java:96) > at org.jboss.forge.addon.ui.UIProvider_$$_javassist_156eeef1-4a8c-4e5f-b623-1e3b4c1c88af.err(UIProvider_$$_javassist_156eeef1-4a8c-4e5f-b623-1e3b4c1c88af.java:-1) > at org.jboss.forge.addon.projects.ui.ProjectBuildStatusListener.postCommandExecuted(ProjectBuildStatusListener.java:49) > at sun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethodAccessorImpl.java:-2) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor$1.call(ClassLoaderInterceptor.java:87) > at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42) > at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor.invoke(ClassLoaderInterceptor.java:103) > at org.jboss.forge.addon.projects.ui.ProjectBuildStatusListener_$$_javassist_71401c63-ec8c-47b3-bacf-ca488c66c404.postCommandExecuted(ProjectBuildStatusListener_$$_javassist_71401c63-ec8c-47b3-bacf-ca488c66c404.java:-1) > at org.jboss.forge.addon.ui.impl.controller.AbstractCommandController.firePostCommandExecuted(AbstractCommandController.java:144) > at org.jboss.forge.addon.ui.impl.controller.SingleCommandControllerImpl.execute(SingleCommandControllerImpl.java:91) > at sun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethodAccessorImpl.java:-2) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback$2.call(ClassLoaderAdapterCallback.java:123) > at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42) > at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.invoke(ClassLoaderAdapterCallback.java:96) > at org.jboss.forge.addon.ui.controller.CommandController_$$_javassist_9f149b2a-2dec-45bb-b13c-ece553d8aaac.execute(CommandController_$$_javassist_9f149b2a-2dec-45bb-b13c-ece553d8aaac.java:-1) > at org.jboss.tools.forge.ui.internal.ext.wizards.ForgeWizard$1.run(ForgeWizard.java:113) > at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:118) > {noformat} > Bundles: > | org.eclipse.core.runtime | 3.11.1.v20150903-1804 | 3.12.0.v20160222-1238 | > | org.eclipse.jface | 3.11.1.v20160128-1644 | 3.12.0.v20160310-1055 | > | org.eclipse.swt | 3.104.2.v20160203-0937 | 3.105.0.v20160317-0027 | > | org.eclipse.ui.console | 3.6.100.v20150822-1912 | 3.6.100.v20160226-2242 | > | org.jboss.tools.forge.ui | 2.0.2.Final-v20160331-1851-B95 | 2.0.2.Final-v20160331-1851-B95 | > | org.jboss.tools.forge.ui.ext | 1.3.3.Final-v20150324-2247-B98 | 2.0.2.Final-v20160331-1851-B95 | > Operating Systems: > | Linux | 3.13.0 | 4.4.7.fc23 | > | MacOSX | 10.11.4 | 10.11.4 | > The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/57237d80e4b0a54983...] 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22766) Cannot load discovery directory

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22766?page=com.atlassian.jira.plugi... ] Jan Richter updated JBIDE-22766: -------------------------------- Project: Tools (JBoss Tools) (was: Red Hat JBoss Developer Studio (devstudio)) Key: JBIDE-22766 (was: JBDS-3971) Workflow: GIT Pull Request workflow (was: CDW v1) Status: Open (was: New) Docs QE Status: (was: NEW) Component/s: central updatesite (was: updatesite) (was: central) Affects Version/s: 4.4.1.AM2 (was: 10.1.0.AM2) > Cannot load discovery directory > ------------------------------- > > Key: JBIDE-22766 > URL: https://issues.jboss.org/browse/JBIDE-22766 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, updatesite > Affects Versions: 4.4.1.AM2 > Reporter: Jan Richter > Assignee: Nick Boldt > Priority: Blocker > > Central is trying to access the following directories on the update site: > - https://devstudio.redhat.com/10.0/snapshots/builds/jbosstools-discovery.e... for devstudio > - http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-dis... for JBT > These directories don't exist on the update sites, so central software/update cannot load. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3971) Cannot load discovery directory

by Jan Richter (JIRA)

Jan Richter created JBDS-3971: --------------------------------- Summary: Cannot load discovery directory Key: JBDS-3971 URL: https://issues.jboss.org/browse/JBDS-3971 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Bug Components: central, updatesite Affects Versions: 10.1.0.AM2 Reporter: Jan Richter Assignee: Nick Boldt Priority: Blocker Central is trying to access the following directories on the update site: - https://devstudio.redhat.com/10.0/snapshots/builds/jbosstools-discovery.e... for devstudio - http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-dis... for JBT These directories don't exist on the update sites, so central software/update cannot load. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22763) [regression] deploying an docker image doesn't select proper project

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22763?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22763: -------------------------------- Story Points: 1 Sprint: devex #117 July 2016 > [regression] deploying an docker image doesn't select proper project > -------------------------------------------------------------------- > > Key: JBIDE-22763 > URL: https://issues.jboss.org/browse/JBIDE-22763 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM1 > Reporter: Fred Bricon > Assignee: Andre Dietisheim > Fix For: 4.4.1.AM2 > > > There's a regression in the Deploy Docker image wizard, where, when you have multiple projects, the selected project in OS explorer is ignored in the wizard. > This works fine in devstudio 10. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-810) Update tests to RedDeer 1.0.2

by Andrej Podhradsky (JIRA)

Andrej Podhradsky created JBTIS-810: --------------------------------------- Summary: Update tests to RedDeer 1.0.2 Key: JBTIS-810 URL: https://issues.jboss.org/browse/JBTIS-810 Project: JBoss Tools Integration Stack Issue Type: Task Components: QE Affects Versions: 4.3.0.Final Reporter: Andrej Podhradsky Assignee: Andrej Podhradsky Fix For: 4.3.1.Final Update tests to use RedDeer 1.0.2 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3961) CDK installation failed with progress bar stuck in 99%

by Budh Ram Gurung (JIRA)

[ https://issues.jboss.org/browse/JBDS-3961?page=com.atlassian.jira.plugin.... ] Budh Ram Gurung commented on JBDS-3961: --------------------------------------- Hi Denis, I have updated jira with my observations. Please have a look. Regards, Budh Ram Gurung Software Engineer - Dev Tools On Wed, Jul 6, 2016 at 10:36 AM, Denis Golovin (JIRA) <issues(a)jboss.org> > CDK installation failed with progress bar stuck in 99% > ------------------------------------------------------ > > Key: JBDS-3961 > URL: https://issues.jboss.org/browse/JBDS-3961 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Environment: h3. Operating System: > Windows 10 Pro 64 Bit > h3. Devstudio version > Devstudio 1.0 GA > Reporter: Budh Ram Gurung > Assignee: Denis Golovin > Labels: cdk > Fix For: 10.1.0.AM2 > > Attachments: dev_studio_installation.PNG, install.log > > > I was trying the "devstudio 1.0 GA build" ("development-suite-1.0.0-GA-bundle-installer.exe") and unable to get CDK installation after gone through the steps of authentication, vagrant, cygwin, jboss dev studio installations. > Observations: > CDK installation stuck in 99% with "failed" mark. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 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 2016