[JBoss JIRA] (FORGE-2125) Frequent errors like this "java.lang.IllegalStateException: Test runner could not locate test class [org.jboss.windup.reporting.FreeMarkerIterationOperationTest] in any deployed Addon."
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-2125?page=com.atlassian.jira.plugin... ]
George Gastaldi reopened FORGE-2125:
------------------------------------
Reopening this issue, as this is still happening.
> Frequent errors like this "java.lang.IllegalStateException: Test runner could not locate test class [org.jboss.windup.reporting.FreeMarkerIterationOperationTest] in any deployed Addon."
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: FORGE-2125
> URL: https://issues.jboss.org/browse/FORGE-2125
> Project: Forge
> Issue Type: Bug
> Reporter: Jess Sightler
> Assignee: Matej Briskar
> Fix For: 2.14.0.Final
>
>
> These happen in frequently within the Windup tests and appear to relate to some startup problem in Forge:
> Full stack:
> {code}
> java.lang.IllegalStateException: Test runner could not locate test class [org.jboss.windup.reporting.FreeMarkerIterationOperationTest] in any deployed Addon.
> at org.jboss.forge.arquillian.ForgeTestMethodExecutor.invoke(ForgeTestMethodExecutor.java:234)
> at org.jboss.arquillian.container.test.impl.execution.RemoteTestExecuter.execute(RemoteTestExecuter.java:109)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116)
> at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67)
> at org.jboss.arquillian.container.test.impl.execution.ClientTestExecuter.execute(ClientTestExecuter.java:57)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
> at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142)
> at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createTestContext(ContainerEventController.java:129)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:65)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:102)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:84)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145)
> at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.test(EventTestRunnerAdaptor.java:111)
> at org.jboss.arquillian.junit.Arquillian$6.evaluate(Arquillian.java:294)
> at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:269)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
> at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:193)
> at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:345)
> at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:49)
> at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:207)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
> at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:155)
> at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124)
> at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200)
> at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 4 months
[JBoss JIRA] (FORGE-2223) Unable to create xhtml file
by Michael Schwartz (JIRA)
[ https://issues.jboss.org/browse/FORGE-2223?page=com.atlassian.jira.plugin... ]
Michael Schwartz commented on FORGE-2223:
-----------------------------------------
I am sure you do not need my help but the source which produces the error is at
org.jboss.forge.addon.parser.xml.resources.XMLResourceGenerator
method handles()
in the parser-xml-impl package.
regards, Mike
> Unable to create xhtml file
> ---------------------------
>
> Key: FORGE-2223
> URL: https://issues.jboss.org/browse/FORGE-2223
> Project: Forge
> Issue Type: Bug
> Components: Addon Development
> Affects Versions: 2.13.0.Final
> Reporter: Michael Schwartz
>
> When creating a file with extension ".xhtml" with the following code the returned XMLResource is null. However creating the same file with extension "xml" works.
> XMLResource config = resourceFactory.create(XMLResource.class, new File(project.toString() + "/src/main/resources/" + filename));
> imho the create() method should produce an exception containing the cause of the error instead of returning null, it would simplify bugfixing.
> Furthermore the code getParent().mkdirs(); (2 occurences) in org.jboss.forge.addon.resource.AbstractFileResource may (and do) produce NullPointerExceptions.
> Is there any suggestion to get the base resource directory via code instead of hardcoding it to "project.toString() + "/src/main/resources"?
> thanks and regards from austria, Mike
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 4 months
[JBoss JIRA] (FORGE-2176) Ability set VERBOSE=true when running the commands in IDE like Intellij
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-2176?page=com.atlassian.jira.plugin... ]
George Gastaldi updated FORGE-2176:
-----------------------------------
Fix Version/s: 2.x Future
> Ability set VERBOSE=true when running the commands in IDE like Intellij
> -----------------------------------------------------------------------
>
> Key: FORGE-2176
> URL: https://issues.jboss.org/browse/FORGE-2176
> Project: Forge
> Issue Type: Feature Request
> Components: Addon Development, UI - Eclipse, UI - IntelliJ IDEA, UI - NetBeans
> Environment: IntelliJ, Eclipse
> Reporter: Jyothiprasad Buddha
> Labels: eclipse, intellij, logging, plugins
> Fix For: 2.x Future
>
>
> I'm trying to develop addons and I'm just a beginner, so I may be missing if this feature is already there. However I can't find any info about this so far in any forums or documentation.
> If I'm running a command from command line, I can set VERBOSE=true that can print information on where the failure is. But if I'm running it from ide plugin, this doesn't work and it only shows single like like NullPointerException etc., Ability to set VERBOSE=true in plugin setting dialog.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 4 months
[JBoss JIRA] (FORGE-2176) Ability set VERBOSE=true when running the commands in IDE like Intellij
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-2176?page=com.atlassian.jira.plugin... ]
George Gastaldi updated FORGE-2176:
-----------------------------------
Component/s: UI - NetBeans
> Ability set VERBOSE=true when running the commands in IDE like Intellij
> -----------------------------------------------------------------------
>
> Key: FORGE-2176
> URL: https://issues.jboss.org/browse/FORGE-2176
> Project: Forge
> Issue Type: Feature Request
> Components: Addon Development, UI - Eclipse, UI - IntelliJ IDEA, UI - NetBeans
> Environment: IntelliJ, Eclipse
> Reporter: Jyothiprasad Buddha
> Labels: eclipse, intellij, logging, plugins
>
> I'm trying to develop addons and I'm just a beginner, so I may be missing if this feature is already there. However I can't find any info about this so far in any forums or documentation.
> If I'm running a command from command line, I can set VERBOSE=true that can print information on where the failure is. But if I'm running it from ide plugin, this doesn't work and it only shows single like like NullPointerException etc., Ability to set VERBOSE=true in plugin setting dialog.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 4 months
[JBoss JIRA] (FORGE-2145) NullPointerException when trying to open in IDEA 14.0.1 with JDK 1.7.0
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-2145?page=com.atlassian.jira.plugin... ]
George Gastaldi reassigned FORGE-2145:
--------------------------------------
Assignee: Adam Wyłuda
Adam, could you take a look at this? Thanks!
> NullPointerException when trying to open in IDEA 14.0.1 with JDK 1.7.0
> ----------------------------------------------------------------------
>
> Key: FORGE-2145
> URL: https://issues.jboss.org/browse/FORGE-2145
> Project: Forge
> Issue Type: Bug
> Components: UI - IntelliJ IDEA
> Reporter: James Strachan
> Assignee: Adam Wyłuda
> Fix For: 2.x Future
>
>
> using 14.0.1 of IDEA Ultimate and JDK 1.7.0 after following these instructions
> https://intellij-support.jetbrains.com/entries/23455956-Selecting-the-JDK...
> I get this track trace below.
> I added "1.7*" to the Info.plist as described above. In IDEA -> About it says "jdk 1.7.0_60-ea-b15". No idea where that comes from.
> {code}
> $ java -version
> java version "1.7.0_55"
> Java(TM) SE Runtime Environment (build 1.7.0_55-b13)
> Java HotSpot(TM) 64-Bit Server VM (build 24.55-b03, mixed mod
> jstrachan (master):/java-workspace/hawtio/hawtio-web/$ ls -al /Library/Java/JavaVirtualMachines/
> total 32
> drwxr-xr-x 12 root wheel 408 13 Nov 15:53 .
> drwxrwxr-x 7 root admin 238 25 Oct 2013 ..
> lrwxr-xr-x 1 root wheel 20 6 Feb 2012 1.6.0.jdk -> 1.6.0_29-b11-402.jdk
> drwxr-xr-x 3 root wheel 102 1 Nov 2011 1.6.0_29-b11-402.jdk
> lrwxr-xr-x 1 root wheel 15 13 Nov 15:53 1.7.0.jdk -> jdk1.7.0_60.jdk
> drwxr-xr-x@ 4 root wheel 136 12 Jul 2012 1.8.0-lambda.jdk
> lrwxr-xr-x 1 root wheel 15 29 Apr 2014 jdk1.7.0 -> jdk1.7.0_55.jdk
> drwxr-xr-x 3 root wheel 102 29 Apr 2014 jdk1.7.0_55.jdk
> drwxr-xr-x 4 root wheel 136 13 Nov 15:53 jdk1.7.0_60.jdk
> lrwxr-xr-x 1 root wheel 15 23 Jun 08:35 jdk1.8.0 -> jdk1.8.0_05.jdk
> drwxr-xr-x 3 root wheel 102 23 Jun 08:34 jdk1.8.0_05.jdk
> {code}
> The exception is:
> {code}
> java.lang.NullPointerException
> at org.jboss.forge.plugin.idea.service.ForgeService.locateNativeClass(ForgeService.java:124)
> at org.jboss.forge.plugin.idea.context.UIContextFactory.getResourceConverter(UIContextFactory.java:76)
> at org.jboss.forge.plugin.idea.context.UIContextFactory.filesToResources(UIContextFactory.java:63)
> at org.jboss.forge.plugin.idea.context.UIContextFactory.getSelection(UIContextFactory.java:51)
> at org.jboss.forge.plugin.idea.context.UIContextFactory.create(UIContextFactory.java:36)
> at org.jboss.forge.plugin.idea.service.callbacks.CommandListPopupCallBack.run(CommandListPopupCallBack.java:37)
> at com.intellij.openapi.application.impl.LaterInvocator$FlushQueue.run(LaterInvocator.java:318)
> at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:312)
> at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:733)
> at java.awt.EventQueue.access$200(EventQueue.java:103)
> at java.awt.EventQueue$3.run(EventQueue.java:694)
> at java.awt.EventQueue$3.run(EventQueue.java:692)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.security.ProtectionDomain$1.doIntersectionPrivilege(ProtectionDomain.java:76)
> at java.awt.EventQueue.dispatchEvent(EventQueue.java:703)
> at com.intellij.ide.IdeEventQueue.e(IdeEventQueue.java:748)
> at com.intellij.ide.IdeEventQueue._dispatchEvent(IdeEventQueue.java:577)
> at com.intellij.ide.IdeEventQueue.dispatchEvent(IdeEventQueue.java:384)
> at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:242)
> at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:161)
> at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:150)
> at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:146)
> at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:138)
> at java.awt.EventDispatchThread.run(EventDispatchThread.java:91)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 4 months
[JBoss JIRA] (FORGE-2238) Adopt JBoss Logging as a defacto logging framework
by George Gastaldi (JIRA)
George Gastaldi created FORGE-2238:
--------------------------------------
Summary: Adopt JBoss Logging as a defacto logging framework
Key: FORGE-2238
URL: https://issues.jboss.org/browse/FORGE-2238
Project: Forge
Issue Type: Enhancement
Components: Furnace (Container)
Affects Versions: 2.14.0.Final
Reporter: George Gastaldi
Fix For: 2.x Future
Configuring categories is a bit unpleasant using the Java logging framework.
We should stick to a decent logging framework that should allow us to i18n our messages and standardize the error messages.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 4 months
[JBoss JIRA] (FORGE-2238) Adopt JBoss Logging as the standard logging framework
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-2238?page=com.atlassian.jira.plugin... ]
George Gastaldi updated FORGE-2238:
-----------------------------------
Summary: Adopt JBoss Logging as the standard logging framework (was: Adopt JBoss Logging as a defacto logging framework)
> Adopt JBoss Logging as the standard logging framework
> -----------------------------------------------------
>
> Key: FORGE-2238
> URL: https://issues.jboss.org/browse/FORGE-2238
> Project: Forge
> Issue Type: Enhancement
> Components: Furnace (Container)
> Affects Versions: 2.14.0.Final
> Reporter: George Gastaldi
> Fix For: 2.x Future
>
>
> Configuring categories is a bit unpleasant using the Java logging framework.
> We should stick to a decent logging framework that should allow us to i18n our messages and standardize the error messages.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 4 months
[JBoss JIRA] (FORGE-2237) Upgrade to Roaster 2.13.0.Final
by George Gastaldi (JIRA)
George Gastaldi created FORGE-2237:
--------------------------------------
Summary: Upgrade to Roaster 2.13.0.Final
Key: FORGE-2237
URL: https://issues.jboss.org/browse/FORGE-2237
Project: Forge
Issue Type: Feature Request
Components: Parsers / File Manipulation
Affects Versions: 2.14.0.Final
Reporter: George Gastaldi
Assignee: George Gastaldi
Fix For: 2.14.1.Final
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 4 months