[JBoss JIRA] (ARQ-1793) arquillian-weld-ee-embedded expose wrong version of Arquillian Core
by Aslak Knutsen (JIRA)
[ https://issues.jboss.org/browse/ARQ-1793?page=com.atlassian.jira.plugin.s... ]
Aslak Knutsen updated ARQ-1793:
-------------------------------
Description: weld-bom expose an older v of Arquillian Core via weld-parent. This forces the direct dependencies of arquillian-weld-ee-embedded on Arquillian Core to downgrade to the weld-bom v while leaving the other dependencies upgraded. Result is a mixed set of Arquillian Core artifacts.
> arquillian-weld-ee-embedded expose wrong version of Arquillian Core
> -------------------------------------------------------------------
>
> Key: ARQ-1793
> URL: https://issues.jboss.org/browse/ARQ-1793
> Project: Arquillian
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Weld Containers
> Affects Versions: weld_1.0.0.CR8
> Reporter: Tomas Remes
>
> weld-bom expose an older v of Arquillian Core via weld-parent. This forces the direct dependencies of arquillian-weld-ee-embedded on Arquillian Core to downgrade to the weld-bom v while leaving the other dependencies upgraded. Result is a mixed set of Arquillian Core artifacts.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 7 months
[JBoss JIRA] (ARQ-1758) Test passes although it fails unexpectedly
by Aslak Knutsen (JIRA)
[ https://issues.jboss.org/browse/ARQ-1758?page=com.atlassian.jira.plugin.s... ]
Aslak Knutsen updated ARQ-1758:
-------------------------------
Fix Version/s: 1.1.5.Final
> Test passes although it fails unexpectedly
> ------------------------------------------
>
> Key: ARQ-1758
> URL: https://issues.jboss.org/browse/ARQ-1758
> Project: Arquillian
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Base Implementation
> Affects Versions: 1.1.4.Final
> Reporter: Robert Panzer
> Fix For: 1.1.5.Final
>
> Attachments: debug.png
>
>
> I have an erronous test class that cannot be loaded in the container due to a NoClassDefFoundError. (A dependent class is missing.)
> The test passes unexpectedly and all test methods are reported to have passed although log entries or SystemOuts show that the methods are actually never invoked.
> The problem seems to be a regression that came with the last release.
> In JUnitTestRunner the TestResults exception is overwritten with null in such a case.
> I will attach a screenshot of the debugger showing that.
> I also have a try of a patch that I will link as soon as I prepared the pull request on github.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 7 months
[JBoss JIRA] (ARQ-1796) Regression: JUnit ExpectedException is not handled correctly
by Rich DiCroce (JIRA)
Rich DiCroce created ARQ-1796:
---------------------------------
Summary: Regression: JUnit ExpectedException is not handled correctly
Key: ARQ-1796
URL: https://issues.jboss.org/browse/ARQ-1796
Project: Arquillian
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 1.1.4.Final
Reporter: Rich DiCroce
I have many tests using JUnit's ExcpectedException rule. In Arquillian 1.1.3, these tests worked perfectly. When I tried to update to 1.1.4, they broke. It seems like Arquillian now catches the exceptions before ExpectedException does, and propagates them back to the client.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 7 months