Restoring ability to use webdav wagon by fixing WagonManager's use of new active collections in the container, and fixing the active collections to scan descendant realms for qualifying components.

git-svn-id: https://svn.apache.org/repos/asf/maven/components/trunk@588777 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
John Dennis Casey 2007-10-26 20:57:39 +00:00
parent bcb1ebe0e0
commit 4f44eaddf3
2 changed files with 15 additions and 15 deletions

View File

@ -148,19 +148,19 @@ public class DefaultLifecycleExecutor
rootProject );
// FIXME: This should be handled by the extension scanner.
try
{
Map handlers = findArtifactTypeHandlers( session );
artifactHandlerManager.addHandlers( handlers );
}
catch ( PluginNotFoundException e )
{
throw new LifecycleExecutionException(
"Plugin could not be not found while searching for artifact-type handlers.",
rootProject,
e );
}
// try
// {
// Map handlers = findArtifactTypeHandlers( session );
//
// artifactHandlerManager.addHandlers( handlers );
// }
// catch ( PluginNotFoundException e )
// {
// throw new LifecycleExecutionException(
// "Plugin could not be not found while searching for artifact-type handlers.",
// rootProject,
// e );
// }
executeTaskSegments(
taskSegments,

View File

@ -470,12 +470,12 @@ public class MavenEmbedder
MavenProject project = readProject( request.getPom() );
Map handlers = findArtifactTypeHandlers( project );
// Map handlers = findArtifactTypeHandlers( project );
//TODO: ok this is crappy, now there are active collections so when new artifact handlers
// enter the system they should be available.
artifactHandlerManager.addHandlers( handlers );
// artifactHandlerManager.addHandlers( handlers );
}
catch ( MavenEmbedderException e )
{