Henri,
On Fri, Jan 8, 2010 at 1:22 AM, Henri Yandell wrote:
> How would that work?
>
> If I do work on one component and want to release it, do I have to
> wait on 7 other releases?
>
If you work on one Commons Collection artifact within a Commons
Collection release, yes.
Paul
How would that work?
If I do work on one component and want to release it, do I have to
wait on 7 other releases?
Multiple artifacts is going to encourage growth, but without separate
release cycles it's going to create release stagnation.
I'd suggest figuring out what the dependency tree is bef
You should have the rights.
Make the branch into the sandbox rather than inside digester. Something like:
svn mkdir https://svn.apache.org/repos/asf/commons/sandbox/digester-anno/
svn cp -m "Branching into the sandbox for annotation changes to
digester" https://svn.apache.org/repos/asf/commons/pr
Hi all, Jochen, Rahul,
thanks for your help, fine for me working on a branch, I'm more than
pleased to adopt the best solution that fits with the community needs
:)
I don't think I have the rights needed to branch the digester, can
anyone help me please? Many thanks in advance, more than appreciate
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=266553&projectId=2619
Build statistics:
State: Failed
Previous State: Failed
Started at: Wed 6 Jan 2010 02:19:40 -0800
Finished at: Wed 6 Jan 2010 02:21:43 -0800
Total time: 2m 3s
Build Trigger: Forced
Bu
I personally don't know when final version of 2.1 will be released, but you
can check out and compile Commons Math from the Subversion repository to get
the fixes:
https://svn.apache.org/repos/asf/commons/proper/math/trunk
Maybe Luc or others know more about the 2.1 roadmap.
2010/1/7 손기섭
> Hi.
Looks like the Thread.sleep(100L) is taking too long, and allowing
some of the initial 10 threads to complete their hold time; this
accounts for the threads with more than 1 loop.
However, the last 10 threads should still timeout, as none of the
first 10 threads should release the connection until
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=266493&projectId=2619
Build statistics:
State: Failed
Previous State: Failed
Started at: Tue 5 Jan 2010 21:38:35 -0800
Finished at: Tue 5 Jan 2010 21:40:40 -0800
Total time: 2m 4s
Build Trigger: Schedule
+1
On Thu, Jan 7, 2010 at 4:45 PM, Dennis Lundberg wrote:
> +1
>
> sebb wrote:
>> Is it OK to delete the Maven1 build files from IO? The code now
>> requires Java 1.5.
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@commons.ap
But not splitting into separate releases, just separate artifacts. As
stated before, separate releases creates a compatibility matrix. These
aren't separate projects, but different areas of one.
On Thu, Jan 7, 2010 at 2:56 PM, Matt Benson wrote:
>
> On Jan 5, 2010, at 7:58 PM, Stephen Colebourne
The overridable methods in DirectoryWalker currently use Collection
as a parameter type.
As far as I can tell, the Collections need to contain File objects, so
would it not be better to use Collection?
Might be nice to use Collection, but when I tried that
there were some problems with the test c
+1
sebb wrote:
> Is it OK to delete the Maven1 build files from IO? The code now
> requires Java 1.5.
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.o
On Jan 5, 2010, at 7:58 PM, Stephen Colebourne wrote:
[SNIP]
And splitting [collections]? Definitely a good idea. I would remove
all the Predicate/Closure/Transformer code (if you believe in FP,
use [functor]). Then split the rest by implementations of JDK
collections, and extended JDK coll
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=266444&projectId=2619
Build statistics:
State: Failed
Previous State: Failed
Started at: Tue 5 Jan 2010 17:35:03 -0800
Finished at: Tue 5 Jan 2010 17:35:52 -0800
Total time: 48s
Build Trigger: Schedule
Bu
On Thu, Jan 7, 2010 at 7:11 AM, Simone Tripodi wrote:
> Hi Jochen,
> sorry for the delay (I'm currently at office), I think it is better if
> we involve Rahul Akolkar (CC-ed in the mail): I'm an ASF committer but
> not a Digester neither Commons committer; in this scenario I propose
> to let the c
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=266440&projectId=2619
Build statistics:
State: Failed
Previous State: Failed
Started at: Tue 5 Jan 2010 16:16:09 -0800
Finished at: Tue 5 Jan 2010 16:17:17 -0800
Total time: 1m 7s
Build Trigger: Schedule
On 07/01/2010, hen...@apache.org wrote:
> Author: henrib
> Date: Thu Jan 7 18:00:07 2010
> New Revision: 896944
>
> URL: http://svn.apache.org/viewvc?rev=896944&view=rev
> Log:
> JEXL-46; adding Perl-like regular-expression operators (=~ and !~)
[...]
> /** {...@inheritdoc} */
> +
On 01/07/2010 06:23 PM, mdirkse wrote:
I suppose I can ping you to test the pre-release
For sure. And if you need any help verifying bug fixes etc. to clean up
Jira, let me know.
Will do.
Thanks
--
^TM
-
To unsubscribe,
> I'll try to make the release by the end of this month.
Fantastic.
> I suppose I can ping you to test the pre-release
For sure. And if you need any help verifying bug fixes etc. to clean up
Jira, let me know.
Regards,
Maarten
On 01/07/2010 05:25 PM, mdirkse wrote:
>
>
> So here's my question: is there any chance of a new release of daemon being
> baked?
I'll try to make the release by the end of this month.
Still have to clean up all the Jira issues.
> I'm willing to help out in any way I can to make it happen. We've
On 01/07/2010 05:25 PM, mdirkse wrote:
>
>
> So here's my question: is there any chance of a new release of daemon being
> baked?
I'll try to make the release by the end of this month.
Still have to clean up all the Jira issues.
> I'm willing to help out in any way I can to make it happen. We've
Hi,
We'd really like for the daemon executable to forward the -javaagent command
line arg to the java command. One of my colleagues actually patched
arguments.c in order to support this. Much to our surprise, when we went to
check the code in svn, it already included a similar fix.
The commit tha
On 07/01/2010, Phil Steitz wrote:
> sebb wrote:
> > On 06/01/2010, Phil Steitz wrote:
> >> sebb wrote:
> >> > On 05/01/2010, sebb wrote:
> >> >> On 05/01/2010, Phil Steitz wrote:
> >> >> > sebb wrote:
> >> >> > > It would be very useful to have a Continuum DBCP build that
> used J
Hi Jochen,
sorry for the delay (I'm currently at office), I think it is better if
we involve Rahul Akolkar (CC-ed in the mail): I'm an ASF committer but
not a Digester neither Commons committer; in this scenario I propose
to let the community express the opinion in having this new feature
included
sebb wrote:
> On 06/01/2010, Phil Steitz wrote:
>> sebb wrote:
>> > On 05/01/2010, sebb wrote:
>> >> On 05/01/2010, Phil Steitz wrote:
>> >> > sebb wrote:
>> >> > > It would be very useful to have a Continuum DBCP build that used
>> Java 5.
>> >> > >
>> >> > > The current build use
That's strange - same symptoms as DBCP-318, but this time it affects
both TestPerUserPoolDataSource and TestSharedPoolDataSource so it must
be a different bug, as 318 only affected PerUser.
I've not yet tried soak testing using Java 1.5; I hope to find time to
do so later today.
Meanwhile I will
+1
Siegfried Goeschl
sebb wrote:
> Is it OK to delete the Maven1 build files from IO? The code now
> requires Java 1.5.
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h..
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=266396&projectId=2619
Build statistics:
State: Failed
Previous State: Failed
Started at: Tue 5 Jan 2010 05:37:11 -0800
Finished at: Tue 5 Jan 2010 05:38:08 -0800
Total time: 57s
Build Trigger: Schedule
Bu
On Thu, Jan 7, 2010 at 7:54 AM, Simone Tripodi wrote:
> very nice to meet you! I imported the digester as dependency since,
> fortunately, I don't have to modify the existing code, but just adding
> a new package that contains the new feature.
Just adds to my concerns. If you are not even modify
29 matches
Mail list logo