November 2014 - jbosstools-issues

[JBoss JIRA] (JBIDE-18826) ClassNotFoundException for creating new Hybrid project

by Ilya Buziuk (JIRA)

Ilya Buziuk created JBIDE-18826: ----------------------------------- Summary: ClassNotFoundException for creating new Hybrid project Key: JBIDE-18826 URL: https://issues.jboss.org/browse/JBIDE-18826 Project: Tools (JBoss Tools) Issue Type: Bug Components: aerogear-hybrid Affects Versions: 4.3.0.Alpha1 Reporter: Ilya Buziuk Assignee: Gorkem Ercan Fix For: 4.3.0.Alpha1 stack trace: {code} Caused by: java.lang.ClassNotFoundException: org.apache.http.client.cache.HttpCacheStorage cannot be found by org.eclipse.thym.core_0.1.0.201411202306 at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:432) at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:345) at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:337) at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:160) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) ... 64 more {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18825) CLONED: Add marker/quick fix if test contains non static deployment method

by Lucia Jelinkova (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18825?page=com.atlassian.jira.plugi... ] Lucia Jelinkova commented on JBIDE-18825: ----------------------------------------- The issue has been cloned to separate branch and master development. > CLONED: Add marker/quick fix if test contains non static deployment method > -------------------------------------------------------------------------- > > Key: JBIDE-18825 > URL: https://issues.jboss.org/browse/JBIDE-18825 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: testing-tools > Affects Versions: 4.1.1.Final > Reporter: Lucia Jelinkova > Assignee: Snjezana Peco > Fix For: 4.3.0.Alpha1 > > > In an Arquillian test class, any method marked @Deployment that returns something other than Archive is not being detected. For example, this method is not detected by the tooling, despite the fact that WebArchive extends Archive: > {code} > @Deployment > public static WebArchive createDeployment() { > ...code to create deployment here... > } > {code} > As a result, the deployment validation features do not work, and the Arquillian Cruiser view does not allow the archive to be browsed. Curiously, however, there is no warning about a missing @Deployment method. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18825) CLONED: Add marker/quick fix if test contains non static deployment method

by Lucia Jelinkova (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18825?page=com.atlassian.jira.plugi... ] Lucia Jelinkova resolved JBIDE-18825. ------------------------------------- Labels: (was: new_and_noteworthy) Fix Version/s: (was: 4.2.1.CR1) Resolution: Done > CLONED: Add marker/quick fix if test contains non static deployment method > -------------------------------------------------------------------------- > > Key: JBIDE-18825 > URL: https://issues.jboss.org/browse/JBIDE-18825 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: testing-tools > Affects Versions: 4.1.1.Final > Reporter: Lucia Jelinkova > Assignee: Snjezana Peco > Fix For: 4.3.0.Alpha1 > > > In an Arquillian test class, any method marked @Deployment that returns something other than Archive is not being detected. For example, this method is not detected by the tooling, despite the fact that WebArchive extends Archive: > {code} > @Deployment > public static WebArchive createDeployment() { > ...code to create deployment here... > } > {code} > As a result, the deployment validation features do not work, and the Arquillian Cruiser view does not allow the archive to be browsed. Curiously, however, there is no warning about a missing @Deployment method. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18570) Creating EJB 3.x bean is asking EJB 2.x values

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18570?page=com.atlassian.jira.plugi... ] Martin Malina reassigned JBIDE-18570: ------------------------------------- Assignee: Rob Stryker Assigning to Rob as he is the component owner of ejb3, but not sure if he's the right person here. > Creating EJB 3.x bean is asking EJB 2.x values > ---------------------------------------------- > > Key: JBIDE-18570 > URL: https://issues.jboss.org/browse/JBIDE-18570 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: ejb3, upstream > Reporter: Arun Gupta > Assignee: Rob Stryker > Fix For: 4.3.x > > Attachments: Screen Shot 2014-10-09 at 9.41.39 pm.png > > > Creating a singleton EJB using 3.x wizard and its asking for home and component interfaces from 2.x. This is confusing and redundant. > Image coming in attachment next. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18570) Creating EJB 3.x bean is asking EJB 2.x values

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18570?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-18570: ---------------------------------- Component/s: ejb3 > Creating EJB 3.x bean is asking EJB 2.x values > ---------------------------------------------- > > Key: JBIDE-18570 > URL: https://issues.jboss.org/browse/JBIDE-18570 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: ejb3, upstream > Reporter: Arun Gupta > Fix For: 4.3.x > > Attachments: Screen Shot 2014-10-09 at 9.41.39 pm.png > > > Creating a singleton EJB using 3.x wizard and its asking for home and component interfaces from 2.x. This is confusing and redundant. > Image coming in attachment next. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18825) CLONED: Add marker/quick fix if test contains non static deployment method

by Lucia Jelinkova (JIRA)

Lucia Jelinkova created JBIDE-18825: --------------------------------------- Summary: CLONED: Add marker/quick fix if test contains non static deployment method Key: JBIDE-18825 URL: https://issues.jboss.org/browse/JBIDE-18825 Project: Tools (JBoss Tools) Issue Type: Bug Components: testing-tools Affects Versions: 4.1.1.Final Reporter: Lucia Jelinkova Assignee: Snjezana Peco Fix For: 4.2.1.CR1, 4.3.0.Alpha1 In an Arquillian test class, any method marked @Deployment that returns something other than Archive is not being detected. For example, this method is not detected by the tooling, despite the fact that WebArchive extends Archive: {code} @Deployment public static WebArchive createDeployment() { ...code to create deployment here... } {code} As a result, the deployment validation features do not work, and the Arquillian Cruiser view does not allow the archive to be browsed. Curiously, however, there is no warning about a missing @Deployment method. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18701) CDI validation: Don't warn if CDI 1.1 project doesn't have beans.xml

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18701?page=com.atlassian.jira.plugi... ] Rastislav Wagner closed JBIDE-18701. ------------------------------------ verified in JBDS 8.0.0.CR1-v20141124-0632-B334 > CDI validation: Don't warn if CDI 1.1 project doesn't have beans.xml > -------------------------------------------------------------------- > > Key: JBIDE-18701 > URL: https://issues.jboss.org/browse/JBIDE-18701 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi > Affects Versions: 4.2.0.Final > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Fix For: 4.2.1.CR1 > > > 1. Create a CDI 1.1 project (the project should have CDI 1.1 jars in its classpath, from WildFly 8.0 for example) > 2. Don't create beans.xml file when using New CDI Web Project wizard or remove the file from the created project > 3. See Problems view: > "Missing beans.xml file in the project cdiweb. This file is required for bean archives [JSR-299 §12.1]" > This warning message should appear only for CDI 1.0 projects. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18008) Nested jars prevent SonarQube/FindBugs from running

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18008?page=com.atlassian.jira.plugi... ] Mickael Istria resolved JBIDE-18008. ------------------------------------ Resolution: Done Thanks Rob, job is now working great. You can now enjoy various quality reports at http://sonar.mw.lab.eng.bos.redhat.com/sonar/project/profile/org.jboss.to... > Nested jars prevent SonarQube/FindBugs from running > --------------------------------------------------- > > Key: JBIDE-18008 > URL: https://issues.jboss.org/browse/JBIDE-18008 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: archives, build, qa > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.3.0.Alpha1 > > > Bundle org.jboss.ide.eclipse.archives.core makes SonarQube analysis fail because it's classes get included in some nested jar (and get to different location that target/classes). > Cf https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > {code} > [ERROR] Failed to execute goal org.codehaus.mojo:sonar-maven-plugin:2.4:sonar (default-cli) on project server.all: Can not execute SonarQube analysis: Can not execute Findbugs: Findbugs needs sources to be compiled. Please build project before executing sonar and check the location of compiled classes. -> [Help 1] > {code} > This is an exploded bundles with nested jars, we should investigate whether it's possible to turn it into a more standard jar, which would still be usable in its Ant version. Cf ./archives/tests/org.jboss.ide.eclipse.archives.test/inputs/projects/SimpleAntTest > Also, the jvmmonitor bundles use nested jars. We should avoid that too. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18008) Nested jars prevent SonarQube/FindBugs from running

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18008?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-18008: ----------------------------------- Component/s: build qa > Nested jars prevent SonarQube/FindBugs from running > --------------------------------------------------- > > Key: JBIDE-18008 > URL: https://issues.jboss.org/browse/JBIDE-18008 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: archives, build, qa > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.3.0.Alpha1 > > > Bundle org.jboss.ide.eclipse.archives.core makes SonarQube analysis fail because it's classes get included in some nested jar (and get to different location that target/classes). > Cf https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > {code} > [ERROR] Failed to execute goal org.codehaus.mojo:sonar-maven-plugin:2.4:sonar (default-cli) on project server.all: Can not execute SonarQube analysis: Can not execute Findbugs: Findbugs needs sources to be compiled. Please build project before executing sonar and check the location of compiled classes. -> [Help 1] > {code} > This is an exploded bundles with nested jars, we should investigate whether it's possible to turn it into a more standard jar, which would still be usable in its Ant version. Cf ./archives/tests/org.jboss.ide.eclipse.archives.test/inputs/projects/SimpleAntTest > Also, the jvmmonitor bundles use nested jars. We should avoid that too. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18008) Nested jars prevent SonarQube/FindBugs from running

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18008?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-18008: ----------------------------------- Fix Version/s: 4.3.0.Alpha1 (was: 4.3.x) > Nested jars prevent SonarQube/FindBugs from running > --------------------------------------------------- > > Key: JBIDE-18008 > URL: https://issues.jboss.org/browse/JBIDE-18008 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: archives > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.3.0.Alpha1 > > > Bundle org.jboss.ide.eclipse.archives.core makes SonarQube analysis fail because it's classes get included in some nested jar (and get to different location that target/classes). > Cf https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > {code} > [ERROR] Failed to execute goal org.codehaus.mojo:sonar-maven-plugin:2.4:sonar (default-cli) on project server.all: Can not execute SonarQube analysis: Can not execute Findbugs: Findbugs needs sources to be compiled. Please build project before executing sonar and check the location of compiled classes. -> [Help 1] > {code} > This is an exploded bundles with nested jars, we should investigate whether it's possible to turn it into a more standard jar, which would still be usable in its Ant version. Cf ./archives/tests/org.jboss.ide.eclipse.archives.test/inputs/projects/SimpleAntTest > Also, the jvmmonitor bundles use nested jars. We should avoid that too. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 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 November 2014