September 2014 - jbosstools-issues

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

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18265?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-18265: ---------------------------------------- Component/s: testing-tools > 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 > Components: testing-tools > 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-11766) Work with "Annotation Properties" view breaks JAX-RS explorer

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11766?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-11766: --------------------------------------- [~rrabara], thanks for the attached video. I can reproduce the eratic behaviour here too. Let me fix that ;) > Work with "Annotation Properties" view breaks JAX-RS explorer > ------------------------------------------------------------- > > Key: JBIDE-11766 > URL: https://issues.jboss.org/browse/JBIDE-11766 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 3.3.0.Beta3 > Reporter: Jaroslav Jankovič > Assignee: Xavier Coulon > Fix For: 4.2.0.CR1 > > Attachments: report-2.ogv > > > After some random clicking on JAX-RS annotation in Annotation Properties view, JAX-RS breaks. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18261) When connectors have same ids, priority should be given to early-access

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18261?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-18261: ------------------------------------- If you have JBT-IS 1.0.1.GA on central and JBT-IS 1.0.1.CR1 on early access, then you're doing it wrong. CR1 should be dropped from EA. Or replaced with next version. > When connectors have same ids, priority should be given to early-access > ----------------------------------------------------------------------- > > Key: JBIDE-18261 > URL: https://issues.jboss.org/browse/JBIDE-18261 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.2.0.CR1 > Reporter: Mickael Istria > Assignee: Mickael Istria > Labels: respin-a > Fix For: 4.2.0.CR1 > > > Assuming we have 2 discoveyr connectors with same IDs (example of AngularJS vs AngularJS+Ionic), then when both are visible, priority should be given to the one which is early access. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15825) JAX-RS problems don't show up after target runtime is set

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15825?page=com.atlassian.jira.plugi... ] Xavier Coulon reassigned JBIDE-15825: ------------------------------------- Assignee: Max Rydahl Andersen (was: Xavier Coulon) Please review the PR > JAX-RS problems don't show up after target runtime is set > --------------------------------------------------------- > > Key: JBIDE-15825 > URL: https://issues.jboss.org/browse/JBIDE-15825 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.1.1.Beta1 > Reporter: Radoslav Rábara > Assignee: Max Rydahl Andersen > Labels: respin-a > Fix For: 4.2.0.CR1 > > > JAX-RS problems don't show up after target runtime is set on project that was created with target runtime set to <None>. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15825) JAX-RS problems don't show up after target runtime is set

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15825?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-15825: ---------------------------------- Labels: respin-a (was: ) > JAX-RS problems don't show up after target runtime is set > --------------------------------------------------------- > > Key: JBIDE-15825 > URL: https://issues.jboss.org/browse/JBIDE-15825 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.1.1.Beta1 > Reporter: Radoslav Rábara > Assignee: Xavier Coulon > Labels: respin-a > Fix For: 4.2.0.CR1 > > > JAX-RS problems don't show up after target runtime is set on project that was created with target runtime set to <None>. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18263) when I install arquillian in jboss tools i says early access is installed - that is only true for devstudio

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18263?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-18263: ---------------------------------------- Arquillian is listed as Early-Access for JBT: https://github.com/jbosstools/jbosstools-discovery/blob/master/jbosstools... So what's the point here, Arquillian isn't early access any more? > when I install arquillian in jboss tools i says early access is installed - that is only true for devstudio > ----------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18263 > URL: https://issues.jboss.org/browse/JBIDE-18263 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > > arquillian is part of the main site of jboss tools and afaics only in earlyaccess of devstudio. > Looks like the metadata for whats is earlyaccess is wrong or ? -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18095) Server adapter fails to publish modules with non-ASCII class names

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18095?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-18095. --------------------------------- Verified both compressed and exploded wars with a utility jar. Verified in JBDS 8.0.0.CR1 B201 > Server adapter fails to publish modules with non-ASCII class names > ------------------------------------------------------------------ > > Key: JBIDE-18095 > URL: https://issues.jboss.org/browse/JBIDE-18095 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta3, 4.2.0.CR1 > Environment: Windows 7, Eclipse Java EE IDE for Web Developers Luna Release (4.4.0) 20140612-0600, JBossAS Tools 3.0.0.CR1-v20140822-0028-B573 (nightly/luna repo), JBoss EAP 5.2.0 on Oracle Java 1.7.0_45 > Reporter: Axel Wathne > Assignee: Rob Stryker > Priority: Critical > Labels: regression > Fix For: 4.2.0.CR1 > > > I have a 35 module war/ear project, where multiple plain jar modules are deployed as bundled libraries in the ear module. The problem is, two of these modules fail to deploy to the server deploy folder, and as a result, ClassNotFoundExceptions are thrown from the JBoss class loader. If I close the projects containing the two troublesome modules, they are deployed correctly and everything is fine (as with the Kepler version). The two modules show up in the "Bundled libraries" view in the ear project, and they show under the ear deployment in the server view. But, in the server view, the decoration on the server is always "Republish" after startup, even though the ear module is "Synchronized". The non-deployed modules have no decoration at all, while the other modules all show "Synchronized". > The problem seems to be classes with non-ASCII class names. If I rename the classes, the modules are deployed correctly. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18252) "Mark as Deployable" does not work in Package Explorer and is not visible in Editor context menu

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18252?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-18252: ---------------------------------------- Priority: Critical (was: Major) > "Mark as Deployable" does not work in Package Explorer and is not visible in Editor context menu > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-18252 > URL: https://issues.jboss.org/browse/JBIDE-18252 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.CR1 > Reporter: Daniel Azarov > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.2.0.CR1, 4.3.0.Alpha1 > > Attachments: CannotPublishToServer.png > > > There is a regression from JBIDE-15678 and JBIDE-18133 > Actions "Mark/Unmark as Deployable" do not working in Package Explorer with follow error: > !CannotPublishToServer.png! > Also these actions are not visible in editor context menu -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18262) exception on startup

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18262?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-18262: ------------------------------------- Is it a blocker? Can the servers be used when added manually? > exception on startup > -------------------- > > Key: JBIDE-18262 > URL: https://issues.jboss.org/browse/JBIDE-18262 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, runtime-detection > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > > not sure what causes it but I'm getting this: > java.lang.IllegalArgumentException: invalid version "6.0.0.CR01.1": invalid qualifier "CR01.1" > at org.osgi.framework.Version.validate(Version.java:205) > at org.osgi.framework.Version.<init>(Version.java:156) > at org.jboss.tools.as.runtimes.integration.util.RuntimeMatcher$RuntimeRangeRepresentation.matchesVersion(RuntimeMatcher.java:83) > at org.jboss.tools.as.runtimes.integration.util.RuntimeMatcher.findExistingRuntimes(RuntimeMatcher.java:171) > at org.jboss.tools.as.runtimes.integration.util.RuntimeMatcher.findExistingRuntimes(RuntimeMatcher.java:151) > at org.jboss.tools.project.examples.fixes.WTPRuntimeFix.getRuntimesFromPattern(WTPRuntimeFix.java:102) > at org.jboss.tools.project.examples.fixes.WTPRuntimeFix.getBestRuntime(WTPRuntimeFix.java:249) > at org.jboss.tools.project.examples.fixes.WTPRuntimeFix.canFix(WTPRuntimeFix.java:130) > at org.jboss.tools.project.examples.ProjectExamplesActivator.canFix(ProjectExamplesActivator.java:818) > at org.jboss.tools.central.jobs.RefreshTutorialsJob.run(RefreshTutorialsJob.java:68) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18262) exception on startup

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18262?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-18262: -------------------------------- Assignee: Rob Stryker > exception on startup > -------------------- > > Key: JBIDE-18262 > URL: https://issues.jboss.org/browse/JBIDE-18262 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, runtime-detection > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > > not sure what causes it but I'm getting this: > java.lang.IllegalArgumentException: invalid version "6.0.0.CR01.1": invalid qualifier "CR01.1" > at org.osgi.framework.Version.validate(Version.java:205) > at org.osgi.framework.Version.<init>(Version.java:156) > at org.jboss.tools.as.runtimes.integration.util.RuntimeMatcher$RuntimeRangeRepresentation.matchesVersion(RuntimeMatcher.java:83) > at org.jboss.tools.as.runtimes.integration.util.RuntimeMatcher.findExistingRuntimes(RuntimeMatcher.java:171) > at org.jboss.tools.as.runtimes.integration.util.RuntimeMatcher.findExistingRuntimes(RuntimeMatcher.java:151) > at org.jboss.tools.project.examples.fixes.WTPRuntimeFix.getRuntimesFromPattern(WTPRuntimeFix.java:102) > at org.jboss.tools.project.examples.fixes.WTPRuntimeFix.getBestRuntime(WTPRuntimeFix.java:249) > at org.jboss.tools.project.examples.fixes.WTPRuntimeFix.canFix(WTPRuntimeFix.java:130) > at org.jboss.tools.project.examples.ProjectExamplesActivator.canFix(ProjectExamplesActivator.java:818) > at org.jboss.tools.central.jobs.RefreshTutorialsJob.run(RefreshTutorialsJob.java:68) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) -- 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