[JBoss JIRA] (FORGE-1968) Misleading exception message when CDI dependency is not found
by Ondrej Zizka (JIRA)
Ondrej Zizka created FORGE-1968:
-----------------------------------
Summary: Misleading exception message when CDI dependency is not found
Key: FORGE-1968
URL: https://issues.jboss.org/browse/FORGE-1968
Project: Forge
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Test Harness
Reporter: Ondrej Zizka
If a test contains unsatisfied CDI depdenency, Forge should pass that information from CDI. Instead, it tells that the test class was not found. See the stacktrace below.
{code:java}
RunWith(Arquillian.class)
public class FooTest
{
@Deployment
@Dependencies({
@AddonDependency(name = "org.jboss.forge.furnace.container:cdi")
})
public static ForgeArchive getDeployment()
{
ForgeArchive archive = ShrinkWrap.create(ForgeArchive.class)
.addBeansXML()
.addClass(FooTest.class)
.addAsAddonDependencies(
AddonDependencyEntry.create("org.jboss.forge.furnace.container:cdi")
);
return archive;
}
@Inject
private UnsatisfiedClass foo;
@Test
public void testFrameToJaxb() throws Exception
{ ... }
{code}
When the inject is removed, it runs fine.
java.lang.IllegalStateException: Test runner could not locate test class [org.jboss.windup.reporting.xslt.jaxb.FrameToJaxbTest] in any deployed Addon.
at org.jboss.forge.arquillian.ForgeTestMethodExecutor.invoke(ForgeTestMethodExecutor.java:222)
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.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.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.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:266)
at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:229)
at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:317)
at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:46)
at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:243)
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:188)
at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:317)
at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:46)
at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:202)
at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:150)
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)
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 5 months
[JBoss JIRA] (FORGE-1968) Misleading exception message when CDI dependency is not found
by Ondrej Zizka (JIRA)
[ https://issues.jboss.org/browse/FORGE-1968?page=com.atlassian.jira.plugin... ]
Ondrej Zizka updated FORGE-1968:
--------------------------------
Affects Version/s: 2.7.2.Final
> Misleading exception message when CDI dependency is not found
> -------------------------------------------------------------
>
> Key: FORGE-1968
> URL: https://issues.jboss.org/browse/FORGE-1968
> Project: Forge
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Test Harness
> Affects Versions: 2.7.2.Final
> Reporter: Ondrej Zizka
>
> If a test contains unsatisfied CDI depdenency, Forge should pass that information from CDI. Instead, it tells that the test class was not found. See the stacktrace below.
> {code:java}
> RunWith(Arquillian.class)
> public class FooTest
> {
> @Deployment
> @Dependencies({
> @AddonDependency(name = "org.jboss.forge.furnace.container:cdi")
> })
> public static ForgeArchive getDeployment()
> {
> ForgeArchive archive = ShrinkWrap.create(ForgeArchive.class)
> .addBeansXML()
> .addClass(FooTest.class)
> .addAsAddonDependencies(
> AddonDependencyEntry.create("org.jboss.forge.furnace.container:cdi")
> );
> return archive;
> }
>
> @Inject
> private UnsatisfiedClass foo;
> @Test
> public void testFrameToJaxb() throws Exception
> { ... }
> {code}
> When the inject is removed, it runs fine.
> java.lang.IllegalStateException: Test runner could not locate test class [org.jboss.windup.reporting.xslt.jaxb.FrameToJaxbTest] in any deployed Addon.
> at org.jboss.forge.arquillian.ForgeTestMethodExecutor.invoke(ForgeTestMethodExecutor.java:222)
> 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.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.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.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:266)
> at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:229)
> at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:317)
> at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:46)
> at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:243)
> 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:188)
> at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:317)
> at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:46)
> at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:202)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
> at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:150)
> 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)
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 5 months
[JBoss JIRA] (FORGE-1966) The text addon tests fail on Windows
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-1966?page=com.atlassian.jira.plugin... ]
George Gastaldi updated FORGE-1966:
-----------------------------------
Fix Version/s: 2.x Future
> The text addon tests fail on Windows
> ------------------------------------
>
> Key: FORGE-1966
> URL: https://issues.jboss.org/browse/FORGE-1966
> Project: Forge
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Text
> Affects Versions: 2.7.3.Final
> Environment: Windows
> Reporter: Ivan St. Ivanov
> Assignee: Ivan St. Ivanov
> Fix For: 2.x Future
>
>
> When the text addon tests are run on windows, some of them (those for YAML, Groovy, JavaScript and HTML) fail. The reason for that is that the patterns for some of the language elements contain the new line characted (\n), while on Windows this is not enough - you also need carriage return (\r).
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 5 months
[JBoss JIRA] (FORGE-1966) The text addon tests fail on Windows
by Ivan St. Ivanov (JIRA)
[ https://issues.jboss.org/browse/FORGE-1966?page=com.atlassian.jira.plugin... ]
Ivan St. Ivanov reassigned FORGE-1966:
--------------------------------------
Assignee: Ivan St. Ivanov
> The text addon tests fail on Windows
> ------------------------------------
>
> Key: FORGE-1966
> URL: https://issues.jboss.org/browse/FORGE-1966
> Project: Forge
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Text
> Affects Versions: 2.7.3.Final
> Environment: Windows
> Reporter: Ivan St. Ivanov
> Assignee: Ivan St. Ivanov
>
> When the text addon tests are run on windows, some of them (those for YAML, Groovy, JavaScript and HTML) fail. The reason for that is that the patterns for some of the language elements contain the new line characted (\n), while on Windows this is not enough - you also need carriage return (\r).
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 5 months
[JBoss JIRA] (FORGE-1966) The text addon tests fail on Windows
by Ivan St. Ivanov (JIRA)
Ivan St. Ivanov created FORGE-1966:
--------------------------------------
Summary: The text addon tests fail on Windows
Key: FORGE-1966
URL: https://issues.jboss.org/browse/FORGE-1966
Project: Forge
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Text
Affects Versions: 2.7.3.Final
Environment: Windows
Reporter: Ivan St. Ivanov
When the text addon tests are run on windows, some of them (those for YAML, Groovy, JavaScript and HTML) fail. The reason for that is that the patterns for some of the language elements contain the new line characted (\n), while on Windows this is not enough - you also need carriage return (\r).
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 5 months
[JBoss JIRA] (FORGE-1964) "Visible for all classloaders" addon option
by Ondrej Zizka (JIRA)
[ https://issues.jboss.org/browse/FORGE-1964?page=com.atlassian.jira.plugin... ]
Ondrej Zizka updated FORGE-1964:
--------------------------------
Labels: logging (was: )
> "Visible for all classloaders" addon option
> -------------------------------------------
>
> Key: FORGE-1964
> URL: https://issues.jboss.org/browse/FORGE-1964
> Project: Forge
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Dependencies
> Affects Versions: 2.7.2.Final
> Reporter: Ondrej Zizka
> Labels: logging
>
> An option to allow an addon's content (classes + resources) to be visible for all other addons is needed.
> Some frameworks are not prepared for modularized environment, and working with them then is a hell. For example, logging frameworks, which initialize pretty much randomly, under undefined conditions through unknown classloaders, hence, adding a logging addon to specific addons doesn't help - one needs to add it to all modules. Which kind of defeats the purpose of modularity.
> Having this option would save a lot of depdendency maintainance effort.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 5 months
[JBoss JIRA] (FORGE-273) Create project from Maven archetype
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-273?page=com.atlassian.jira.plugin.... ]
George Gastaldi updated FORGE-273:
----------------------------------
Status: Pull Request Sent (was: Coding In Progress)
Git Pull Request: https://github.com/forge/core/pull/493
> Create project from Maven archetype
> -----------------------------------
>
> Key: FORGE-273
> URL: https://issues.jboss.org/browse/FORGE-273
> Project: Forge
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Blessed Plugins
> Reporter: Dan Allen
> Assignee: George Gastaldi
> Priority: Critical
> Fix For: 2.x Future
>
>
> Since the catalog of Maven archetypes is substantial, and the archetype plugin interface is so abysmal, Forge could benefit from being a stand-in replacement to archetype:generate. A command in Forge to create a new project from a Maven archetype would certainly offer a nice complement to the more basic "new-project" command. It could just be an additional flag to the new-project command, such as:
> new-project --named MyProject --fromArchetype org.jboss.weld.archetypes:jboss-javaee6-webapp
> Using the interactive prompts, you may be able to provide a list of archetypes, perhaps w/ a filtering mechanism. You could also just do a best guess based on what's found in the catalog.
> new-project --named MyProject --fromArchetype jboss-javaee6-webapp
> You could just delegate to Maven by building up the "mvn archetype:generate" command from Forge. Long term we could consider emulating the archetype:generate plugin so as just to consume the projects that are out there already w/o any linkage to Maven.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 5 months