June 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21657) set up jobs to handle building from PRs

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21657?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-21657: ---------------------------------------- I already tried everything I needed to try, we're not in testing phase any more. > set up jobs to handle building from PRs > --------------------------------------- > > Key: JBIDE-21657 > URL: https://issues.jboss.org/browse/JBIDE-21657 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.1.Beta2, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.4.0.Final > > > First experimental build: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sit... > Output: > http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-bui... > {code} > "revision" : { > "HEAD" : "bfe76fb3f3c34d68b873d0acf715e2145e4cb805", > "currentBranch" : "HEAD", > "knownReferences" : [{ > "name" : "origin", > "url" : "git://github.com/jbosstools/jbosstools-build-sites.git", > "ref" : "pr/221/merge" > }] > }, > {code} > http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-bui... > {code} > #Fri Feb 05 16:42:42 EST 2016 > null\:merge=bfe76fb3f3c34d68b873d0acf715e2145e4cb805 > HEAD=bfe76fb3f3c34d68b873d0acf715e2145e4cb805 > {code} > build log: > {code} > Started by upstream project "jbosstools-build-sites.aggregate.child-sites__pull-request_master" build number 1 > originally caused by: > GitHub pull request #221 of commit 50c10ad83d250d2b86f5697c4581ba8f9cb4937d, no merge conflicts. > ... > Fetching upstream changes from git://github.com/jbosstools/jbosstools-build-sites.git > > git -c core.askpass=true fetch --tags --progress git://github.com/jbosstools/jbosstools-build-sites.git +refs/heads/*:refs/remotes/origin/* +refs/pull/*:refs/remotes/origin/pr/* > Checking out Revision bfe76fb3f3c34d68b873d0acf715e2145e4cb805 (refs/remotes/origin/pr/221/merge) > > git config core.sparsecheckout # timeout=10 > > git checkout -f bfe76fb3f3c34d68b873d0acf715e2145e4cb805 > {code} > vars: > {code} > -DghprbActualCommit=50c10ad83d250d2b86f5697c4581ba8f9cb4937d > -DghprbPullId=221 > -Dsha1=origin/pr/221/merge > "-DghprbPullDescription=GitHub pull request #221 of commit 50c10ad83d250d2b86f5697c4581ba8f9cb4937d, no merge conflicts." > -DghprbActualCommit=50c10ad83d250d2b86f5697c4581ba8f9cb4937d > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ERT-238) Issue in DockerConnection#hasImage(String, String) [EBZ#495243]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-238: --------------------------------------- Summary: Issue in DockerConnection#hasImage(String,String) [EBZ#495243] Key: ERT-238 URL: https://issues.jboss.org/browse/ERT-238 Project: Eclipse Release Train Issue Type: Task Components: Linux Tools Reporter: Friendly Jira Robot The method only inspects the first 'repo' value for a given image, so if a given Docker image was tagged with different names (eg: 'jboss/wildfly' and 'xcoulon/wildfly'), then one method call will respond 'false' while it should be 'true'. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21657) set up jobs to handle building from PRs

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21657?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-21657: --------------------------------------------- also, I still think you can simply try this with your *own* user. Then no need to wait for who ever owns rhdevelopers-ci to to respond to your request. > set up jobs to handle building from PRs > --------------------------------------- > > Key: JBIDE-21657 > URL: https://issues.jboss.org/browse/JBIDE-21657 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.1.Beta2, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.4.0.Final > > > First experimental build: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sit... > Output: > http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-bui... > {code} > "revision" : { > "HEAD" : "bfe76fb3f3c34d68b873d0acf715e2145e4cb805", > "currentBranch" : "HEAD", > "knownReferences" : [{ > "name" : "origin", > "url" : "git://github.com/jbosstools/jbosstools-build-sites.git", > "ref" : "pr/221/merge" > }] > }, > {code} > http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-bui... > {code} > #Fri Feb 05 16:42:42 EST 2016 > null\:merge=bfe76fb3f3c34d68b873d0acf715e2145e4cb805 > HEAD=bfe76fb3f3c34d68b873d0acf715e2145e4cb805 > {code} > build log: > {code} > Started by upstream project "jbosstools-build-sites.aggregate.child-sites__pull-request_master" build number 1 > originally caused by: > GitHub pull request #221 of commit 50c10ad83d250d2b86f5697c4581ba8f9cb4937d, no merge conflicts. > ... > Fetching upstream changes from git://github.com/jbosstools/jbosstools-build-sites.git > > git -c core.askpass=true fetch --tags --progress git://github.com/jbosstools/jbosstools-build-sites.git +refs/heads/*:refs/remotes/origin/* +refs/pull/*:refs/remotes/origin/pr/* > Checking out Revision bfe76fb3f3c34d68b873d0acf715e2145e4cb805 (refs/remotes/origin/pr/221/merge) > > git config core.sparsecheckout # timeout=10 > > git checkout -f bfe76fb3f3c34d68b873d0acf715e2145e4cb805 > {code} > vars: > {code} > -DghprbActualCommit=50c10ad83d250d2b86f5697c4581ba8f9cb4937d > -DghprbPullId=221 > -Dsha1=origin/pr/221/merge > "-DghprbPullDescription=GitHub pull request #221 of commit 50c10ad83d250d2b86f5697c4581ba8f9cb4937d, no merge conflicts." > -DghprbActualCommit=50c10ad83d250d2b86f5697c4581ba8f9cb4937d > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22301) NPE in new OS application from eclipse project with no remote git reference.

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22301?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-22301: ----------------------------------------------- [~adietish], please take a look at the pull request https://github.com/jbosstools/jbosstools-openshift/pull/1205 > NPE in new OS application from eclipse project with no remote git reference. > ---------------------------------------------------------------------------- > > Key: JBIDE-22301 > URL: https://issues.jboss.org/browse/JBIDE-22301 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Environment: JBDS 10.0.0.Alpha1 > Reporter: Radim Hopp > Assignee: Viacheslav Kabanovich > Fix For: 4.4.0.Alpha2 > > > Trying to finish new openshift application wizard using existing aplication from workspace without remote git repository fails with NPE: > {noformat:title=Unhandled event loop exception} > java.lang.NullPointerException > at org.jboss.tools.openshift.internal.ui.wizard.newapp.NewApplicationWizard.performFinish(NewApplicationWizard.java:194) > at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:790) > at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:423) > at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:618) > 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:4494) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1339) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3832) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3443) > at org.eclipse.jface.window.Window.runEventLoop(Window.java:818) > at org.eclipse.jface.window.Window.open(Window.java:794) > at org.jboss.tools.common.ui.WizardUtils.openWizardDialog(WizardUtils.java:287) > at org.jboss.tools.common.ui.WizardUtils.openWizardDialog(WizardUtils.java:270) > at org.jboss.tools.openshift.internal.ui.handler.NewApplicationHandler.execute(NewApplicationHandler.java:34) > at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:295) > 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:497) > at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:54) > at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:282) > at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:264) > at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132) > at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:152) > at org.eclipse.core.commands.Command.executeWithChecks(Command.java:494) > at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:491) > at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210) > at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:425) > at org.eclipse.e4.ui.workbench.renderers.swt.AbstractContributionItem.handleWidgetSelection(AbstractContributionItem.java:449) > at org.eclipse.e4.ui.workbench.renderers.swt.AbstractContributionItem$3.handleEvent(AbstractContributionItem.java:477) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4494) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1339) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3832) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3443) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1118) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1019) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:157) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:691) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:604) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138) > 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:388) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243) > 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:497) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:670) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:609) > at org.eclipse.equinox.launcher.Main.run(Main.java:1516) > at org.eclipse.equinox.launcher.Main.main(Main.java:1489) > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-728) Fix 'DataTransformationDeploymentEAPTest'

by Tomáš Sedmík (JIRA)

Tomáš Sedmík created JBTIS-728: ---------------------------------- Summary: Fix 'DataTransformationDeploymentEAPTest' Key: JBTIS-728 URL: https://issues.jboss.org/browse/JBTIS-728 Project: JBoss Tools Integration Stack Issue Type: Bug Components: QE Affects Versions: 4.3.0.Final Reporter: Tomáš Sedmík Assignee: Tomáš Sedmík {code} org.jboss.reddeer.common.exception.WaitTimeoutExpiredException: Timeout after: 10 s.: at least one project is loaded at org.jboss.reddeer.common.wait.AbstractWait.timeoutExceeded(AbstractWait.java:173) at org.jboss.reddeer.common.wait.AbstractWait.wait(AbstractWait.java:126) at org.jboss.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:91) at org.jboss.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:61) at org.jboss.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:46) at org.jboss.reddeer.common.wait.WaitUntil.<init>(WaitUntil.java:37) at org.jboss.reddeer.eclipse.ui.wizards.datatransfer.WizardProjectsImportPage.setPath(WizardProjectsImportPage.java:154) at org.jboss.reddeer.eclipse.ui.wizards.datatransfer.WizardProjectsImportPage.setRootDirectory(WizardProjectsImportPage.java:62) at org.jboss.tools.fuse.ui.bot.test.utils.ProjectFactory.importExistingProject(ProjectFactory.java:155) at org.jboss.tools.fuse.ui.bot.test.DataTransformationDeploymentEAPTest.testDeployment(DataTransformationDeploymentEAPTest.java:72) {code} on Mac only: {code} org.jboss.reddeer.common.exception.WaitTimeoutExpiredException: Timeout after: 300 s.: server's state is: Started at org.jboss.reddeer.common.wait.AbstractWait.timeoutExceeded(AbstractWait.java:173) at org.jboss.reddeer.common.wait.AbstractWait.wait(AbstractWait.java:126) at org.jboss.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:91) at org.jboss.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:61) at org.jboss.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:46) at org.jboss.reddeer.common.wait.WaitUntil.<init>(WaitUntil.java:37) at org.jboss.reddeer.eclipse.wst.server.ui.view.Server.operateServerState(Server.java:304) at org.jboss.reddeer.eclipse.wst.server.ui.view.Server.start(Server.java:159) at org.jboss.tools.runtime.reddeer.ServerBase.setState(ServerBase.java:97) at org.jboss.tools.runtime.reddeer.requirement.ServerRequirement.fulfill(ServerRequirement.java:98) at org.jboss.reddeer.junit.internal.requirement.Requirements.fulfill(Requirements.java:95) at org.jboss.reddeer.junit.internal.runner.statement.FulfillRequirementsStatement.evaluate(FulfillRequirementsStatement.java:34) at org.jboss.reddeer.junit.internal.runner.statement.RunIBeforeClassExtensions.evaluate(RunIBeforeClassExtensions.java:60) at org.jboss.reddeer.junit.internal.runner.statement.RunAfters.evaluate(RunAfters.java:58) at org.jboss.reddeer.junit.internal.runner.statement.CleanUpRequirementStatement.evaluate(CleanUpRequirementStatement.java:34) at org.jboss.reddeer.junit.internal.runner.statement.RunIAfterClassExtensions.evaluate(RunIAfterClassExtensions.java:48) at org.junit.runners.ParentRunner.run(ParentRunner.java:363) at org.jboss.reddeer.junit.internal.runner.RequirementsRunner.run(RequirementsRunner.java:146) at org.junit.runners.Suite.runChild(Suite.java:128) at org.junit.runners.Suite.runChild(Suite.java:27) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) at org.junit.runners.ParentRunner.run(ParentRunner.java:363) at org.junit.runners.Suite.runChild(Suite.java:128) at org.junit.runners.Suite.runChild(Suite.java:27) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) at org.junit.runners.ParentRunner.run(ParentRunner.java:363) at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264) at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153) at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124) 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:497) at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray2(ReflectionUtils.java:208) at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:156) at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:82) at org.eclipse.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:91) at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication.runTests(AbstractUITestApplication.java:44) at org.eclipse.e4.ui.internal.workbench.swt.E4Testable$1.run(E4Testable.java:73) at java.lang.Thread.run(Thread.java:745) {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-727) Extend Server requirement for Runtime Execution

by Tomáš Sedmík (JIRA)

Tomáš Sedmík created JBTIS-727: ---------------------------------- Summary: Extend Server requirement for Runtime Execution Key: JBTIS-727 URL: https://issues.jboss.org/browse/JBTIS-727 Project: JBoss Tools Integration Stack Issue Type: Task Components: QE Affects Versions: 4.3.0.Final Reporter: Tomáš Sedmík Assignee: Tomáš Sedmík for more info see https://github.com/jbosstools/jbosstools-integration-stack-tests/pull/734... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22487) For JBIDE 4.4.0.Final: Prepare for Final/GA [Playground]

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22487?page=com.atlassian.jira.plugi... ] Mickael Istria closed JBIDE-22487. ---------------------------------- Resolution: Rejected Playground component doesn't contribute anymore to JBoss Tools or JBDS. See JBIDE-21134 > For JBIDE 4.4.0.Final: Prepare for Final/GA [Playground] > -------------------------------------------------------- > > Key: JBIDE-22487 > URL: https://issues.jboss.org/browse/JBIDE-22487 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: playground > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Blocker > Labels: task > Fix For: 4.4.0.Final > > > For JBIDE 4.4.0.Final [Playground]: Please perform the following tasks: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.0.Final or 10.0.0.GA > [Unresolved JIRAs with fixVersion = 4.4.0.Final, 10.0.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...] > 1. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.0.Final-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.0.Final-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:orange}4.4.0.Final-SNAPSHOT{color}* in your *{color:orange}jbosstools-4.4.x{color}* branch > 2. Branch from your existing master branch into a new *{color:blue}jbosstools-4.4.x{color}* branch; > {code} > git checkout master > git pull origin master > git checkout -b jbosstools-4.4.x > git push origin jbosstools-4.4.x > {code} > Now, your root pom will use parent pom version: > * *{color:orange}4.4.0.Final-SNAPSHOT{color}* in your *{color:blue}master{color}* branch (we'll move to 4.5.0.Alpha1 later!) > * *{color:blue}4.4.0.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.x{color}* branch > 3. Ensure you've *built your code* using the latest target platform version 4.60.0.Final-SNAPSHOT (4.60 = Eclipse Neon.0) > {code} > mvn clean verify -Dtpc.version=4.60.0.Final-SNAPSHOT > {code} > 4. Close (do not resolve) this JIRA when done. > 5. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Playground task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22071) JDBCMetaDataConfiguration should allow fetching of table names only

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22071?page=com.atlassian.jira.plugi... ] Koen Aers resolved JBIDE-22071. ------------------------------- Resolution: Rejected > JDBCMetaDataConfiguration should allow fetching of table names only > ------------------------------------------------------------------- > > Key: JBIDE-22071 > URL: https://issues.jboss.org/browse/JBIDE-22071 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: hibernate > Environment: Hibernate Tools 4.3.1.Final ({{org.hibernate:hibernate-tools:4.3.1.Final}}) > Reporter: George Gastaldi > Assignee: Koen Aers > Fix For: 4.4.0.Final > > > I have a MySQL DB containing 40 tables. When I call {{org.hibernate.cfg.JDBCMetaDataConfiguration.readFromJDBC()}} it takes a considerably amount of time (minutes) when all I need are the table names. It seems that this method reads the entire mapping structure for all tables. > This is where I am using it: https://github.com/forge/core/blob/master/database-tools/impl/src/main/ja.... > The {{HibernateToolsHelper}} class calls {{JDBCMetaDataConfiguration.readFromJDBC()}} here: https://github.com/forge/core/blob/master/database-tools/impl/src/main/ja... > Can we improve this class to return only the table names and avoid this extra amount of work? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22168) Solve the test problems on Windows

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22168?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-22168: ------------------------------ Fix Version/s: 4.4.x (was: 4.4.0.Final) > Solve the test problems on Windows > ---------------------------------- > > Key: JBIDE-22168 > URL: https://issues.jboss.org/browse/JBIDE-22168 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.4.x > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22498) Memory leak in ServerLogView

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22498?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-22498: ----------------------------------------------- [~rob.stryker], please take a look at the pull request. > Memory leak in ServerLogView > ---------------------------- > > Key: JBIDE-22498 > URL: https://issues.jboss.org/browse/JBIDE-22498 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.4.0.Alpha2 > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Fix For: 4.4.0.Alpha2 > > > When ServerLogView is closed, it remains a listener of the last selected IServer and is not finalized. The listener should be removed in dispose(). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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