[Design the new POJO MicroContainer] - Re: aop-mc-int tests with maven
by kabir.khan@jboss.com
"kabir.khan(a)jboss.com" wrote : "kabir.khan(a)jboss.com" wrote :
| | In addition to the things I mentioned above, one thing that makes the console output impossible to read is that all the log messages/System.out.println()s from the tests appear in the console. With ant, the junit task would redirect these to to only appear in the log file. What maven-fu is needed to do that?
|
| Adding
|
| | <redirectTestOutputToFile>true</redirectTestOutputToFile>
| | </configuration>
| | </execution>
| |
| to the pom helps. It has the problem though of (over)writing all tests for all modes to the surefire-reports directory, similarly to what I mentioned for the test log files. "reportsDirectory" could maybe be used to split where the tests run with different weaving/security settings. Paul, how would that work with the report plugin?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4040013#4040013
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4040013
18 years, 11 months
[Design of OSGi Integration] - OSGi Bundle Repository
by scott.stark@jboss.org
I have gone over the OSGi bundle repository (OBR) draft:
http://www2.osgi.org/div/rfc-0112_BundleRepository.pdf
as input into what the profile service spi needs to be for managing the deployment content. Its a short, easy read.
The OBR is a read-only view of bundles that primarily focuses on a federated repository for resolving bundle dependencies. The main notions is a collection of resources (a generalization of a bundle), and resources have requirements (an ldap type of filter on resource properties and/or capabilities) and capabilities (a named collection of properties). Version is a first class notion in that its a required resource property. There is an xml schema for describing the contents of a repository, and federation of repositories relies on this in terms of linking repositories together.
The two initial tasks are to:
1. Revise the current profile service repository spi to support the OBR requirements. I'm working on this as part of JBAS-4362.
2. Define how the OBR integrates with the current OSGi mc integration work. It would seem that this is simply an injection of a org.osgi.servicex.obr.Resolver implementation for use by the dependency layer. The main point of this thread is to discuss how we do that.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4040005#4040005
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4040005
18 years, 11 months