March 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3360) Align bits offered in JBoss Central with installed version of JBDS

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3360?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3360: ---------------------------------- So, does that mean that you want https://devstudio.jboss.com/updates/8.0/ to includes multiple versions of JBDS (8.0, 8.0.1, 8.0.2, 8.1), but only one version of Central (the latest one for 8.1) ? > Align bits offered in JBoss Central with installed version of JBDS > ------------------------------------------------------------------ > > Key: JBDS-3360 > URL: https://issues.jboss.org/browse/JBDS-3360 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: central, updatesite > Affects Versions: 8.0.2.GA > Reporter: Martin Malina > Fix For: 8.1.0.CR1 > > > The problem in JBDS-3359 shows a broader issue. > (That one is about issues when clicking on an example in Central in JBDS 8.0.0 when 8.0.2 has already been released and central points to it.) > Currently when you install JBDS 8.0.0, it will contain this update site in Preferences -> Available Software Sites: > https://devstudio.redhat.com/updates/8.0/ > Initially this update site contained JBDS 8.0.0 core + 8.0.0 central. > But once we released JBDS 8.0.1, the update site was updated with 8.0.1 and this update was offered to users in Eclipse. And we started to have two groups of users: > 1. Those who stayed on JBDS 8.0.0, but their Central already pointed to 8.0.1 bits > 2. Those who update to JBDS 8.0.1 (and their Central also pointed to 8.0.1 bits) > Wouldn't it make more sense if central used the same version that is currently installed? I.e. if a user stays with JBDS 8.0.0, the bits offered in Central are 8.0.0 also. > I'm not sure if this is doable or makes sense at all, so I'm looking forward to feedback :) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19189) NullPointerException in TablePropertiesBlock.doAdd

by Jiri Peterka (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19189?page=com.atlassian.jira.plugi... ] Jiri Peterka closed JBIDE-19189. -------------------------------- Verified with JBDS 8.1.0.Beta1-B438, L64 > NullPointerException in TablePropertiesBlock.doAdd > -------------------------------------------------- > > Key: JBIDE-19189 > URL: https://issues.jboss.org/browse/JBIDE-19189 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.2.2.Final > Environment: eclipse.buildId=4.4.1.M20140925-0400 > java.version=1.8.0_31 > java.vendor=Oracle Corporation > BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=de_DE > Command-line arguments: -os win32 -ws win32 -arch x86_64 > Reporter: Michael Kolowicz > Assignee: Koen Aers > Priority: Critical > Fix For: 4.2.3.Beta1, 4.3.0.Alpha2 > > > I want to develop a small prototype of a application. I have create a database on MySQL 5.6 on a remote server. They have only 1 table (It´s like a easy prototype). The table have a Id-column. > I using the eclipse 4.4.1 (on Windows 7 x64 - german), Hibernate 4.3.8, Hibernate Tools 4.0.0 (Final). > Installation is a fresh downloaded eclipse with all actual updates. In the application is added the JDBC for MySQL and the Hibernate-Core Files. > BTW: If i use Eclipse 4.3 with the same database, then the columns can be added an no error come up. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19157) Wrong configuration of entry for XML catalog in org.hibernate.eclipse.mapper_4.0.0.Final-v20141016-1911-B82

by Jiri Peterka (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19157?page=com.atlassian.jira.plugi... ] Jiri Peterka closed JBIDE-19157. -------------------------------- Editing, validation, code completion in reveng file works. Verified with JBDS 8.1.0.Beta1-B438. > Wrong configuration of entry for XML catalog in org.hibernate.eclipse.mapper_4.0.0.Final-v20141016-1911-B82 > ----------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19157 > URL: https://issues.jboss.org/browse/JBIDE-19157 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Environment: org.hibernate.eclipse.mapper_4.0.0.Final-v20141016-1911-B82 > Reporter: Vitali Dyachkov > Assignee: Koen Aers > Priority: Critical > Fix For: 4.2.3.Beta1, 4.3.0.Alpha2 > > > plugin.xml does not refer correct > hibernate-tools-3.4.0.CR2.jar > which makes impossible loading of DTD by Eclipse from XML catalog and editing of <hibernate-reverse-engineering> type of XML files in source mode with drop down elements. > Fix: > {code:xml} > <public publicId="-//Hibernate/Hibernate Reverse Engineering DTD 3.0//EN" > uri="jar:platform:/plugin/org.hibernate.eclipse.libs/lib/tools/hibernate-tools-3.4.0.CR2.jar!/org/hibernate/hibernate-reverse-engineering-3.0.dtd" > webURL="http://hibernate.sourceforge.net/hibernate-reverse-engineering-3.0.dtd" > /> > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19361) Fix Failing Test Suite For 4.2.3.Beta1

by Jiri Peterka (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19361?page=com.atlassian.jira.plugi... ] Jiri Peterka closed JBIDE-19361. -------------------------------- > Fix Failing Test Suite For 4.2.3.Beta1 > -------------------------------------- > > Key: JBIDE-19361 > URL: https://issues.jboss.org/browse/JBIDE-19361 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Reporter: Koen Aers > Assignee: Koen Aers > Priority: Blocker > Fix For: 4.2.3.Beta1 > > > After incrementing the version numbers the tests suite started failing. This appears to be due to Apache Commons Logging being present multiple times on the classpath. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-18769) ResourceException when generating hbm.xml

by Jiri Peterka (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18769?page=com.atlassian.jira.plugi... ] Jiri Peterka closed JBIDE-18769. -------------------------------- Verified with JBDS 8.1.0.Beta1-B438, L64 > ResourceException when generating hbm.xml > ----------------------------------------- > > Key: JBIDE-18769 > URL: https://issues.jboss.org/browse/JBIDE-18769 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.2.0.Final > Reporter: Rastislav Wagner > Assignee: Koen Aers > Priority: Blocker > Fix For: 4.2.3.Beta1 > > > {code} > org.eclipse.core.internal.resources.ResourceException: Resource '/jboss-javaee6-webapp/org/jboss/tools/examples/model' does not exist. > at org.eclipse.core.internal.resources.Resource.checkExists(Resource.java:341) > at org.eclipse.core.internal.resources.Resource.checkAccessible(Resource.java:215) > at org.eclipse.core.internal.resources.File.create(File.java:115) > at org.eclipse.core.internal.resources.File.create(File.java:188) > at org.eclipse.jdt.internal.corext.refactoring.nls.changes.CreateFileChange.perform(CreateFileChange.java:165) > at org.eclipse.ltk.core.refactoring.CompositeChange.perform(CompositeChange.java:278) > at org.hibernate.eclipse.jdt.ui.wizards.NewHibernateMappingPreviewPage.performFinish(NewHibernateMappingPreviewPage.java:299) > at org.hibernate.eclipse.jdt.ui.wizards.NewHibernateMappingFileWizard.performFinish(NewHibernateMappingFileWizard.java:408) > at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:853) > at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:438) > at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:619) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4454) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3799) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3409) > at org.eclipse.jface.window.Window.runEventLoop(Window.java:832) > at org.eclipse.jface.window.Window.open(Window.java:808) > at org.eclipse.ui.internal.handlers.WizardHandler$New.executeHandler(WizardHandler.java:269) > at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:290) > at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:294) > at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:55) > at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:247) > at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:229) > at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132) > at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:149) > at org.eclipse.core.commands.Command.executeWithChecks(Command.java:499) > at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508) > at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210) > at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:343) > at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:159) > at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:595) > at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511) > at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:420) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4454) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3799) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3409) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603) > at org.eclipse.equinox.launcher.Main.run(Main.java:1465) > at org.eclipse.equinox.launcher.Main.main(Main.java:1438) > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3360) Align bits offered in JBoss Central with installed version of JBDS

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3360?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3360: ------------------------------------------- I think it makes sense for the released updatesite to composite the versions to allow for rolling back and for installing specific versions. But that will be a manual procedure and I still think Central is better of encouraging updates rather than letting everything be a'la'carte. > Align bits offered in JBoss Central with installed version of JBDS > ------------------------------------------------------------------ > > Key: JBDS-3360 > URL: https://issues.jboss.org/browse/JBDS-3360 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: central, updatesite > Affects Versions: 8.0.2.GA > Reporter: Martin Malina > Fix For: 8.1.0.CR1 > > > The problem in JBDS-3359 shows a broader issue. > (That one is about issues when clicking on an example in Central in JBDS 8.0.0 when 8.0.2 has already been released and central points to it.) > Currently when you install JBDS 8.0.0, it will contain this update site in Preferences -> Available Software Sites: > https://devstudio.redhat.com/updates/8.0/ > Initially this update site contained JBDS 8.0.0 core + 8.0.0 central. > But once we released JBDS 8.0.1, the update site was updated with 8.0.1 and this update was offered to users in Eclipse. And we started to have two groups of users: > 1. Those who stayed on JBDS 8.0.0, but their Central already pointed to 8.0.1 bits > 2. Those who update to JBDS 8.0.1 (and their Central also pointed to 8.0.1 bits) > Wouldn't it make more sense if central used the same version that is currently installed? I.e. if a user stays with JBDS 8.0.0, the bits offered in Central are 8.0.0 also. > I'm not sure if this is doable or makes sense at all, so I'm looking forward to feedback :) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19384) Package visibility in the different plugins needs cleanup and re-exports

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19384?page=com.atlassian.jira.plugi... ] Andre Dietisheim closed JBIDE-19384. ------------------------------------ > Package visibility in the different plugins needs cleanup and re-exports > ------------------------------------------------------------------------ > > Key: JBIDE-19384 > URL: https://issues.jboss.org/browse/JBIDE-19384 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.3.0.Alpha2 > > > The package visibilities in all the plugins we have need cleanup. We especially need to reeport common.core since express.core/openshift.core extends those classes which then need to be visible in express.test/openshift.test -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19384) Package visibility in the different plugins needs cleanup and re-exports

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19384?page=com.atlassian.jira.plugi... ] Andre Dietisheim resolved JBIDE-19384. -------------------------------------- Resolution: Done re-closing > Package visibility in the different plugins needs cleanup and re-exports > ------------------------------------------------------------------------ > > Key: JBIDE-19384 > URL: https://issues.jboss.org/browse/JBIDE-19384 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.3.0.Alpha2 > > > The package visibilities in all the plugins we have need cleanup. We especially need to reeport common.core since express.core/openshift.core extends those classes which then need to be visible in express.test/openshift.test -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19384) Package visibility in the different plugins needs cleanup and re-exports

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19384?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19384: ------------------------------------- Fix Version/s: 4.3.0.Alpha2 > Package visibility in the different plugins needs cleanup and re-exports > ------------------------------------------------------------------------ > > Key: JBIDE-19384 > URL: https://issues.jboss.org/browse/JBIDE-19384 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.3.0.Alpha2 > > > The package visibilities in all the plugins we have need cleanup. We especially need to reeport common.core since express.core/openshift.core extends those classes which then need to be visible in express.test/openshift.test -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-560) We should add an illustration of the RESTFUL output

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-560?page=com.atlassian.jira.plug... ] Michelle Murray commented on TOOLSDOC-560: ------------------------------------------ [~mhusnain] - when you work through the Start Developing guide please can you see if you have problems with this aspect of the tutorial as Marian reports. I tried it for 8.0.0GA and it worked so I am surprised to hear that it does not work now. > We should add an illustration of the RESTFUL output > --------------------------------------------------- > > Key: TOOLSDOC-560 > URL: https://issues.jboss.org/browse/TOOLSDOC-560 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Enhancement > Affects Versions: 4.2.0.Final > Environment: Build Name: 22960, Start Developing-8.0 > Build Date: 22-10-2014 11:29:36 > Topic ID: 13785-717269 [Latest] > Reporter: Len DiMaggio > Assignee: Misha Ali > Priority: Minor > Fix For: 4.2.3.Beta1 > > > Title: Add a RESTful Web Service > Describe the issue: > The final step in this section reads: > Open a new Web Browser and in the address bar of the Web Browser enter http://localhost:8080/ticket-monster/rest/events. This shows the output of the new RESTful endpoint. > Suggestions for improvement: > We should add test explaining to the reader that the output should look like this: > [{"id":2,"version":1,"name":"Rock concert of the decade","description":"Get ready to rock...","major":true,"picture":null},{"id":1,"version":1,"name":"Shane's Sock Puppets","description":"This critically acclaimed masterpiece...","major":true,"picture":null}] > Additional information: -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

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 March 2015