Hi all,
I asked INFRA to open deploy on Nexus for commons-validator groupId,
Brian asked me[1] something I don't know how to reply.
Can someone join the discussion and provide a reply, please?
Many thanks in advance, all the best!
-Simo
[1] http://s.apache.org/PIb
http://people.apache.org/~simone
IMNAL, but it seems to be a basically badly worded basically BSD license.
The main problems I see is that it is missing the words 'irrevocable' and
'perpetual' in the language. The correct place would probably be
legal-discuss@a.o.
An ICLA wouldn't help. Getting a grant or getting an agreemen
Hi folks,
I think the best for commons-email-1.3 will be reverting the changes of
the setters from
Email setXXX(arg)
to
void setXXX(arg)
which in turn gives me binary backward compatibility. I would like to
see a commons-email-1.3 out there which gives me time to work on 2.0
Cheers,
Sie
Hi,
Dennis recently contributed a patch for triangular distributions (see
MATH-731). One of the methods implemented is based on a third party
Python code, the license of which is reproduced below. My question is:
can I commit this patch? Should we try and get in touch with the
original author (1998
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
I've just done a quick trawl through the clirr report comparing trunk with 1.2
I think all the incompatibilities can be fixed, provided that some
compromises are made.
There are about 25 constants that were removed from the Mail class
These changes are binary compatible, because compilers are req
You're right, it works (thoughI'm pretty sure that I wasn't able to edit
the page (I could be wrong), even if I was already register)
Twitter :http://www.twitter.com/m_cucchiara
G+ :https://plus.google.com/107903711540963855921
Linkedin:http://www.linkedin.com/in/mauriziocucchiara
On 8 January 2012 18:24, Maurizio Cucchiara wrote:
> Hi Christian,
> I would have added the OGNL infos, but seems that I have no enough karma.
> Can you add it or, alternatively, give me the appropriate privileges?
You should just need to create yourself a Wiki login, and then you can
update any
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
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-digester3 has an issue affecting its community integration.
This i
On Tue, 10 Jan 2012, Simone Tripodi wrote:
any reason why this release has to be a beta1? With all that fixed
issues, I would expect a GA release... WDYT?
I think it's fine to be a GA release. Back when I first tried to do the
release, the plan was to do a beta first as there were quite a few
+1
Oliver
Am 09.01.2012 16:46, schrieb Gary Gregory:
Good day to you all:
I have prepared Commons Pool 1.6-RC4.
There is NO change from RC3.
This RC exists because I blew up the Nexus staging repository for RC3
and a new RC is needed for a clean release process.
The only changes from 1.5.7
Hi again Nick,
any reason why this release has to be a beta1? With all that fixed
issues, I would expect a GA release... WDYT?
TIA,
-Simo
http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://www.99soft.org/
On Tue, Jan 10, 2012
Gary Gregory wrote:
> Good day to you all:
>
> I have prepared Commons Pool 1.6-RC4.
>
> There is NO change from RC3.
>
> This RC exists because I blew up the Nexus staging repository for RC3
> and a new RC is needed for a clean release process.
>
> The only changes from 1.5.7 are the addition
Hi again Nick!
I just requested to INFRA (see INFRA-4313) the access to Nexus to
deploy commons-validator groupId on Nexus to stage artifacts - I'll
cut out the RC as soon as the access will be open.
Hope this works for you ;)
Have anice day, all the best!
-Simo
http://people.apache.org/~simone
On 10 January 2012 20:04, Christian Grobmeier wrote:
> On Tue, Jan 10, 2012 at 8:54 PM, sebb wrote:
>> On 10 January 2012 19:37, Christian Grobmeier wrote:
>>> On Tue, Jan 10, 2012 at 5:45 PM, Siegfried Goeschl wrote:
Hi folks,
the main reason for the failed vote of commons-email
On Tue, Jan 10, 2012 at 8:54 PM, sebb wrote:
> On 10 January 2012 19:37, Christian Grobmeier wrote:
>> On Tue, Jan 10, 2012 at 5:45 PM, Siegfried Goeschl wrote:
>>> Hi folks,
>>>
>>> the main reason for the failed vote of commons-email-1.3 is that the release
>>> is only source but not binary co
On 10 January 2012 19:37, Christian Grobmeier wrote:
> On Tue, Jan 10, 2012 at 5:45 PM, Siegfried Goeschl wrote:
>> Hi folks,
>>
>> the main reason for the failed vote of commons-email-1.3 is that the release
>> is only source but not binary compatible
>>
>> +) if you compile your application wit
On Tue, Jan 10, 2012 at 5:45 PM, Siegfried Goeschl wrote:
> Hi folks,
>
> the main reason for the failed vote of commons-email-1.3 is that the release
> is only source but not binary compatible
>
> +) if you compile your application with the new version everything is fine
> +) if you replace simpl
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Commons Wiki" for
change notification.
The "Net/FrequentlyAskedQuestions" page has been changed by sebbapache:
http://wiki.apache.org/commons/Net/FrequentlyAskedQuestions?action=diff&rev1=21&rev2=22
Comment:
Fix up Jakarta
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Commons Wiki" for
change notification.
The "Net/FrequentlyAskedQuestions" page has been changed by sebbapache:
http://wiki.apache.org/commons/Net/FrequentlyAskedQuestions?action=diff&rev1=20&rev2=21
Comment:
No longer uses
On 10 January 2012 16:45, Siegfried Goeschl wrote:
> Hi folks,
>
> the main reason for the failed vote of commons-email-1.3 is that the release
> is only source but not binary compatible
>
> +) if you compile your application with the new version everything is fine
> +) if you replace simply the J
Hi folks,
the main reason for the failed vote of commons-email-1.3 is that the
release is only source but not binary compatible
+) if you compile your application with the new version everything is fine
+) if you replace simply the JAR the invocation fails
Is it mandatory that a minor release
+1 and thanks Gary once again for not giving up!!!
all the best,
-Simo
http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://www.99soft.org/
On Tue, Jan 10, 2012 at 3:26 AM, Gary Gregory wrote:
> On Mon, Jan 9, 2012 at 8:36 PM, s
Hi Nick!
of course, I'll give yet another review tonight (my +1 CET local
timezone) then I'll cut the RC :)
All the best,
-Simo
http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://www.99soft.org/
On Mon, Jan 9, 2012 at 11:51 P
25 matches
Mail list logo
