February 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-19184) Threadlock when JS autocomplete turned on

by Victor Rubezhny (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19184?page=com.atlassian.jira.plugi... ] Victor Rubezhny commented on JBIDE-19184: ----------------------------------------- Tern.java v. 0.8.2 is released: http://oss.opensagres.fr/tern.repository/0.8.2/ AngukarJS-Eclipse is still not (0.8.1-SNAPSHOT still based on Tern.java v. 0.8.1) so we have to wait a bit more for v.0.8.2 to be released. > Threadlock when JS autocomplete turned on > ----------------------------------------- > > Key: JBIDE-19184 > URL: https://issues.jboss.org/browse/JBIDE-19184 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing, upstream > Affects Versions: 4.2.2.Final > Environment: JBDS 8.0.2 > Reporter: Mustafa Musaji > Assignee: Victor Rubezhny > Priority: Blocker > Fix For: 4.2.3.Beta1, 4.3.0.Alpha2 > > Attachments: threaddump_jdk1.7.0_71_1422011702000.txt > > > Seeing a thread lock when using large JS projects when trying to autocomplete. Please refer to attached thread dump. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3064) New JBDS 8 Welcome screen graphics

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3064?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3064: ------------------------------------------- I don't really see a big problem with the main welcome screen we got now. It's using same colors and has just one function: guide you to central. rejecting for now. > New JBDS 8 Welcome screen graphics > ---------------------------------- > > Key: JBDS-3064 > URL: https://issues.jboss.org/browse/JBDS-3064 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: ui/branding > Affects Versions: 8.0.0.Beta2 > Reporter: Pavol Srna > Fix For: 9.x > > > JBDS 8 comes with new splash and installer graphics (see https://issues.jboss.org/browse/JBDS-3036) > It would be good to have new graphics also for the Welcome screen. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3064) New JBDS 8 Welcome screen graphics

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3064?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen closed JBDS-3064. ------------------------------------- Resolution: Rejected > New JBDS 8 Welcome screen graphics > ---------------------------------- > > Key: JBDS-3064 > URL: https://issues.jboss.org/browse/JBDS-3064 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: ui/branding > Affects Versions: 8.0.0.Beta2 > Reporter: Pavol Srna > Fix For: 9.x > > > JBDS 8 comes with new splash and installer graphics (see https://issues.jboss.org/browse/JBDS-3036) > It would be good to have new graphics also for the Welcome screen. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3064) New JBDS 8 Welcome screen graphics

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3064?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-3064: -------------------------------------- Fix Version/s: 9.x (was: 9.0.0.Alpha1) > New JBDS 8 Welcome screen graphics > ---------------------------------- > > Key: JBDS-3064 > URL: https://issues.jboss.org/browse/JBDS-3064 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: ui/branding > Affects Versions: 8.0.0.Beta2 > Reporter: Pavol Srna > Fix For: 9.x > > > JBDS 8 comes with new splash and installer graphics (see https://issues.jboss.org/browse/JBDS-3036) > It would be good to have new graphics also for the Welcome screen. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3355) Missing zip file for JBDS 8.0.2.GA

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3355?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen reassigned JBDS-3355: ----------------------------------------- Assignee: Nick Boldt (was: Max Rydahl Andersen) Component/s: build Since 8.0.2 is an update only release I believe we didn't do much to update on developer.jboss.org but I can see how it can be misleading. On CSP it definitely should be there. [~nickboldt] can you remind me what if anything we did in past on developer.jboss.org and fix it if CSP is wrong/missing the info ? > Missing zip file for JBDS 8.0.2.GA > ---------------------------------- > > Key: JBDS-3355 > URL: https://issues.jboss.org/browse/JBDS-3355 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build > Affects Versions: 8.0.2.GA > Reporter: Andrej Podhradsky > Assignee: Nick Boldt > Priority: Blocker > > I cannot find zip file for JBDS 8.0.2.GA. > At https://www.jboss.org/products/devstudio/download/ and also in CSP there is only zip file for 8.0.0.GA. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19217) org.hibernate.exception.JDBCConnectionException: Error calling DriverManager#getConnection

by Jiri Peterka (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19217?page=com.atlassian.jira.plugi... ] Jiri Peterka closed JBIDE-19217. -------------------------------- Resolution: Rejected Issue was fixed by updating insufficient configuration in hibernate configuration file. Not a bug. Closing. > org.hibernate.exception.JDBCConnectionException: Error calling DriverManager#getConnection > ------------------------------------------------------------------------------------------ > > Key: JBIDE-19217 > URL: https://issues.jboss.org/browse/JBIDE-19217 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.3.0.Alpha1 > Environment: JBDS Version: 9.0.0.Alpha1 nightly build > Build id: Alpha1-v20150204-0904-B2748 > Build date: 20150204-0904 > Reporter: Jiri Peterka > Assignee: Koen Aers > Priority: Critical > Fix For: 4.3.0.Alpha2 > > > While using Hibernate console in maven project > {code} > org.hibernate.exception.JDBCConnectionException: Error calling DriverManager#getConnection > at org.hibernate.exception.internal.SQLStateConversionDelegate.convert(SQLStateConversionDelegate.java:132) > at org.hibernate.engine.jdbc.connections.internal.BasicConnectionCreator$1$1.convert(BasicConnectionCreator.java:118) > at org.hibernate.engine.jdbc.connections.internal.BasicConnectionCreator.convertSqlException(BasicConnectionCreator.java:140) > at org.hibernate.engine.jdbc.connections.internal.DriverManagerConnectionCreator.makeConnection(DriverManagerConnectionCreator.java:54) > at org.hibernate.engine.jdbc.connections.internal.BasicConnectionCreator.createConnection(BasicConnectionCreator.java:75) > at org.hibernate.engine.jdbc.connections.internal.DriverManagerConnectionProviderImpl.configure(DriverManagerConnectionProviderImpl.java:106) > at org.hibernate.boot.registry.internal.StandardServiceRegistryImpl.configureService(StandardServiceRegistryImpl.java:89) > at org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:206) > at org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:178) > at org.hibernate.engine.jdbc.internal.JdbcServicesImpl.buildJdbcConnectionAccess(JdbcServicesImpl.java:260) > at org.hibernate.engine.jdbc.internal.JdbcServicesImpl.configure(JdbcServicesImpl.java:94) > at org.hibernate.boot.registry.internal.StandardServiceRegistryImpl.configureService(StandardServiceRegistryImpl.java:89) > at org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:206) > at org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:178) > at org.hibernate.cfg.SettingsFactory.buildSettings(SettingsFactory.java:80) > at org.hibernate.cfg.Configuration.buildSettingsInternal(Configuration.java:2442) > at org.hibernate.cfg.Configuration.buildSettings(Configuration.java:2434) > at org.jboss.tools.hibernate.proxy.ConfigurationProxy.buildSettings(ConfigurationProxy.java:125) > at org.hibernate.console.ConsoleConfiguration$6.execute(ConsoleConfiguration.java:438) > at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63) > at org.hibernate.console.ConsoleConfiguration.execute(ConsoleConfiguration.java:108) > at org.hibernate.console.ConsoleConfiguration.getSettings(ConsoleConfiguration.java:436) > at org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter$2.execute(LazyDatabaseSchemaWorkbenchAdapter.java:129) > at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63) > at org.hibernate.console.ConsoleConfiguration.execute(ConsoleConfiguration.java:108) > at org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter.readDatabaseSchema(LazyDatabaseSchemaWorkbenchAdapter.java:125) > at org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter.getChildren(LazyDatabaseSchemaWorkbenchAdapter.java:65) > at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.fetchDeferredChildren(BasicWorkbenchAdapter.java:104) > at org.eclipse.ui.progress.DeferredTreeContentManager$1.run(DeferredTreeContentManager.java:233) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > Caused by: java.sql.SQLException: No suitable driver found for jdbc:h2:tcp://localhost/sakila > at java.sql.DriverManager.getConnection(DriverManager.java:689) > at java.sql.DriverManager.getConnection(DriverManager.java:208) > at org.hibernate.engine.jdbc.connections.internal.DriverManagerConnectionCreator.makeConnection(DriverManagerConnectionCreator.java:51) > ... 26 more > {code} > Pom.xml > {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>org.jboss.tools.hibernate.ui.bot.test</groupId> > <artifactId>mvn-hibernate43</artifactId> > <version>0.0.1-SNAPSHOT</version> > <dependencies> > <dependency> > <groupId>org.hibernate</groupId> > <artifactId>hibernate-core</artifactId> > <version>4.3.0.Final</version> > </dependency> > <dependency> > <groupId>org.hibernate</groupId> > <artifactId>hibernate-entitymanager</artifactId> > <version>4.3.0.Final</version> > </dependency> > <dependency> > <groupId>org.hibernate.javax.persistence</groupId> > <artifactId>hibernate-jpa-2.1-api</artifactId> > <version>1.0.0.Final</version> > </dependency> > <dependency> > <groupId>com.h2database</groupId> > <artifactId>h2</artifactId> > <version>1.3.161</version> > </dependency> > </dependencies> > </project> > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3273) JBoss Central: Automatic upstream quickstart integration

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBDS-3273?page=com.atlassian.jira.plugin.... ] Paul Robinson commented on JBDS-3273: ------------------------------------- [~fbricon]: FYI, here's a search that returns all the data held in the DCP for 2 quickstarts. Notice that I replaced all the 'field=' params with 'field=_source', this gives us back the source document for each result. http://dcp.jboss.org/v1/rest/search?field=_source&query=sys_tags%3A(%22JA... I agree, you don't seem to be able to figure out which commit we are indexing from these results. Notice on here http://www.jboss.org//quickstarts/eap/jax-rs-client/index.html that there is a link to https://github.com/jboss-developer/jboss-eap-quickstarts/tree/6.3.0.GA. This is the tag that was indexed. Unfortunately, this data is not yet present in the DCP data. However, we could add it, I'm sure. How about we add: quickstart_id: the directory name of the qs (e.g. 'jax-rs-client') commit_id: 9c2b50a2b68a9d1f9f4fba22d0799964990add9c Would this give you what you need? > JBoss Central: Automatic upstream quickstart integration > --------------------------------------------------------- > > Key: JBDS-3273 > URL: https://issues.jboss.org/browse/JBDS-3273 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: central, requirements > Reporter: Burr Sutter > Assignee: Fred Bricon > Fix For: 9.0.0.Alpha2 > > > Support a more dynamic JBoss Central with direct access to the upstream quickstarts - no longer requiring a fork and tweak to the current quickstarts. We will need some form of 'search UI' as the total list of quickstarts has grown dramatically. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18807) Invalid error message when @Target is missing on a custom Name Binding annotation

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18807?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-18807. --------------------------------- Verified in JBDS 9.0.0.Alpha1 build ID 11. > Invalid error message when @Target is missing on a custom Name Binding annotation > ---------------------------------------------------------------------------------- > > Key: JBIDE-18807 > URL: https://issues.jboss.org/browse/JBIDE-18807 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.2.0.Final > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Labels: jax-rs > Fix For: 4.3.0.Alpha1 > > > With the following code: > {code} > @NameBinding > @Retention(RetentionPolicy.RUNTIME) > public @interface LoggingBinding { > } > {code} > The error message is > {quote} > The Name Binding should have a @Target(ElementType.METHOD) annotation on its type. > {quote} > but it should be > {quote} > The Name Binding should have a @Target(\{ElementType.TYPE, ElementType.METHOD\}) annotation on its type. > {quote} > Note that the QuickFix adds the correct {{(a)Target(\{ElementType.TYPE, ElementType.METHOD\})}}, it's just that the initial error message was misleading -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19324) Arquillian core frezzes Eclipse startup

by Lucia Jelinkova (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19324?page=com.atlassian.jira.plugi... ] Lucia Jelinkova commented on JBIDE-19324: ----------------------------------------- I've just checked and the issue is not present in JBT 4.2.2. > Arquillian core frezzes Eclipse startup > --------------------------------------- > > Key: JBIDE-19324 > URL: https://issues.jboss.org/browse/JBIDE-19324 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: testing-tools > Affects Versions: 4.3.0.Alpha1 > Reporter: Lucia Jelinkova > Assignee: Snjezana Peco > Priority: Blocker > Fix For: 4.3.0.Alpha2 > > Attachments: dump.txt, restart.ogv > > > When I have arquillian.xml with at least one container defined and I open it with Arquillian editor and restart Eclipse, the Eclipse wont start and it freezes on loading arquillian core plugin (see screencast). > I am also attaching thread dump (thanks to [~rhopp]) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18866) allow URL in the form "from-code=git@github.com" for custom app source code and downloadable cartridges

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18866?page=com.atlassian.jira.plugi... ] Marián Labuda edited comment on JBIDE-18866 at 2/20/15 4:58 AM: ---------------------------------------------------------------- I used following from-code: {code} from-code=git@github.com:openshift-cartridges/openshift-wildfly-cartridge.git/ {code} This is not working unfortunately, after hitting Finish button in creating an application on standalone cartridge from git code, the error dialog is shown and following stack trace is in error log: {code} java.lang.IllegalArgumentException: newValue is null at org.jboss.dmr.ModelNode.set(ModelNode.java:499) at com.openshift.internal.client.httpclient.request.JsonMediaType.create(JsonMediaType.java:86) at com.openshift.internal.client.httpclient.request.JsonMediaType.create(JsonMediaType.java:69) at com.openshift.internal.client.httpclient.request.JsonMediaType.create(JsonMediaType.java:63) at com.openshift.internal.client.httpclient.request.JsonMediaType.create(JsonMediaType.java:73) at com.openshift.internal.client.httpclient.request.JsonMediaType.create(JsonMediaType.java:80) at com.openshift.internal.client.httpclient.request.JsonMediaType.create(JsonMediaType.java:71) at com.openshift.internal.client.httpclient.request.JsonMediaType.writeTo(JsonMediaType.java:53) at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:159) at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:144) at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.post(UrlConnectionHttpClient.java:120) at com.openshift.internal.client.RestService.request(RestService.java:164) at com.openshift.internal.client.RestService.request(RestService.java:107) at com.openshift.internal.client.RestService.request(RestService.java:92) at com.openshift.internal.client.AbstractOpenShiftResource$ServiceRequest.execute(AbstractOpenShiftResource.java:169) at com.openshift.internal.client.DomainResource$CreateApplicationRequest.execute(DomainResource.java:478) at com.openshift.internal.client.DomainResource.createApplication(DomainResource.java:186) at com.openshift.internal.client.DomainResource.createApplication(DomainResource.java:168) at com.openshift.client.ApplicationBuilder$NamedUnTypedCartridgeBuilder.build(ApplicationBuilder.java:138) at org.jboss.tools.openshift.express.internal.ui.job.CreateApplicationJob.doRun(CreateApplicationJob.java:92) at org.jboss.tools.openshift.express.internal.ui.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:36) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) {code} was (Author: mlabuda): This is not working unfortunately, after hitting Finish button in creating an application on standalone cartridge from git code, the error dialog is shown and following stack trace is in error log: {code} java.lang.IllegalArgumentException: newValue is null at org.jboss.dmr.ModelNode.set(ModelNode.java:499) at com.openshift.internal.client.httpclient.request.JsonMediaType.create(JsonMediaType.java:86) at com.openshift.internal.client.httpclient.request.JsonMediaType.create(JsonMediaType.java:69) at com.openshift.internal.client.httpclient.request.JsonMediaType.create(JsonMediaType.java:63) at com.openshift.internal.client.httpclient.request.JsonMediaType.create(JsonMediaType.java:73) at com.openshift.internal.client.httpclient.request.JsonMediaType.create(JsonMediaType.java:80) at com.openshift.internal.client.httpclient.request.JsonMediaType.create(JsonMediaType.java:71) at com.openshift.internal.client.httpclient.request.JsonMediaType.writeTo(JsonMediaType.java:53) at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:159) at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:144) at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.post(UrlConnectionHttpClient.java:120) at com.openshift.internal.client.RestService.request(RestService.java:164) at com.openshift.internal.client.RestService.request(RestService.java:107) at com.openshift.internal.client.RestService.request(RestService.java:92) at com.openshift.internal.client.AbstractOpenShiftResource$ServiceRequest.execute(AbstractOpenShiftResource.java:169) at com.openshift.internal.client.DomainResource$CreateApplicationRequest.execute(DomainResource.java:478) at com.openshift.internal.client.DomainResource.createApplication(DomainResource.java:186) at com.openshift.internal.client.DomainResource.createApplication(DomainResource.java:168) at com.openshift.client.ApplicationBuilder$NamedUnTypedCartridgeBuilder.build(ApplicationBuilder.java:138) at org.jboss.tools.openshift.express.internal.ui.job.CreateApplicationJob.doRun(CreateApplicationJob.java:92) at org.jboss.tools.openshift.express.internal.ui.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:36) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) {code} > allow URL in the form "from-code=git(a)github.com" for custom app source code and downloadable cartridges > ------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18866 > URL: https://issues.jboss.org/browse/JBIDE-18866 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.2.0.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: new_and_noteworthy > Fix For: 4.3.0.Alpha1 > > > We should be able to use urls that refer to github repositories when using custom application source code and downloadable cartridges -- This message was sent by Atlassian JIRA (v6.3.11#6341)

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