public <T> T parseStandardScriptInstance( final StandardScriptType scriptType, final String name,
                                              final Class<T> type )
            throws IndyGroovyException {
    """
	Provide a standard set of places to store common types of scripts used throughout Indy, such as
	{@link org.commonjava.indy.model.core.ArtifactStore} creators. This is better from a config maintenance
	perspective than having these spread out across the whole data/ subdirectory structure, particularly since it's
	likely if one script needs to be revised, they all will.
	
	If the script doesn't exist in the data/scripts directory structure, this method will search the classpath
	for the same path (scripts/[type]/[name]).
    """
        return parseStandardScriptInstance( scriptType, name, type, false );
    }
public <T> T parseStandardScriptInstance( final StandardScriptType scriptType, final String name,
                                              final Class<T> type )
            throws IndyGroovyException
    {
        return parseStandardScriptInstance( scriptType, name, type, false );
    }
public < T > T parseStandardScriptInstance ( final StandardScriptType scriptType , final String name , final Class < T > type ) throws IndyGroovyException { return parseStandardScriptInstance ( scriptType , name , type , false ) ; }
Provide a standard set of places to store common types of scripts used throughout Indy, such as
{@link org.commonjava.indy.model.core.ArtifactStore} creators. This is better from a config maintenance
perspective than having these spread out across the whole data/ subdirectory structure, particularly since it's
likely if one script needs to be revised, they all will.

If the script doesn't exist in the data/scripts directory structure, this method will search the classpath
for the same path (scripts/[type]/[name]).
Provide a standard set of places to store common types of scripts used throughout Indy such as { @link org . commonjava . indy . model . core . ArtifactStore } creators . This is better from a config maintenance perspective than having these spread out across the whole data / subdirectory structure particularly since it s likely if one script needs to be revised they all will .