You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by js...@apache.org on 2002/08/19 11:34:31 UTC
cvs commit: jakarta-commons-sandbox/jelly/xdocs todo.xml
jstrachan 2002/08/19 02:34:31
Modified: jelly/xdocs todo.xml
Log:
tidied up the to do list to describe the need for a Maven / JJAR style local/remote repository to download new libraries on the fly, along with their dependencies.
Revision Changes Path
1.21 +4 -3 jakarta-commons-sandbox/jelly/xdocs/todo.xml
Index: todo.xml
===================================================================
RCS file: /home/cvs/jakarta-commons-sandbox/jelly/xdocs/todo.xml,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -r1.20 -r1.21
--- todo.xml 31 Jul 2002 11:48:09 -0000 1.20
+++ todo.xml 19 Aug 2002 09:34:31 -0000 1.21
@@ -20,9 +20,10 @@
in a similar way to how the commons-discovery and JAXP libraries work.
This would allow Jelly libraries to be distributed in a self contained JAR then just put
on the classpath and they'd be usable.
- One day it might be interesting to add some funky classloader thing like JJAR/Maven
- so that using a new jelly library via a URL would automatically download the jar from some
- local/remote repository.
+ </li>
+ <li>
+ Implement a JJAR/Maven mechanism so that using a new Jelly library via a namespace URI would
+ automatically download the jar and its dependencies from some local/remote repository.
</li>
<li>Maybe add a Scope class to make it easier to plugin custom scopes such as
request, session, applicaiton, initParams, params, transation etc.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>