+1
Le mercredi 12 février 2014, Matt Benson a écrit :
> I would like to make the inaugural release of the [weaver] component.
>
> Apache Commons Weaver 1.0 RC1 is available for review at:
> https://dist.apache.org/repos/dist/dev/commons/weaver/ (r4368).
>
> Maven artifacts are at:
>
https://rep
I would like to make the inaugural release of the [weaver] component.
Apache Commons Weaver 1.0 RC1 is available for review at:
https://dist.apache.org/repos/dist/dev/commons/weaver/ (r4368).
Maven artifacts are at:
https://repository.apache.org/content/repositories/orgapachecommons-1007/.
T
On 11 February 2014 22:40, Thomas Neidhart wrote:
> On 02/10/2014 10:16 AM, Thomas Neidhart wrote:
>> Hi,
>>
>> this is an issue I was thinking about for some time now, and it is quite
>> some recurrent theme that we face in Commons.
>>
>> Considering our release practice, it is actually quite har
On 02/10/2014 10:16 AM, Thomas Neidhart wrote:
> Hi,
>
> this is an issue I was thinking about for some time now, and it is quite
> some recurrent theme that we face in Commons.
>
> Considering our release practice, it is actually quite hard to come up
> with new features as the API is more or le
I give the name I want on the command line: svn co tag_url dir_name.
Gary
Original message
From: sebb
Date:02/11/2014 15:49 (GMT-05:00)
To: Commons Developers List
Subject: Re: svn commit: r1566932 -
/commons/proper/weaver/tags/COMMONS_WEAVER_1_0_RC1/
On 11 February 20
On 11 February 2014 18:04, Gary Gregory wrote:
> IMO the tag should be:
>
> /commons/proper/weaver/tags/1_0_RC1/
>
> The path already has 'commons' AND 'weaver' in the name. I don't like the
> redundancies.
If you check the tag out, what is the default directory called?
That's one reason why it
Hi Benedikt,
many thanks for your kind introduction. :-) I also think jumping into the
code will do most, that's where I start for now. What I have seen so far
looks quite promising, especially the test coverage, hence it's maybe hard
for me to find big improvements. ... you mentioned a requiremen
On Tue, Feb 11, 2014 at 1:09 PM, Matt Benson wrote:
> On Mon, Feb 10, 2014 at 7:01 PM, Matt Benson wrote:
>
> > That ping came months ago, it's just that my OSS velocity is that slow
> > these days. I guess I'll just have to get on the RC merry-go-round. :/
> >
> >
> http://markmail.org/messag
Hi
IMO we should just use the mvn release plugin defaults
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
2014-02-11 19:09 GMT+01:00 Matt Benson :
> On Mon, Feb 10, 2014 at 7:
:)
G
-- Forwarded message --
From:
Date: Tue, Feb 11, 2014 at 1:08 PM
Subject: svn commit: r1567244 - /commons/proper/weaver/tags/1.0_RC1/
To: comm...@commons.apache.org
Author: mbenson
Date: Tue Feb 11 18:08:57 2014
New Revision: 1567244
URL: http://svn.apache.org/r1567244
Lo
On Mon, Feb 10, 2014 at 7:01 PM, Matt Benson wrote:
> That ping came months ago, it's just that my OSS velocity is that slow
> these days. I guess I'll just have to get on the RC merry-go-round. :/
>
>
http://markmail.org/message/f4ukbn5toxosnrmh
> Matt
>
>
> On Mon, Feb 10, 2014 at 6:59 PM,
IMO the tag should be:
/commons/proper/weaver/tags/1_0_RC1/
The path already has 'commons' AND 'weaver' in the name. I don't like the
redundancies.
Gary
On Tue, Feb 11, 2014 at 10:59 AM, Benedikt Ritter wrote:
> Do we really need the "COMMONS_" prefix in the tag?
>
>
> 2014-02-11 2:01 GMT+01:
I'll at least [codec] and see how that goes...
Gary
On Tue, Feb 11, 2014 at 11:01 AM, Benedikt Ritter wrote:
> Hi,
>
> this vote passes, since no -1 votes have been casted. I'll publish
> commons-parent 33 to maven central.
>
> After that, all component sites have to be republished, so that the
Le 11/02/2014 16:59, Benedikt Ritter a écrit :
> Do we really need the "COMMONS_" prefix in the tag?
And these CVS like underscores ? :)
Emmanuel Bourg
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional
I can't say the tag name matters much at all to me. :P
Matt
On Tue, Feb 11, 2014 at 9:59 AM, Benedikt Ritter wrote:
> Do we really need the "COMMONS_" prefix in the tag?
>
>
> 2014-02-11 2:01 GMT+01:00 Matt Benson :
>
> > That ping came months ago, it's just that my OSS velocity is that slow
Hi,
this vote passes, since no -1 votes have been casted. I'll publish
commons-parent 33 to maven central.
After that, all component sites have to be republished, so that they pick
up the new skin. Since this is very time consuming, I'd like to divide this
task a bit. Anybody who can help me with
Do we really need the "COMMONS_" prefix in the tag?
2014-02-11 2:01 GMT+01:00 Matt Benson :
> That ping came months ago, it's just that my OSS velocity is that slow
> these days. I guess I'll just have to get on the RC merry-go-round. :/
>
> Matt
>
>
> On Mon, Feb 10, 2014 at 6:59 PM, Gary Gre
Hello André,
nice that you're interested in BU2, welcome to this list.
2014-02-11 12:26 GMT+01:00 André Diermann :
> Hi,
>
> I stumbled upon the BeanUtils2 project which looks quite interessing to me.
> Do you have any future plans? (When) Will it replace the BeanUtils
> component?
>
We don't
On Mon, Feb 10, 2014 at 11:01 PM, Phil Steitz wrote:
> On 2/10/14, 5:14 PM, sebb wrote:
> > The advantage of annotations over Javadoc is that the meaning of each
> > annotation is precisely defined.
> >
> > Javadoc is mainly written in natural language.
> > This much harder to pin down precisely
Hi,
I stumbled upon the BeanUtils2 project which looks quite interessing to me.
Do you have any future plans? (When) Will it replace the BeanUtils
component?
I'm highly interested in contributing to this project. Please let me know,
if you plan to continue work on that project and how I might hel
Online report :
https://continuum-ci.apache.org/continuum/buildResult.action?buildId=28084&projectId=73
Build statistics:
State: Failed
Previous State: Ok
Started at: Tue 11 Feb 2014 11:20:17 +
Finished at: Tue 11 Feb 2014 11:22:11 +
Total time: 1m 54s
Build Trigger: Schedule
21 matches
Mail list logo
