smor
Mon, 17 Mar 2003 14:40:11 -0800
smor 2003/03/17 14:41:11
Modified: xdocs roadmap.xml
Log:
minor typos.
Great doc, btw!
Revision Changes Path
1.8 +2 -2 jakarta-turbine-maven/xdocs/roadmap.xml
Index: roadmap.xml
===================================================================
RCS file: /home/cvs/jakarta-turbine-maven/xdocs/roadmap.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- roadmap.xml 17 Mar 2003 05:33:06 -0000 1.7
+++ roadmap.xml 17 Mar 2003 22:41:11 -0000 1.8
@@ -82,7 +82,7 @@
libraries to deal with the downloading of dependencies. I feel that
Maven still leads the way in this effort by dealing not only with JAR
dependencies but any project artifact that can be a dependency. This
- code should be separately into a simple set of beans. From there we
+ code should be separated into a simple set of beans. From there we
can wrap it in component logic for use inside Maven and others can
use the code as they wish. One of our mandates now is to encourage
other projects to be involved in Maven and this is probably the
@@ -178,7 +178,7 @@
extension. I don't want to change anything about the way Jelly
plugins work. They should just continue to work they always have but
I would like to add a pure Java API so I can write plugins purely in
- Java with no Jelly interaction. So people could easily created their
+ Java with no Jelly interaction. So people could easily create their
own plugin mechanisms for their own scripting languages or BSF for
example. I'm not overly fond of BSF but I think something like BSF
would make for a better plugin mechanism than Jelly.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]