June 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3449) Add Windows 10 to the support matrix for JBDS 9

by Martin Malina (JIRA)

Martin Malina created JBDS-3449: ----------------------------------- Summary: Add Windows 10 to the support matrix for JBDS 9 Key: JBDS-3449 URL: https://issues.jboss.org/browse/JBDS-3449 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Components: requirements Affects Versions: 9.0.0.Beta1 Reporter: Martin Malina JBDS 9 GA is currently scheduled for Tue 2015-10-06. Microsoft announced recently that Windows 10 will come out on July 29. We should try and support Windows 10 with JBDS 9. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19897) Remove check server type

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19897?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-19897: ------------------------------------------ thanks! rebased, merged and pushed to upstream/master > Remove check server type > ------------------------ > > Key: JBIDE-19897 > URL: https://issues.jboss.org/browse/JBIDE-19897 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Labels: connection_wizard > Fix For: 4.3.0.Beta1 > > Attachments: check-server-type-disabled.png > > > In JBIDE-19829 we disabled the "Check Server Type" button that was detecting the server type (v2 or v3) for a given server url. We should now remove the widget and the related code. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19890) compilation failure: The method release() is undefined for the type RevWalk

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19890?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19890: ------------------------------------- Fix Version/s: 4.3.0.Beta1 > compilation failure: The method release() is undefined for the type RevWalk > --------------------------------------------------------------------------- > > Key: JBIDE-19890 > URL: https://issues.jboss.org/browse/JBIDE-19890 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.3.0.Beta1 > > > Compiling openshift currently fails with the following maven error: > {code} > [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.22.0:compile (default-compile) on project org.jboss.tools.openshift.egit.test: Compilation failure: Compilation failure: > [ERROR] /mnt/hudson_workspace/workspace/jbosstools-openshift_master/sources/tests/org.jboss.tools.openshift.egit.test/src/org/jboss/tools/openshift/egit/internal/test/util/TestRepository.java:[451] > [ERROR] rw.release(); > [ERROR] ^^^^^^^ > [ERROR] The method release() is undefined for the type RevWalk > [ERROR] /mnt/hudson_workspace/workspace/jbosstools-openshift_master/sources/tests/org.jboss.tools.openshift.egit.test/src/org/jboss/tools/openshift/egit/internal/test/util/TestRepository.java:[454] > [ERROR] tw.release(); > [ERROR] ^^^^^^^ > [ERROR] The method release() is undefined for the type TreeWalk > [ERROR] 2 problems (2 errors) > [ERROR] -> [Help 1] > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.22.0:compile (default-compile) on project org.jboss.tools.openshift.egit.test: Compilation failure > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) > at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116) > at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80) > at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) > at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:355) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155) > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:216) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:160) > 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.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) > at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) > at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) > at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) > Caused by: copied.org.apache.maven.plugin.CompilationFailureException: Compilation failure > at copied.org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:418) > at org.eclipse.tycho.compiler.AbstractOsgiCompilerMojo.execute(AbstractOsgiCompilerMojo.java:254) > at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208) > ... 19 more > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19890) compilation failure: The method release() is undefined for the type RevWalk

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19890?page=com.atlassian.jira.plugi... ] Andre Dietisheim closed JBIDE-19890. ------------------------------------ Resolution: Done re-closing > compilation failure: The method release() is undefined for the type RevWalk > --------------------------------------------------------------------------- > > Key: JBIDE-19890 > URL: https://issues.jboss.org/browse/JBIDE-19890 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.3.0.Beta1 > > > Compiling openshift currently fails with the following maven error: > {code} > [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.22.0:compile (default-compile) on project org.jboss.tools.openshift.egit.test: Compilation failure: Compilation failure: > [ERROR] /mnt/hudson_workspace/workspace/jbosstools-openshift_master/sources/tests/org.jboss.tools.openshift.egit.test/src/org/jboss/tools/openshift/egit/internal/test/util/TestRepository.java:[451] > [ERROR] rw.release(); > [ERROR] ^^^^^^^ > [ERROR] The method release() is undefined for the type RevWalk > [ERROR] /mnt/hudson_workspace/workspace/jbosstools-openshift_master/sources/tests/org.jboss.tools.openshift.egit.test/src/org/jboss/tools/openshift/egit/internal/test/util/TestRepository.java:[454] > [ERROR] tw.release(); > [ERROR] ^^^^^^^ > [ERROR] The method release() is undefined for the type TreeWalk > [ERROR] 2 problems (2 errors) > [ERROR] -> [Help 1] > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.22.0:compile (default-compile) on project org.jboss.tools.openshift.egit.test: Compilation failure > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) > at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116) > at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80) > at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) > at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:355) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155) > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:216) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:160) > 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.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) > at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) > at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) > at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) > Caused by: copied.org.apache.maven.plugin.CompilationFailureException: Compilation failure > at copied.org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:418) > at org.eclipse.tycho.compiler.AbstractOsgiCompilerMojo.execute(AbstractOsgiCompilerMojo.java:254) > at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208) > ... 19 more > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19835) 'JPA Tools -> Generate Tables from Entities' does not work for Hibernate 4.0

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19835?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-19835: ------------------------------ Fix Version/s: 4.3.0.Beta2 > 'JPA Tools -> Generate Tables from Entities' does not work for Hibernate 4.0 > ---------------------------------------------------------------------------- > > Key: JBIDE-19835 > URL: https://issues.jboss.org/browse/JBIDE-19835 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.3.0.Beta2 > > > This issue is a result of further investigation of JBIDE-19431 and JBIDE-19535. This investigation showed me that the generation of DDL works fine (wether a defined console configuration is used or not) unless version 4.0 of Hibernate is used. > So for JPA 2.0 (which uses Hibernate 4.0 under the covers) the DDL generation does not work if the console configuration is used, nor when the use of a console configuration is disabled and Hibernate 4.0 is selected in the DDL generation dialog. It works however for Hibernate 3.5, 3.6 and 4.3. > For a JPA 1.0 project, DDL generation works with the console configuration and when console configuration is disabled and Hibernate 3.5, 3.6 or 4.3 are selected in the DDL generation dialog. > For JPA 2.1, only Hibernate 4.3 is a compatible Hibernate version and DDL generation works in this case both with and without using the console configuration. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19531) Forge console doesn't start without any error reported in eclipse UI when "VM Arguments" have errors

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19531?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-19531: ------------------------------ Fix Version/s: 4.3.x > Forge console doesn't start without any error reported in eclipse UI when "VM Arguments" have errors > ---------------------------------------------------------------------------------------------------- > > Key: JBIDE-19531 > URL: https://issues.jboss.org/browse/JBIDE-19531 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.2.3.CR1 > Reporter: Denis Golovin > Fix For: 4.3.x > > > See Steps to replicate. It doesn't report any errors about forge start. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19531) Forge console doesn't start without any error reported in eclipse UI when "VM Arguments" have errors

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19531?page=com.atlassian.jira.plugi... ] Koen Aers reassigned JBIDE-19531: --------------------------------- Assignee: Koen Aers > Forge console doesn't start without any error reported in eclipse UI when "VM Arguments" have errors > ---------------------------------------------------------------------------------------------------- > > Key: JBIDE-19531 > URL: https://issues.jboss.org/browse/JBIDE-19531 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.2.3.CR1 > Reporter: Denis Golovin > Assignee: Koen Aers > Fix For: 4.3.x > > > See Steps to replicate. It doesn't report any errors about forge start. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19792) antlr packages and lib not exported in Hibernate Tools 4.0.1

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19792?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-19792: ------------------------------ Fix Version/s: 4.3.x > antlr packages and lib not exported in Hibernate Tools 4.0.1 > ------------------------------------------------------------ > > Key: JBIDE-19792 > URL: https://issues.jboss.org/browse/JBIDE-19792 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.2.3.Final > Environment: Eclipse Luna SR2 > Reporter: Bastian Ulke > Assignee: Koen Aers > Fix For: 4.3.x > > Attachments: B82_MANIFEST.MF, B95_MANIFEST.MF > > > I am currently working on an Eclipse-Plugin that is built on top of the > Hibernate Tools project. For example, I am using the following statements > to get the AST of a named query: > {code} > try { > HqlParser parser = HqlParser.getInstance(statementString); > parser.statement(); > } catch (RecognitionException | TokenStreamException e) { > e.printStackTrace(); > } > AST statementAst = parser.getAST(); > {code} > For this to work well with Hibernate Tools Version 4.0.0, I added bundle > org.hibernate.eclipse.libs as required bundle to my plug-in configuration > (which resolved to > org.hibernate.eclipse.libs_4.0.0.Final-v20141016-1911-B82 so far). > However, I now updated to Hiberate Tools 4.0.1 > (org.hibernate.eclipse.libs_4.0.1.Final-v20150324-2307-B95). The problem I > have now is that the following imports cannot be resolved: > import antlr.RecognitionException; > import antlr.TokenStreamException; > import antlr.collections.AST; > The problem seems to arise from the fact, that in the new version's > MANIFEST.MF, the antlr... packages are not exported and > lib/hibernate/antlr-2.7.6.jar is not listed in the Bundle-ClassPath any > more (I reformatted both MANIFEST.MFs, that you can find attached, to allow > a convenient comparison). After manually adding the antlr-related entries > to the new version's MANIFEST.MF, my code works pretty well again. > I agree, that internal libraries should generally not be exported. However, > org.hibernate.hql.ast.HqlParser is exported -- so why not its prerequesites? > (By the way, I'd be fine with integrating another library into my project. > However, I tried to manally add antlr-2.7.6.jar as library to > my project, which solved the compilation error, but yields a > java.lang.ClassNotFoundException: antlr.LLkParser cannot be found by > org.hibernate.eclipse.libs_4.0.1.Final-v20150324-2307-B95.) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19721) look at fixing quickaccess resizing bug

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19721?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-19721: ------------------------------ Fix Version/s: 4.3.x > look at fixing quickaccess resizing bug > --------------------------------------- > > Key: JBIDE-19721 > URL: https://issues.jboss.org/browse/JBIDE-19721 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Reporter: Max Rydahl Andersen > Assignee: Koen Aers > Fix For: 4.3.x > > > See https://bugs.eclipse.org/bugs/show_bug.cgi?id=432688 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19830) Nullpointer at recieving schema

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19830?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-19830: ------------------------------ Fix Version/s: 4.3.0.Beta1 > Nullpointer at recieving schema > ------------------------------- > > Key: JBIDE-19830 > URL: https://issues.jboss.org/browse/JBIDE-19830 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.3.0.Alpha2 > Environment: Hibernate: 5.0.0.Alpha2-v20150417-1452-B12 > Eclipse: Eclipse Mars M7 > OS: Windows 7 x64 Enterprise > DB: Postgres 9.3 > Reporter: Philipp Birkl > Assignee: Koen Aers > Fix For: 4.3.0.Beta1 > > > While receiving a schema from Database initially a _java.lang.NullPointerException* is thrown_. > !http://i.imgur.com/2Frtlwu.png! > Stack trace can be found [here|https://gist.github.com/calaedo/394f3fdb8994741de3ce#file-jbide-1983...]. > While debugging the plugin i found the problem at the implementation of the anonymous comperator in _org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter.getChildren(Object, IProgressMonitor)_. > {code} > res = toArray(result.iterator(), Object.class, new Comparator<Object>() { > public int compare(Object arg0, Object arg1) { > return getName(arg0).compareTo(getName(arg1)); > } > private String getName(Object o) { > String result = null; > try { > Method m = o.getClass().getMethod("getName", new Class[] {}); > m.invoke(o, new Object[] {}); > } catch (Exception e) { > throw new RuntimeException(e); > } > return result; > } > }); > {code} > The string result is never set. So the _compareTo_ is always failing. > I haven't looked it up, but the problem might consist also in earlier versions of JBoss tools. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 2 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 2015