[
https://issues.apache.org/jira/browse/BROOKLYN-183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15030126#comment-15030126
]
ASF GitHub Bot commented on BROOKLYN-183:
-----------------------------------------
GitHub user CMoH opened a pull request:
https://github.com/apache/incubator-brooklyn/pull/1075
[BROOKLYN-183] Fix brooklyn-itest
Unfortunately pax-exam-testng is not yet usable. We decided to switch to
the junit runner until this gets resolved upstream (see
https://ops4j1.jira.com/browse/PAXEXAM-698)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/CMoH/incubator-brooklyn itest
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-brooklyn/pull/1075.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1075
----
commit 9b2960fec7139db249fe076da809452bfc647ccf
Author: Łukasz Dywicki <[email protected]>
Date: 2015-11-09T16:48:05Z
Fix failing integration tests.
commit 61669cf3c19d7d0513680a8fbbe2612f52284440
Author: Ciprian Ciubotariu <[email protected]>
Date: 2015-11-27T17:13:08Z
Merge remote-tracking branch 'splatch/itests' into itest
commit 7ed6ac165f92bc7bc8142192cc2e3866442a0e53
Author: Ciprian Ciubotariu <[email protected]>
Date: 2015-11-27T17:55:17Z
[BROOKLYN-183] Move to pax-exam-4.6.0
commit 69d62c746529e38fdd88b924022200f4122685f9
Author: Ciprian Ciubotariu <[email protected]>
Date: 2015-11-27T18:00:36Z
[BROOKLYN-183] Use junit4 in brooklyn-itest
pax-exam-4.6.0 is not properly tested with test-ng, leading to obscure
behavior
----
> Create a Karaf runtime for Brooklyn
> -----------------------------------
>
> Key: BROOKLYN-183
> URL: https://issues.apache.org/jira/browse/BROOKLYN-183
> Project: Brooklyn
> Issue Type: Improvement
> Affects Versions: 0.8.0
> Reporter: Hadrian Zbarcea
> Assignee: Ciprian Ciubotariu
> Fix For: 0.9.0
>
>
> Apache Karaf defines a lot of features out of the box, from security to
> logging that Brooklyn should use. Using an OSGi container (as opposed to the
> bare framework) allows us to better modularize Brooklyn focus on OSGi
> services and delegate commodity concerns to the container.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
