Hey All,
As a user (and occasional contributor) I would have to agree with Jorg
that 1.5 makes more sense, in the fact that it does retain binary
compatibility. Like with Lang 3.0, I would expect that the 2.0 release
would be a major change (dropping backwards compatibility, removing
deprecated co
Will IO 2.0 be targeting Java 1.5+ (with generics, varargs, other 1.5+
goodness) like Lang 3.0 or will it be retaining backwards
compatibility?
On Wed, Aug 4, 2010 at 1:43 AM, Henri Yandell wrote:
> Great to have you involved Lorenzo.
>
> I'm happy to help out - both with a release and if you hav
+1
As a user I'm looking forward to this!
On Thu, Jul 29, 2010 at 6:36 AM, James Carman
wrote:
> +1
>
> On Thu, Jul 29, 2010 at 3:00 AM, Henri Yandell wrote:
>> I'm obviously +1. Looking for more votes.
>>
>> On Mon, Jul 26, 2010 at 12:55 PM, Oliver Heger
>> wrote:
>>> +1
>>>
>>> Oliver
>>>
>>
+1 agreed. I think that there is a usefulness in both cases Matt
mentions. May I also suggest that the interface be named EventSource
instead of EventSupport, so as to avoid confusion with the
EventListenerSupport class and better identify the class as being a
source of events.
-Michael
On Mon, J
A couple of things I noticed.
1) In the JavaDocs section of the developer guide
(http://people.apache.org/~bayard/commons-lang-3.0-beta-3/site/developerguide.html)
it states that IllegalArgumentException should always be thrown
instead of NullPointerException. However, changes for version 3.0 to
t
+1 to restricting the type.
On Mon, Jul 26, 2010 at 12:05 PM, Matt Benson wrote:
> To try and get this whole subject put to bed, is anyone opposed to
> restricting the bounds of EventListenerSupport's variable to EventListener>? It's not strictly necessary, but without the restriction,
> the
I've been talking it over with James and we've considered the option
of swapping the inheritance chain so that there is an
EventListenerSource class that extends EventListenerSupport but
includes the "source" property and documentation on how to write
subclasses as described in the AbstractEventSup
l 22, 2010 at 12:56 PM, Matt Benson wrote:
>
> On Jul 22, 2010, at 11:44 AM, Michael Wooten wrote:
>
>> All,
>>
>> Since I started this mess with LANG-580 I figured I would chime in.
>>
>> I personally believe that there is a benefit for the EventSupport
>>
All,
Since I started this mess with LANG-580 I figured I would chime in.
I personally believe that there is a benefit for the EventSupport
interface, even if it can only register one type of listener. I also
believe that AbstractEventSupport could be very useful. It basically
provides an abstract
James,
I really like your implementation of the EventListenerSupport class. I
think there is still a case for the EventSupport interface and the
AbstractEventSupport class, but your EventListenerSupport class
definitely deprecates the ReflectiveEventSupport class from LANG-580.
I have created a ne
Hey All,
Not trying to be a pain, but I would like to slip in some new
functionality before the deadline if possible. I've updated LANG-580
(https://issues.apache.org/jira/browse/LANG-580) to include a patch.
The patch adds an interface for registering events, an abstract class
for publishing even
Hey All,
I have created a JIRA entry for adding a Builder interface to the
builder package. The JIRA entry is 601
(http://issues.apache.org/jira/browse/LANG-601). The basic suggestion
is to add an interface Builder that provides a "T build()" method
to indicate that a class is capable of building
Hey All,
I added patches for IO-229, my suggestion to convert AndFileFilter and
OrFileFilter to use varargs constructors instead of two arguments ones
(https://issues.apache.org/jira/browse/IO-229), and IO-239, which was
converting IOCase to a proper enumeration
(https://issues.apache.org/jira/bro
izeOf(File) Method to FileUtils
(https://issues.apache.org/jira/browse/IO-238)
IO-239 Convert IOCase to a Java 1.5+ Enumeration
(https://issues.apache.org/jira/browse/IO-239)
Thanks.
-Michael Wooten
-
To unsubscribe, e-mail: de
ks.
-Michael
On Thu, Aug 20, 2009 at 7:27 AM, James Carman wrote:
> On Thu, Aug 20, 2009 at 8:23 AM, Michael Wooten
> wrote:
> > I was assuming I would use the fact that compareTo() returns 0 for the
> case
> > of equality. My original assumption was the test would be as simpl
On Tue, Aug 11, 2009 at 8:31 AM, James Carman wrote:
> On Tue, Aug 11, 2009 at 2:09 AM, Henri Yandell wrote:
> >> - sizeInRange(int minSize, int maxSize, String string, String message)
> >> - throws an IllegalArgumentException stating (message + value) when
> >> the length of the provi
What version of Java will IO 2.0 be targeting? As I understand it, the next
version will target Java 5 compatibility, in which case the file monitoring
functionality may be beneficial to users who will not be transitioning to
Java 7 soon. I personally think this would be great functionality and wou
an example of how these classes
could be used so that you're not constantly rewriting the code and
interfaces for adding and removing listeners, and it provides a fairly easy
method of creating methods to fire events.
So, anyone have thoughts or opinions on these proposed features?
-Michael Wooten
se see the JIRA posting at
https://issues.apache.org/jira/browse/IO-198 .
I would love feedback on either of these features.
Thank you.
-Michael Wooten
gEscape, myString);
Just ideas. It's a framework I've found useful when passing behavior around,
especially when there's a fixed set of operations or a known subset to be
supported.
Hope that's useful.
-Michael Wooten
On 6/14/09, Henri Yandell wrote:
>
> I've
new to the contribution process, so I would love any feedback.
Thanks!
-Michael Wooten
Hi.
I am very interested in contributing to the commons-lang project, but would
like to know the state of it. I've seen several posts in JIRA and in the
developer mailing list about LangTwo and moving to Java 5.0 for version 3.0.
The projects I work on for my company have either moved to Java 6.0,
22 matches
Mail list logo
