You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ivy-commits@incubator.apache.org by "Matt Inger (JIRA)" <ji...@apache.org> on 2007/10/17 11:34:51 UTC
[jira] Created: (IVY-623) Ability to automatically recognize new
resolvers, latest strategies, etc...
Ability to automatically recognize new resolvers, latest strategies, etc...
---------------------------------------------------------------------------
Key: IVY-623
URL: https://issues.apache.org/jira/browse/IVY-623
Project: Ivy
Issue Type: Improvement
Components: Core
Affects Versions: 2.0.0-alpha-2
Reporter: Matt Inger
What i'd like to see though is for the ivy engine to use more pluggable
configuration elements, rather than forcing a <typedef>.
For example, one could create a jar file with the resolver classes
and a jar entry:
META-INF/ivy-typedefs.properties
--------------------------------------------
svn=org.myorg.ivy.resolver.SvnResolver
and have ivy load this resource at startup time, and make all the typedefs
available. Then, including additional resolvers and latest/conflict
resolution strategies would be simply a matter of dropping in the .jar file
containing the class (and of course, any supporting jar files).
An alternative to the .properties would be an .xml file, though the simplicity
of a properties file might be enough, as i'm not sure offhand whether or not
typedef's can have subelements for things like parameters.
This would also need to be supported in IvyDE.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.