September 2014 - jbosstools-issues

[JBoss JIRA] (JBIDE-18436) Central archetype versions should depend on selected runtime version

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18436?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-18436: --------------------------------------------- ..but the runtime id's was never unique..(soa-p, etc.) anyways good if we can fix it this way. > Central archetype versions should depend on selected runtime version > -------------------------------------------------------------------- > > Key: JBIDE-18436 > URL: https://issues.jboss.org/browse/JBIDE-18436 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.2.0.CR1 > Environment: JBDS 8 CR1, Fedora 20 > Reporter: Vineet Reynolds > Assignee: Fred Bricon > Priority: Critical > Fix For: 4.2.0.CR2 > > > A newly created project using the "Java EE Web Project" in JBoss Central, uses the {{org.jboss.bom:jboss-javaee-6.0-with-tools:1.0.4.Final-redhat-4}} and {{org.jboss.bom:jboss-javaee-6.0-with-hibernate:1.0.4.Final-redhat-4}} BOMs in the {{dependencyManagement}} section. > These are the older versions. It should instead be using the BOMs from the {{org.jboss.bom.wfk}} and {{org.jboss.bom.eap}} groupIds instead. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17619) Console for remote server disappears when workspace is switched

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17619?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-17619: --------------------------------------- A) I just tried a simple workspace restart and the console still disappeared. But I think at one point it was preserved between restarts so that's why I added the workspace switch to make the issue 100 % reproducible. B) Yes, only remote servers C) No, nothing in the error log. > Console for remote server disappears when workspace is switched > --------------------------------------------------------------- > > Key: JBIDE-17619 > URL: https://issues.jboss.org/browse/JBIDE-17619 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta2 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.2.0.CR2 > > > This happened to me today. I created a remote server (EAP 6.2, management, no runtime) and when I started it, I saw the console output for the server. But after some more tinkering with it, the console suddenly stopped appearing (I had the console view open). Not even IDE restart helped. > The only thing that helped me here was to delete the server and create a new one. > I think I have a way to reproduce this - it actually happens when you create the server, then switch to a new workspace, then back again. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18399) JBT website "What's new" page missing Alpha-Beta3 new features

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18399?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-18399: --------------------------------------------- Xavier, do you remember why we don't have this there? > JBT website "What's new" page missing Alpha-Beta3 new features > -------------------------------------------------------------- > > Key: JBIDE-18399 > URL: https://issues.jboss.org/browse/JBIDE-18399 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: website > Affects Versions: 4.2.0.CR1 > Reporter: Michelle Murray > Fix For: 4.2.0.CR2 > > > http://tools.jboss.org/documentation/whatsnew/jbosstools/4.2.0.CR1.html > Alpha-Beta3 tabs for 4.2.0 have been removed with the release of CR1. Now it looks like the only improvements since 4.2.1 are those listed for CR1. I assume for the 4.2.0.Final release all of the "What's new" for Alpha-Beta3-CR2 will all be combined into one tab titled 4.2.0.Final. Until then, can the Alpha-Beta3 pages be reinstated? -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18399) JBT website "What's new" page missing Alpha-Beta3 new features

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18399?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-18399: ---------------------------------------- Fix Version/s: 4.2.0.CR2 > JBT website "What's new" page missing Alpha-Beta3 new features > -------------------------------------------------------------- > > Key: JBIDE-18399 > URL: https://issues.jboss.org/browse/JBIDE-18399 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: website > Affects Versions: 4.2.0.CR1 > Reporter: Michelle Murray > Fix For: 4.2.0.CR2 > > > http://tools.jboss.org/documentation/whatsnew/jbosstools/4.2.0.CR1.html > Alpha-Beta3 tabs for 4.2.0 have been removed with the release of CR1. Now it looks like the only improvements since 4.2.1 are those listed for CR1. I assume for the 4.2.0.Final release all of the "What's new" for Alpha-Beta3-CR2 will all be combined into one tab titled 4.2.0.Final. Until then, can the Alpha-Beta3 pages be reinstated? -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17619) Console for remote server disappears when workspace is switched

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17619?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-17619: --------------------------------------------- C) anything in error log ? > Console for remote server disappears when workspace is switched > --------------------------------------------------------------- > > Key: JBIDE-17619 > URL: https://issues.jboss.org/browse/JBIDE-17619 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta2 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.2.0.CR2 > > > This happened to me today. I created a remote server (EAP 6.2, management, no runtime) and when I started it, I saw the console output for the server. But after some more tinkering with it, the console suddenly stopped appearing (I had the console view open). Not even IDE restart helped. > The only thing that helped me here was to delete the server and create a new one. > I think I have a way to reproduce this - it actually happens when you create the server, then switch to a new workspace, then back again. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16066) Top-Down WS deployment isn't successful when selecting Start/Test service in Web Service dialog

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16066?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-16066: --------------------------------------------- Brian - what is failing with respect to EAP 6.1 and JBDS 8 cr1 ? that should not happen either and is more critical issue. and to look into this first I would check if the deployment (jar/war?) actually have the class on the file system ? > Top-Down WS deployment isn't successful when selecting Start/Test service in Web Service dialog > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-16066 > URL: https://issues.jboss.org/browse/JBIDE-16066 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.1.1.CR1 > Environment: JBDS 7.1.0 CR1, EAP-6.1 > Reporter: Radoslav Rábara > Assignee: Brian Fitzpatrick > Fix For: 4.2.0.CR2 > > Attachments: topDownServer.log > > > Deployment isn't successful when Top-Down web service is created with slider level selected to "Start service" or "Test service". Project is deployed to the server but the service endpoint isn't added so the service is not accessible. > It works with other slider levels and all levels works when the server isn't started before the web service is created. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18453) NPE while processing change in code

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18453?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-18453: ---------------------------------- Priority: Critical (was: Major) > NPE while processing change in code > ----------------------------------- > > Key: JBIDE-18453 > URL: https://issues.jboss.org/browse/JBIDE-18453 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.2.0.CR1 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Priority: Critical > > Following exception occurred while editing some code in a sample project: > {code} > java.lang.NullPointerException > at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JavaElementDeltaScanner.scanDelta(JavaElementDeltaScanner.java:139) > at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JavaElementDeltaScanner.scanAndFilterEvent(JavaElementDeltaScanner.java:73) > at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JavaElementChangedBuildJob.run(JavaElementChangedBuildJob.java:57) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18453) NPE while processing change in code

by Xavier Coulon (JIRA)

Xavier Coulon created JBIDE-18453: ------------------------------------- Summary: NPE while processing change in code Key: JBIDE-18453 URL: https://issues.jboss.org/browse/JBIDE-18453 Project: Tools (JBoss Tools) Issue Type: Bug Components: webservices Affects Versions: 4.2.0.CR1 Reporter: Xavier Coulon Following exception occurred while editing some code in a sample project: {code} java.lang.NullPointerException at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JavaElementDeltaScanner.scanDelta(JavaElementDeltaScanner.java:139) at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JavaElementDeltaScanner.scanAndFilterEvent(JavaElementDeltaScanner.java:73) at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JavaElementChangedBuildJob.run(JavaElementChangedBuildJob.java:57) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18453) NPE while processing change in code

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18453?page=com.atlassian.jira.plugi... ] Xavier Coulon reassigned JBIDE-18453: ------------------------------------- Assignee: Xavier Coulon > NPE while processing change in code > ----------------------------------- > > Key: JBIDE-18453 > URL: https://issues.jboss.org/browse/JBIDE-18453 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.2.0.CR1 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > > Following exception occurred while editing some code in a sample project: > {code} > java.lang.NullPointerException > at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JavaElementDeltaScanner.scanDelta(JavaElementDeltaScanner.java:139) > at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JavaElementDeltaScanner.scanAndFilterEvent(JavaElementDeltaScanner.java:73) > at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JavaElementChangedBuildJob.run(JavaElementChangedBuildJob.java:57) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14305) Error popup when runing schema ddl with Hibernate Configurations

by Andrei Ivanov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14305?page=com.atlassian.jira.plugi... ] Andrei Ivanov commented on JBIDE-14305: --------------------------------------- My current way of reproducing is to generate entities from the db tables. Can you check that way? > Error popup when runing schema ddl with Hibernate Configurations > ----------------------------------------------------------------- > > Key: JBIDE-14305 > URL: https://issues.jboss.org/browse/JBIDE-14305 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Reporter: labdoui labdoui > Assignee: Koen Aers > Priority: Critical > Fix For: 4.2.0.CR2 > > Attachments: workspace.zip > > > Using Hibernate 4, and slf4j 1.7.2, I can't runing my ddl schema > to reproduce the problem just explore the database from hibernate console > java.lang.NoSuchMethodError: org.slf4j.spi.LocationAwareLogger.log(Lorg/slf4j/Marker;Ljava/lang/String;ILjava/lang/String;[Ljava/lang/Object;Ljava/lang/Throwable;)V > at org.apache.commons.logging.impl.SLF4JLocationAwareLog.debug(SLF4JLocationAwareLog.java:133) > at org.hibernate.cfg.reveng.dialect.JDBCMetaDataDialect.getTables(JDBCMetaDataDialect.java:26) > at org.hibernate.cfg.reveng.JDBCReader.processTables(JDBCReader.java:476) > at org.hibernate.cfg.reveng.JDBCReader.readDatabaseSchema(JDBCReader.java:74) > at org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter$2.execute(LazyDatabaseSchemaWorkbenchAdapter.java:116) > at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63) > at org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter.readDatabaseSchema(LazyDatabaseSchemaWorkbenchAdapter.java:107) > at org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter.getChildren(LazyDatabaseSchemaWorkbenchAdapter.java:63) > at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.fetchDeferredChildren(BasicWorkbenchAdapter.java:106) > at org.eclipse.ui.progress.DeferredTreeContentManager$1.run(DeferredTreeContentManager.java:235) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 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