I guess your +1 does not apply to the vote. :-)
And to be honest, javax.script is implemented by org.apache.bsf 3.1 which
runs on Java 1.5...
Nevertheless, the fair point that has been made by Matt later in this thread
is that Commons is a do-ocracy; if someone badly needs a component in Java
1.5,
On 6 December 2011 15:38, Siegfried Goeschl wrote:
> Hi Gary,
>
> ad RAT - I added a license header for "mime.types" but doing this for the
> mail messages is not possible AFAIK since there is no such thing as a
> comment for mail messages
>
> ad src zip - need to check since I did a last minute u
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-jexl-jexl-compat has an issue affecting its community
integration
It's a matter or balance, if you just want to have fun you can build a
component based on OpenJDK 8 with lots of lambda, but nobody will use it
today. And I doubt it will attract new contributors.
If avoiding trivial things like String.isEmpty() can widen the audience,
and thus the potential c
I respect your point of view but it is really hard to attract new
contributors when we first state they MUST code with JDK 1.5.
And again, if the need for a Java 1.5 backport is proven - rather than
imposed by default - , it's always possible to people interested in it to
contribute (and/or ask). P
On 5 December 2011 22:45, Jörg Schaible wrote:
> Hi Gary,
>
> Gary Gregory wrote:
>
>> Hi All:
>>
>> I've made several improvements to VFS over the last couple of months which
>> feels ready for a release soon.
>>
>> One important internal change is that the builds runs almost all unit
>> tests
>>
The Commons Codec team is pleased to announce the commons-codec-1.6 release!
The codec package contains simple encoder and decoders for
various formats such as Base64 and Hexadecimal. In addition to these
widely used encoders and decoders, the codec package also maintains a
collection of phonetic
On Wed, Dec 7, 2011 at 11:46 AM, henrib wrote:
> I respect your point of view but it is really hard to attract new
> contributors when we first state they MUST code with JDK 1.5.
> And again, if the need for a Java 1.5 backport is proven - rather than
> imposed by default - , it's always possible
I am thinking of a different package name, not just version for VFS on Java
7 because we might want to release more VFS2-based versions that do break
binary compatibility.
We can retain the VFS name and brand for the project, but I'd prefer
o.a.c.vfs to be for VFS2 based work and to create o.a.c.f
I'm much less concerned with the package name than I am that it appear to be
part of the VFS subproject. By necessity, it won't be binary compatible - and
presumably users won't interact with the commons vfs code directly anyway.
Ralph
On Dec 7, 2011, at 10:01 AM, Gary Gregory wrote:
> I am t
Hi all guys,
I consider there are no objections, I'll fill an issue and start working on it.
-Simo
http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://www.99soft.org/
On Tue, Dec 6, 2011 at 1:21 PM, Simone Tripodi wrote:
> Hi a
On 7 December 2011 16:10, sebb wrote:
> On 6 December 2011 15:38, Siegfried Goeschl wrote:
>> Hi Gary,
>>
>> ad RAT - I added a license header for "mime.types" but doing this for the
>> mail messages is not possible AFAIK since there is no such thing as a
>> comment for mail messages
Did you try
On 7 December 2011 21:07, Ralph Goers top-posted:
> I'm much less concerned with the package name than I am that it appear to be
> part of the VFS subproject. By necessity, it won't be binary compatible -
> and presumably users won't interact with the commons vfs code directly anyway.
Package
On 6 December 2011 12:21, Simone Tripodi wrote:
> Hi all guys,
> to complete DIGESTER-153 we had to include CGLIB as new dependency,
> actually I would like to experiment distributing an *additional*
> artifact (jar) where dependencies are shaded - maybe also renamed for
> internal use only.
> Not
The copy of cglib source I have locally includes an AL2.
Matt
On Wed, Dec 7, 2011 at 5:35 PM, sebb wrote:
> On 6 December 2011 12:21, Simone Tripodi wrote:
>> Hi all guys,
>> to complete DIGESTER-153 we had to include CGLIB as new dependency,
>> actually I would like to experiment distributing
How about creating a new package that has adapters for java7?
o.a.c.vfs3.nio
On Dec 7, 2011 6:32 PM, "sebb" wrote:
> On 7 December 2011 21:07, Ralph Goers
> top-posted:
> > I'm much less concerned with the package name than I am that it appear
> to be part of the VFS subproject. By necessity,
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-exec-test has an issue affecting its community integration.
This i
On Tue, Dec 6, 2011 at 9:56 PM, Henri Yandell wrote:
> On Sun, Dec 4, 2011 at 9:28 AM, sebb wrote:
>> On 4 December 2011 17:13, William Speirs wrote:
>>> What is the "rule" on when you can switch Java versions? Is going from
>>
>> http://commons.apache.org/releases/versioning.html
>>
>>> 1.4 to
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-proxy-test has an issue affecting its community integration.
This
That might be a reasonable approach, but it will depend on what changes might
need to be made to the providers.
Ralph
On Dec 7, 2011, at 4:11 PM, James Carman wrote:
> How about creating a new package that has adapters for java7?
>
> o.a.c.vfs3.nio
> On Dec 7, 2011 6:32 PM, "sebb" wrote:
>
>
Hi,
Gary Gregory wrote:
> I am thinking of a different package name, not just version for VFS on
> Java 7 because we might want to release more VFS2-based versions that do
> break binary compatibility.
>
> We can retain the VFS name and brand for the project, but I'd prefer
> o.a.c.vfs to be for
Hi Devs,
Has there been any work done on the issue
https://issues.apache.org/jira/browse/VFS-178? Is this fixed on the last
release?
Thanks
--
Hiranya Jayathilaka
Associate Technical Lead;
WSO2 Inc.; http://wso2.org
E-mail: hira...@wso2.com; Mobile: +94 77 633 3491
Blog: http://techfeast-hiran
22 matches
Mail list logo
