September 2014 - jbosstools-issues

[JBoss JIRA] (JBIDE-17854) ArrayStoreException while opening database in Hibernate Console

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17854?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-17854: --------------------------------------------- Just for reference - You are not at the same place from perspective of the bug - this bug and related fix is about exception being thrown. That was fixed - it is 99% certain than a seperate jira is needed when you are now talking about having to edit persistence.xml and linking cfg.xml - not related to the initial problem first. And it is much simpler and safer to reject or reopen an issue as duplicate than to see a major issue overlooked because an issue that reads as a completely different issue is hiding the actual issue. > ArrayStoreException while opening database in Hibernate Console > --------------------------------------------------------------- > > Key: JBIDE-17854 > URL: https://issues.jboss.org/browse/JBIDE-17854 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.2.0.Beta3 > Environment: JBDS 8.0.0.CR1 > Reporter: Jiri Peterka > Assignee: Koen Aers > Priority: Critical > Fix For: 4.2.0.CR1 > > > An internal error has occurred. > java.lang.ArrayStoreException > Used pom file > {code} > <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"> > <modelVersion>4.0.0</modelVersion> > <groupId>testjpa</groupId> > <artifactId>testjpa</artifactId> > <version>0.0.1-SNAPSHOT</version> > <dependencies> > <dependency> > <groupId>org.hibernate</groupId> > <artifactId>hibernate-core</artifactId> > <version>4.0.0.Final</version> > </dependency> > <dependency> > <groupId>org.hibernate</groupId> > <artifactId>hibernate-entitymanager</artifactId> > <version>4.0.0.Final</version> > </dependency> > <dependency> > <groupId>org.hibernate.javax.persistence</groupId> > <artifactId>hibernate-jpa-2.0-api</artifactId> > <version>1.0.0.Final</version> > </dependency> > <dependency> > <groupId>com.h2database</groupId> > <artifactId>h2</artifactId> > <version>1.3.161</version> > </dependency> > </dependencies> > <build> > <sourceDirectory>src</sourceDirectory> > <resources> > <resource> > <directory>src</directory> > <excludes> > <exclude>**/*.java</exclude> > </excludes> > </resource> > </resources> > <plugins> > <plugin> > <artifactId>maven-compiler-plugin</artifactId> > <version>3.1</version> > <configuration> > <source>1.8</source> > <target>1.8</target> > </configuration> > </plugin> > </plugins> > </build> > </project> > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17268) Forge wizards block eclipse UI while executing - need to be stoppable/canceble

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17268?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-17268. ------------------------------ Verified in JBT 4.2.0.CR1 build. > Forge wizards block eclipse UI while executing - need to be stoppable/canceble > ------------------------------------------------------------------------------ > > Key: JBIDE-17268 > URL: https://issues.jboss.org/browse/JBIDE-17268 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: forge > Affects Versions: 4.2.0.Beta1 > Reporter: Lincoln Baxter III > Assignee: George Gastaldi > Priority: Critical > Fix For: 4.2.0.CR1 > > > Forge wizards currently can block the eclipse UI. Run any non-trivial command and the Eclipse interface will be completely blocked until the forge command is cancelled, which may not be possible if the command is not using a fine-grained progress monitor and checks frequently. > Introducing a threaded command execution would allow the use of {code}commandThread.interrupt(){code} > And should allow both backgrounding of running wizards, but also more reliable cancellation with Forge's proxy support for thread interrupt handling. > Alternative is to: > provide method to cancel progress. > on first try cancel if command is "CanCancel" then use progress monitor cancel, if not use thread.interrupt() that will stop the progress on proxy boundaries. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18182) JBDS crashes when editor is opened on RHEL 6

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18182?page=com.atlassian.jira.plugi... ] Len DiMaggio edited comment on JBIDE-18182 at 9/2/14 10:03 AM: --------------------------------------------------------------- Just to summarize the issue - JBDS 6,7,8 (beta3) all crash on RHEL 6.6 when ANY file is opened in an editor or an EAP server is started. JBDS 5 is not affected by this bug. was (Author: ldimaggio): Just to summarize the issue - JBDS 5,6,7,8 (beta3) all crash on RHEL 6.6 when ANY file is opened in an editor or an EAP server is started. > JBDS crashes when editor is opened on RHEL 6 > -------------------------------------------- > > Key: JBIDE-18182 > URL: https://issues.jboss.org/browse/JBIDE-18182 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.2.0.Beta3 > Environment: RHEL 6.6 Beta > JBDS 8.0.0.Beta3 (also happening for JBDS 7 and 6) > Reporter: Rastislav Wagner > Priority: Blocker > Fix For: 4.2.0.CR2 > > > JBDS is crashing when I try to open any file in editor or start EAP server (when console is trying to show output). > The only thing I can see is in terminal > {code} > java: cairo-misc.c:380: _cairo_operator_bounded_by_source: Assertion 'NOT_REACHED' failed. > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3139) Error when isnstalling AngularJS from JBoss Central

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-3139?page=com.atlassian.jira.plugin.... ] Mickael Istria commented on JBDS-3139: -------------------------------------- This is also caught by install-grinder tests (on master): https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-g... - needs to be logged in to view. > Error when isnstalling AngularJS from JBoss Central > --------------------------------------------------- > > Key: JBDS-3139 > URL: https://issues.jboss.org/browse/JBDS-3139 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: central > Affects Versions: 8.0.0.CR1 > Environment: JBDS 8.0.0.CR1-v20140831-0335-B201 > Reporter: Vlado Pakan > Priority: Critical > Labels: respin-a > > Getting this error when trying to install AngularJS from JBoss Central: > The following connectors are not available: AngularJS for WebTools -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3139) Error when isnstalling AngularJS from JBoss Central

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-3139?page=com.atlassian.jira.plugin.... ] Mickael Istria updated JBDS-3139: --------------------------------- Labels: respin-a (was: ) > Error when isnstalling AngularJS from JBoss Central > --------------------------------------------------- > > Key: JBDS-3139 > URL: https://issues.jboss.org/browse/JBDS-3139 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: central > Affects Versions: 8.0.0.CR1 > Environment: JBDS 8.0.0.CR1-v20140831-0335-B201 > Reporter: Vlado Pakan > Priority: Critical > Labels: respin-a > > Getting this error when trying to install AngularJS from JBoss Central: > The following connectors are not available: AngularJS for WebTools -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3139) Error when isnstalling AngularJS from JBoss Central

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBDS-3139?page=com.atlassian.jira.plugin.... ] Vlado Pakan updated JBDS-3139: ------------------------------ Description: Getting this error when trying to install AngularJS from JBoss Central: The following connectors are not available: AngularJS for WebTools was: Getting this error when trying to install AngularJS from JBoss Central: The following connectors are not available: AngularHS for WebTools > Error when isnstalling AngularJS from JBoss Central > --------------------------------------------------- > > Key: JBDS-3139 > URL: https://issues.jboss.org/browse/JBDS-3139 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: central > Affects Versions: 8.0.0.CR1 > Environment: JBDS 8.0.0.CR1-v20140831-0335-B201 > Reporter: Vlado Pakan > Priority: Critical > > Getting this error when trying to install AngularJS from JBoss Central: > The following connectors are not available: AngularJS for WebTools -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17274) Support JPA 2.1 in Hibernate Tools

by Jiri Peterka (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17274?page=com.atlassian.jira.plugi... ] Jiri Peterka closed JBIDE-17274. -------------------------------- Support added, verified with JBDS 8.0.0.CR1, GNU/Linux 64. Specific issues will be tracked by separated JIRAs. > Support JPA 2.1 in Hibernate Tools > ---------------------------------- > > Key: JBIDE-17274 > URL: https://issues.jboss.org/browse/JBIDE-17274 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: hibernate > Reporter: Max Rydahl Andersen > Assignee: Koen Aers > Priority: Blocker > Fix For: 4.2.0.CR1 > > > Until now Hibernate tools "survived" that Hibernate 3.5+ could load hibernate 3 and 4 projects metadata without problems. > With JPA 2.1 this changed and it requires Hibernate 4.3+ to load these metadata. > We could update hibernate tools to use hibernate 4.3 to load the metadata but in doing so we would gain support for JPA 2.1 but at least loose support for loading Hibernate 3.3-4.2+ projects that uses custom user types (there could be more combinations that fails - figuring out how much requires a lot of work, but for now at least we know the usertypes are not binary compatible anymore). > To fix this a rethink/reimplementation is needed of how hibernate tools works. > It basicallly needs to become completely independent of hibernate binaries/classes. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3139) Error when isnstalling AngularJS from JBoss Central

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBDS-3139?page=com.atlassian.jira.plugin.... ] Vlado Pakan updated JBDS-3139: ------------------------------ Summary: Error when isnstalling AngularJS from JBoss Central (was: AngularJS is not possible to install from JBoss Central) > Error when isnstalling AngularJS from JBoss Central > --------------------------------------------------- > > Key: JBDS-3139 > URL: https://issues.jboss.org/browse/JBDS-3139 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: central > Affects Versions: 8.0.0.CR1 > Environment: JBDS 8.0.0.CR1-v20140831-0335-B201 > Reporter: Vlado Pakan > Priority: Critical > > Getting this error when trying to install AngularJS from JBoss Central: > The following connectors are not available: AngularHS for WebTools -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3139) AngularJS is not possible to install from JBoss Central

by Vlado Pakan (JIRA)

Vlado Pakan created JBDS-3139: --------------------------------- Summary: AngularJS is not possible to install from JBoss Central Key: JBDS-3139 URL: https://issues.jboss.org/browse/JBDS-3139 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: central Affects Versions: 8.0.0.CR1 Environment: JBDS 8.0.0.CR1-v20140831-0335-B201 Reporter: Vlado Pakan Priority: Critical Getting this error when trying to install AngularJS from JBoss Central: The following connectors are not available: AngularHS for WebTools -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18117) Unable to remove the JAX-RS facet on a Dynamic Web Project version 3.1

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18117?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-18117: --------------------------------------------- linking this in as reason for SR1 update. > Unable to remove the JAX-RS facet on a Dynamic Web Project version 3.1 > ---------------------------------------------------------------------- > > Key: JBIDE-18117 > URL: https://issues.jboss.org/browse/JBIDE-18117 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream, webservices > Affects Versions: 4.2.0.Beta3 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.2.1.Final, 4.3.0.Alpha1 > > > A bug in Eclipse WTP causes the following exception: > {code} > java.lang.ClassCastException: org.eclipse.jst.javaee.web.internal.impl.WebAppImpl cannot be cast to org.eclipse.jst.j2ee.webapplication.WebApp > at org.eclipse.jst.ws.jaxrs.core.internal.project.facet.JAXRSFacetUninstallDelegate.uninstallJAXRSReferencesFromWebApp(JAXRSFacetUninstallDelegate.java:116) > at org.eclipse.jst.ws.jaxrs.core.internal.project.facet.JAXRSFacetUninstallDelegate.execute(JAXRSFacetUninstallDelegate.java:85) > at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.callDelegate(FacetedProject.java:1477) > at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.modifyInternal(FacetedProject.java:441) > at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.mergeChangesInternal(FacetedProject.java:1181) > at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.access$2(FacetedProject.java:1117) > at org.eclipse.wst.common.project.facet.core.internal.FacetedProject$5.run(FacetedProject.java:1099) > at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2313) > at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.mergeChanges(FacetedProject.java:1109) > at org.eclipse.wst.common.project.facet.core.internal.FacetedProjectWorkingCopy.commitChanges(FacetedProjectWorkingCopy.java:2020) > at org.eclipse.wst.common.project.facet.ui.internal.FacetsPropertyPage$4.run(FacetsPropertyPage.java:232) > at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2313) > at org.eclipse.wst.common.project.facet.ui.internal.FacetsPropertyPage$5.run(FacetsPropertyPage.java:246) > at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122) > {code} > the problem comes from an evaluation that checks for dynamic project facet version 2.5 or 3.0 but not higher, in {{JAXRSJEEUtils#isWebApp25or40(Object)}} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 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 September 2014