dion2002/12/08 00:11:36
Modified:latkaproject.xml
Log:
Fix maven build so that resources are found
Revision ChangesPath
1.35 +13 -4 jakarta-commons/latka/project.xml
Index: project.xml
dion2002/12/08 00:13:30
Removed: latka/src/jelly latka.jelly
Log:
Remove old jelly file
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
dion2002/12/08 00:52:10
Modified:latkaproject.xml
Log:
Change id to match other deployed commons projects
Revision ChangesPath
1.36 +1 -1 jakarta-commons/latka/project.xml
Index: project.xml
dion2002/12/08 04:58:38
Modified:latka/src/java/org/apache/commons/latka LatkaProperties.java
Log:
There may not be a context class loader
Revision ChangesPath
1.14 +4 -0
jakarta-commons/latka/src/java/org/apache/commons/latka/LatkaProperties.java
This email is autogenerated from the output from:
http://cvs.apache.org/builds/gump/2002-12-08/commons-httpclient.html
Buildfile: build.xml
init:
[echo] HttpClient Library
This email is autogenerated from the output from:
http://cvs.apache.org/builds/gump/2002-12-08/commons-io.html
Buildfile: build.xml
init:
[echo] io 20021208
prepare
This email is autogenerated from the output from:
http://cvs.apache.org/builds/gump/2002-12-08/commons-email.html
Buildfile: build-gump.xml
jar:
[mkdir] Created dir:
dion2002/12/08 05:37:56
Modified:latka/src/java/org/apache/commons/latka Latka.java
Log:
Allow for no context class loader
Revision ChangesPath
1.40 +5 -1
jakarta-commons/latka/src/java/org/apache/commons/latka/Latka.java
Index: Latka.java
I've taken a look at the code, and there are a lot of useful facilities. As
you may have noticed from the list however, the current position with these
classes is confused. I am going to try to get the position sorted and then
your submission can be properly considered. (I basically want to avoid
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15160.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15160.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
I've added the beginnings of a Latka plugin to Maven.
See http://jakarta.apache.org/turbine/maven/reference/plugins/latka/ for
the home page.
Currently all the plugin does is execute any scripts found in
${maven.latka.src.dir} which defaults to src/test/latka that have the file
suffix .latka.
On a number of occasions we have received requests for implementations of
the Functors (Predicate, Transformer, Closure and Factory). These
implementations now exist in [lang], however they implement the [lang]
version of the interfaces, not the [collections] version. This problem must
be solved.
scolebourne2002/12/08 07:29:26
Modified:collections/src/test/org/apache/commons/collections
TestCollectionUtils.java
Log:
Test the new countMatches method
Revision ChangesPath
1.10 +19 -4
scolebourne2002/12/08 07:29:59
Modified:collections/src/java/org/apache/commons/collections
CollectionUtils.java
Log:
Add new countMatches method
Revision ChangesPath
1.22 +23 -4
scolebourne2002/12/08 07:30:58
Modified:collections/src/java/org/apache/commons/collections
package.html
Log:
Update to latest package status
Revision ChangesPath
1.8 +121 -120
scolebourne2002/12/08 07:42:35
Modified:collections/src/test/org/apache/commons/collections
TestIteratorUtils.java
collections/src/java/org/apache/commons/collections
IteratorUtils.java
Log:
Add IteratorUtils
Patch applied, thanks.
Stephen
- Original Message -
From: Rich Dougherty [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, December 06, 2002 1:29 AM
Subject: [Collections] [SUBMIT] Unmodifiable iterators
Hi
This patch adds two methods to IteratorUtils which return unmodifiable
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9422.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15128.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
scolebourne2002/12/08 08:06:30
Modified:lang default.properties
Log:
Remove Hen's personal settings (!)
Revision ChangesPath
1.9 +0 -1 jakarta-commons/lang/default.properties
Index: default.properties
scolebourne2002/12/08 08:18:39
Modified:lang/src/java/org/apache/commons/lang SystemUtils.java
Log:
Keep javadoc generation happy
Revision ChangesPath
1.6 +74 -65
jakarta-commons/lang/src/java/org/apache/commons/lang/SystemUtils.java
Index:
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15154.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Dmitri,
I tried to check in these patches, but the tests didn't produce the wrapped
effect on my box. (Windows Sun JDK1.4.0. If you like, you can check them in
yourself.
Stephen
- Original Message -
From: Dmitri Plotnikov [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, November 08,
jsdever 2002/12/08 10:51:07
Modified:httpclient/src/java/org/apache/commons/httpclient
HttpMethodBase.java
Removed: httpclient/src/java/org/apache/commons/httpclient/cookie
HttpMethodBase.java
Log:
Fix a patch problem with
scolebourne2002/12/08 12:45:08
Modified:lang/src/java/org/apache/commons/lang/builder
ToStringBuilder.java ToStringStyle.java
StandardToStringStyle.java
Log:
Add ability to build compound toStrings using superclass and delegates
scolebourne2002/12/08 12:48:46
Modified:lang/src/test/org/apache/commons/lang/builder
StandardToStringStyleTest.java
MultiLineToStringStyleTest.java
ToStringBuilderTest.java
On Sun, 8 Dec 2002, Stephen Colebourne wrote:
Solution #3
[functor] project, that contains the functor interfaces, implementations and
CollectionUtils implementations, with the collections interfaces and
CollectionUtils code deprecated in favour of the functor ones.
In this scenario, why
scolebourne2002/12/08 13:10:11
Modified:lang/src/test/org/apache/commons/lang/builder
EqualsBuilderTest.java
Log:
Add ability to build compound equals using superclass
Revision ChangesPath
1.2 +10 -1
scolebourne2002/12/08 13:10:42
Modified:lang/src/java/org/apache/commons/lang/builder
EqualsBuilder.java
Log:
Add ability to build compound equals using superclass
Revision ChangesPath
1.7 +18 -1
scolebourne2002/12/08 13:22:07
Modified:lang/src/java/org/apache/commons/lang/builder
HashCodeBuilder.java
Log:
Add ability to build compound hashCode using superclass
Revision ChangesPath
1.6 +17 -2
Rich:
This change makes this class unable to deserialize prior serialized forms of
this class. I'm not a committer, but I'd like to suggest that such a change
be voted on prior to inclusion. In order to retain the ability to
deserialize prior versions, readObject must issue a readInt call (to
Variables should automatically be available to their child
contexts so I
don't think you need to create your own JellyContext for that.
What I meant to say was that a variable _value_ should be visible only in a certain
scope. So there is a stack of values per variable.
Also the push/pop
This change makes this class unable to deserialize prior serialized
forms of this class. I'm not a committer, but I'd like to suggest that
such a change be voted on prior to inclusion. In order to retain the
ability to
deserialize prior versions, readObject must issue a readInt call (to
From: Mark R. Diggory [EMAIL PROTECTED]
Ohhh, I got it, I was trying to run ant and not maven. I thought maven
was getting started by ant. The build.xml script in the jelly directory
seems to have problems. If ant is no longer used to build Jelly,
wouldn't it be good to get rid of the
What I meant to say was that a variable _value_ should be visible only in
a certain
scope. So there is a stack of values per variable.
You could create a number of different contexts each of which can contain
different values of a given variable name. e.g.
j:set var=foo value=1/
j:scope
36 matches
Mail list logo