September 2014 - jbosstools-issues

[JBoss JIRA] (JBIDE-18208) JBoss Central New and Noteworthy for 4.2.0.CR1

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18208?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-18208: ---------------------------------------- Assignee: Fred Bricon > JBoss Central New and Noteworthy for 4.2.0.CR1 > ---------------------------------------------- > > Key: JBIDE-18208 > URL: https://issues.jboss.org/browse/JBIDE-18208 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: central > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Priority: Critical > Fix For: 4.2.0.CR1 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If JBoss Central is not listed here check if there are issues that should be added and add them. > Document the ones relevant for JBoss Central by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/wha...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18206) server New and Noteworthy for 4.2.0.CR1

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18206?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-18206: ---------------------------------------- Assignee: Rob Stryker > server New and Noteworthy for 4.2.0.CR1 > --------------------------------------- > > Key: JBIDE-18206 > URL: https://issues.jboss.org/browse/JBIDE-18206 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: archives, jmx, server > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.2.0.CR1 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If server is not listed here check if there are issues that should be added and add them. > Document the ones relevant for server by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/wha...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18218) Missing Provider records for hibernate feature

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18218?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen reassigned JBIDE-18218: ------------------------------------------- Assignee: Max Rydahl Andersen > Missing Provider records for hibernate feature > ---------------------------------------------- > > Key: JBIDE-18218 > URL: https://issues.jboss.org/browse/JBIDE-18218 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, hibernate > Affects Versions: 4.2.0.Beta3 > Environment: JBDS 8.0.0.CR1, GNU/Linux 64, Fedora 20 > Reporter: Jiri Peterka > Assignee: Max Rydahl Andersen > Priority: Minor > Fix For: 4.2.0.Final > > Attachments: empty-provider-fields.png > > > There are empty Provider fields under Hibernate Feature (see screenshot) -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18264) Weird JMX entries in server view

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18264?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-18264: ---------------------------------- Attachment: weird-entries-2.png And btw look what happened here when I added another server (EAP 5.2) and started it: !weird-entries.png! You can see that the entry within the first (stopped) server kind of makes sense, at least it's called JMX. But inside the started server, there's just [Disconnected] and then two other such entries completely on their own. Personally I would get rid of this altogether, I don't really see any purpose. > Weird JMX entries in server view > -------------------------------- > > Key: JBIDE-18264 > URL: https://issues.jboss.org/browse/JBIDE-18264 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.CR1 > Reporter: Martin Malina > Assignee: Rob Stryker > Labels: respin-a > Fix For: 4.2.0.CR1 > > Attachments: weird-entries-2.png, weird-entries.png > > > When I start EAP 6, two new entries appear in the Server view: > [Disconnected] > [Disconnected] > !weird-entries.png! > That looks pretty weird. > I can right-click them and connect and they actually correspond to the two server entries in JMX Navigator - one in Local Processes, the other in Server Connections. But there is nothing else I can do with these in the server views. What's the point of having it there? I find it confusing, especially since there is no explanations whatsoever about what these are. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18264) Weird JMX entries in server view

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18264?page=com.atlassian.jira.plugi... ] Martin Malina edited comment on JBIDE-18264 at 9/4/14 8:45 AM: --------------------------------------------------------------- And btw look what happened here when I added another server (EAP 5.2) and started it: !weird-entries-2.png! You can see that the entry within the first (stopped) server kind of makes sense, at least it's called JMX. But inside the started server, there's just [Disconnected] and then two other such entries completely on their own. Personally I would get rid of this altogether, I don't really see any purpose. was (Author: mmalina): And btw look what happened here when I added another server (EAP 5.2) and started it: !weird-entries.png! You can see that the entry within the first (stopped) server kind of makes sense, at least it's called JMX. But inside the started server, there's just [Disconnected] and then two other such entries completely on their own. Personally I would get rid of this altogether, I don't really see any purpose. > Weird JMX entries in server view > -------------------------------- > > Key: JBIDE-18264 > URL: https://issues.jboss.org/browse/JBIDE-18264 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.CR1 > Reporter: Martin Malina > Assignee: Rob Stryker > Labels: respin-a > Fix For: 4.2.0.CR1 > > Attachments: weird-entries-2.png, weird-entries.png > > > When I start EAP 6, two new entries appear in the Server view: > [Disconnected] > [Disconnected] > !weird-entries.png! > That looks pretty weird. > I can right-click them and connect and they actually correspond to the two server entries in JMX Navigator - one in Local Processes, the other in Server Connections. But there is nothing else I can do with these in the server views. What's the point of having it there? I find it confusing, especially since there is no explanations whatsoever about what these are. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18223) Forge context should be set to the 'new project location' after 'project-new' command

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18223?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-18223: --------------------------------------------- dont think this is a major thing - it seem to depend on where you call cmd+4 from. > Forge context should be set to the 'new project location' after 'project-new' command > ------------------------------------------------------------------------------------- > > Key: JBIDE-18223 > URL: https://issues.jboss.org/browse/JBIDE-18223 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: forge > Affects Versions: 4.2.0.CR1 > Reporter: Pavol Srna > Assignee: George Gastaldi > Labels: respin-a > Fix For: 4.2.1.Final > > > Forge context should be set to the 'new project location' after project-new command execution. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18223) Forge context should be set to the 'new project location' after 'project-new' command

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18223?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-18223: ---------------------------------------- Fix Version/s: 4.2.1.Final (was: 4.2.0.CR1) > Forge context should be set to the 'new project location' after 'project-new' command > ------------------------------------------------------------------------------------- > > Key: JBIDE-18223 > URL: https://issues.jboss.org/browse/JBIDE-18223 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: forge > Affects Versions: 4.2.0.CR1 > Reporter: Pavol Srna > Assignee: George Gastaldi > Labels: respin-a > Fix For: 4.2.1.Final > > > Forge context should be set to the 'new project location' after project-new command execution. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18265) NullPointerException in ArquillianBuilder when creating test class with the name Test

by Lucia Jelinkova (JIRA)

Lucia Jelinkova created JBIDE-18265: --------------------------------------- Summary: NullPointerException in ArquillianBuilder when creating test class with the name Test Key: JBIDE-18265 URL: https://issues.jboss.org/browse/JBIDE-18265 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 4.2.0.CR1 Reporter: Lucia Jelinkova Priority: Critical Fix For: 4.2.0.CR2 When I try to create an Arquillan test class with the name Test, it is created, however, the Arquillian builder fails with NP. {code} java.lang.NullPointerException at org.eclipse.jdt.core.dom.MethodBinding.filterTypeAnnotations(MethodBinding.java:205) at org.eclipse.jdt.core.dom.MethodBinding.getAnnotations(MethodBinding.java:104) at org.jboss.tools.arquillian.core.internal.util.ArquillianSearchEngine.isDeploymentMethod(ArquillianSearchEngine.java:862) at org.jboss.tools.arquillian.core.internal.util.ArquillianSearchEngine.getDeploymentMethods(ArquillianSearchEngine.java:849) at org.jboss.tools.arquillian.core.internal.util.ArquillianSearchEngine.hasDeploymentMethod(ArquillianSearchEngine.java:599) at org.jboss.tools.arquillian.core.internal.builder.ArquillianBuilder.build(ArquillianBuilder.java:255) at org.jboss.tools.arquillian.core.internal.builder.ArquillianBuilder.buildDelta(ArquillianBuilder.java:210) at org.jboss.tools.arquillian.core.internal.builder.ArquillianBuilder.build(ArquillianBuilder.java:109) at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:734) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:206) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:246) at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:299) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:302) at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:358) at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:381) at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143) at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) {code} This is because the test method is generated with the @Test annotation without fully qualified name. {code} @Test public void test() { fail("Not yet implemented"); } {code} In JUnit, when I tried to create test class with the name Test, the @Test annotation was generated with fullly qualified name {code} @Test @org.junit.Test public void test() { fail("Not yet implemented"); } {code} However, when I checked that I want do generate tearDown method, JUnit created the annotation withou fully qualified name too. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18223) Forge context should be set to the 'new project location' after 'project-new' command

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18223?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-18223: ---------------------------------------- Assignee: George Gastaldi > Forge context should be set to the 'new project location' after 'project-new' command > ------------------------------------------------------------------------------------- > > Key: JBIDE-18223 > URL: https://issues.jboss.org/browse/JBIDE-18223 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: forge > Affects Versions: 4.2.0.CR1 > Reporter: Pavol Srna > Assignee: George Gastaldi > Labels: respin-a > Fix For: 4.2.0.CR1 > > > Forge context should be set to the 'new project location' after project-new command execution. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18257) Missing quickfix for NameBinding without Target and Retention annotations

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18257?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-18257: ---------------------------------- Fix Version/s: 4.2.1.Final 4.3.0.Alpha1 (was: 4.2.x) > Missing quickfix for NameBinding without Target and Retention annotations > ------------------------------------------------------------------------- > > Key: JBIDE-18257 > URL: https://issues.jboss.org/browse/JBIDE-18257 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: webservices > Affects Versions: 4.2.0.CR1 > Reporter: Radoslav Rábara > Assignee: Xavier Coulon > Labels: respin-a > Fix For: 4.2.1.Final, 4.3.0.Alpha1 > > -- 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