[jboss-jira] [JBoss JIRA] (DROOLS-194) Add support in KIE to register custom Wagons

[Kurt Stam (JIRA)]

     [ https://issues.jboss.org/browse/DROOLS-194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kurt Stam updated DROOLS-194:
-----------------------------

    Attachment: kie-srampwagon.tgz


Import the project into eclipse - go into the dtgov-workflows module
and run the KieTest. 

If you have a breakpoint set in the Aether class; it will stop and say the hint = "files".

so you return 'null' at the moment. 

it gets "files' from the protocol defined in the url:

ArtifactRepository srampRepo = artifactRepoFactory.createArtifactRepository("central",  //$NON-NLS-1$
    			"files:/tmp/srampRepo",
                
> Add support in KIE to register custom Wagons
> --------------------------------------------
>
>                 Key: DROOLS-194
>                 URL: https://issues.jboss.org/browse/DROOLS-194
>             Project: Drools
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Kurt Stam
>            Assignee: Mark Proctor
>         Attachments: kie-srampwagon.tgz
>
>
> The ManualWagonProvider subclass of Aether in KIE registers the HTTPWagon. It should be possible to add your own Wagon through config our automated machinery when another Wagon is put on the classpath and references in the build/extensions of a MavenProject. To get the SrampWagon to work we used the following code:
> {quote}
> private static class ManualWagonProvider implements WagonProvider {
>         public Wagon lookup( String roleHint ) throws Exception {
>             if ( "http".equals( roleHint ) ) {
>                 return new AhcWagon();
>             }
>             if ( "sramp".equals( roleHint ) ) {
>                 return new SrampWagon();
>             }
>             return null;
>         }
>         public void release( Wagon wagon ) { }
>     }
> {quote}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira