JBoss development,
A new message was posted in the thread "Pluggable dependency resolver":
http://community.jboss.org/message/522036#522036
Author : Kabir Khan
Profile :
http://community.jboss.org/people/kabir.khan@jboss.com
Message:
--------------------------------------------------------------
I've further extracted how the on demand dependencies are handled in the legacy and
new model, which brings the total errors in KernelAllTestSuite down to 10. These are in:
* ScopingAliasTestCase
* ScopingAliasAPITestCase
* ScopingOverrideTestCase
* ScopingDependencyTestCase
By the way, if anybody wants to try this out, you switch the dependency resolvers in
https://svn.jboss.org/repos/jbossas/projects/kernel/branches/resolver/dep....
Currently it looks like this:
public class DependencyResolverAbstractFactory
{
private static final DependencyResolverAbstractFactory INSTANCE = new
DependencyResolverAbstractFactory();
private static final DependencyResolverFactory factory;
static
{
//TODO configure with system properties
// String name =
"org.jboss.dependency.plugins.resolver.standard.StandardDependencyResolverFactory";
//1
// String name =
"org.jboss.dependency.plugins.resolver.indexing.IndexingDependencyResolverFactory";
//2
String name =
"org.jboss.kernel.plugins.resolver.indexing.IndexingKernelDependencyResolverFactory";
//3
* 1 is the legacy resolver and all tests pass with that
* 2 is the new resolver used for the dependency project
* 3 is the new resolver used for the kernel project
--------------------------------------------------------------
To reply to this message visit the message page:
http://community.jboss.org/message/522036#522036