scolebourne2002/12/25 14:03:00
Modified:lang/src/java/org/apache/commons/lang/reflect
ReflectionUtils.java MethodUtils.java
Log:
Remove unused imports
Revision ChangesPath
1.6 +2 -6
scolebourne2002/12/25 14:16:05
Modified:io/src/test/org/apache/commons/io/filefilter
FileFilterTestCase.java
Log:
Make the test compile against the current code
Revision ChangesPath
1.3 +4 -4
scolebourne2002/12/25 14:16:36
Added: io/src/test/org/apache/commons/io FileUtilsTestCase.java
Removed: io/src/test/org/apache/commons/io FileUtilTestCase.java
Log:
Rename test case to match renamed code
Revision ChangesPath
1.1
scolebourne2002/12/25 14:17:28
Modified:io STATUS.html
Log:
Add myself as a committer
Document [lang] dependency
Revision ChangesPath
1.7 +17 -10jakarta-commons-sandbox/io/STATUS.html
Index: STATUS.html
Hey everybody,
I think Jelly might be far enough along now for us to
prepare some beta releases. I propose that we focus
on stabilizing the API and work out the remaining
issues. I also volunteer to be release manager for
1.0. Any objections?
Assuming that everyone is comfortable with
The last time this came up, we got a lot of +1's to move
it from the sandbox, but then arguments were made to actually
move jelly not just to the commons proper but to a bonafide
top-level project.
Though, that'd mean changing the packaging also from
org.apache.commons.jelly.* to
://jakarta.apache.org/commons/betwixt/old.20021225/
just in case something didn't go right.
Hen
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Actually, Jelly has already been voted into the
Commons Proper:
http://marc.theaimsgroup.com/?t=10391841051r=1w=2
I don't recall any recent proposal to make it a
top-level project, and this vote was called only a few
weeks ago. Now it's a question of whether or not to
begin the process
