Hi Matt,
I had a quick look at your branch and I honestly think it is a very
good work, maybe we could insert even more modules granularization,
but IMHO it worths to merge it in the main branch.
Do you see any blocker?
Best and thanks!
-Simo
http://people.apache.org/~simonetripodi/
http://simon
If I do "mvn -Preporting clean site" with CP 28 I get:
[INFO]
[INFO] <<< jdepend-maven-plugin:2.0-beta-2:generate (report:generate) @
commons-codec <<<
[INFO] configuring report plugin
org.codehaus.mojo:cobertura-maven-plugin:2.5.2
[WARNING] The POM for org.codehaus.mojo:cobertura-maven-plugin:jar
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 has an issue affecting its community integration.
This issue
Hey Gary,
I had a short look at the parent and it seems to be okay... I'll try to
build codec after work when I'm at home. Until then, you could try mvn
clean install -U to force update of releases (and snapshots). Maybe -X
gives us some more information, whats wrong...
Benedikt
2013/1/28 Gary
Sorry, in your case it should be mvn -Preporting clean site -U
Benedikt
2013/1/28 Benedikt Ritter
> Hey Gary,
>
> I had a short look at the parent and it seems to be okay... I'll try to
> build codec after work when I'm at home. Until then, you could try mvn
> clean install -U to force update
On Mon, Jan 28, 2013 at 8:21 AM, Benedikt Ritter wrote:
> Sorry, in your case it should be mvn -Preporting clean site -U
>
OK, that worked.
Thank you!
Gary
>
> Benedikt
>
>
> 2013/1/28 Benedikt Ritter
>
> > Hey Gary,
> >
> > I had a short look at the parent and it seems to be okay... I'll tr
Hi Simo,
As for the modularization, I went ahead and did this in the trunk. On
the overall I think Bruno's work is proceeding in a good direction, so I
agree that it should be merged back to trunk when ready. I have some more
refactorings i am interested to try out on this, or another, branch.
Hi Matt
> As for the modularization, I went ahead and did this in the trunk. On
>the overall I think Bruno's work is proceeding in a good direction, so I
>agree that it should be merged back to trunk when ready.
Thanks! I'll sync the repos here at office in the next hours. Regarding the
other
Hi.
Is there any sort of estimate release date for 1.1.2?
the reason im asking is this issue
https://issues.apache.org/jira/browse/LOGGING-119 which is affecting
jenkins (https://issues.jenkins-ci.org/browse/JENKINS-15846) is now marked
as fixed for 1.1.2, but given that 1.1.1 was released novembe
On 01/28/2013 07:02 PM, radai wrote:
> Hi.
>
> Is there any sort of estimate release date for 1.1.2?
> the reason im asking is this issue
> https://issues.apache.org/jira/browse/LOGGING-119 which is affecting
> jenkins (https://issues.jenkins-ci.org/browse/JENKINS-15846) is now marked
> as fixed f
On Mon, Jan 28, 2013 at 10:18 AM, Bruno P. Kinoshita wrote:
> Hi Matt
>
> > As for the modularization, I went ahead and did this in the trunk. On
> >the overall I think Bruno's work is proceeding in a good direction, so I
> >agree that it should be merged back to trunk when ready.
>
> Thanks! I'
Am 28.01.2013 um 19:08 schrieb Thomas Neidhart :
> On 01/28/2013 07:02 PM, radai wrote:
>> Hi.
>>
>> Is there any sort of estimate release date for 1.1.2?
>> the reason im asking is this issue
>> https://issues.apache.org/jira/browse/LOGGING-119 which is affecting
>> jenkins (https://issues.jen
On 01/28/2013 09:21 PM, Benedikt Ritter wrote:
>
>
> Am 28.01.2013 um 19:08 schrieb Thomas Neidhart :
>
>> On 01/28/2013 07:02 PM, radai wrote:
>>> Hi.
>>>
>>> Is there any sort of estimate release date for 1.1.2?
>>> the reason im asking is this issue
>>> https://issues.apache.org/jira/browse/L
Am 28.01.2013 um 21:12 schrieb Matt Benson :
> On Mon, Jan 28, 2013 at 10:18 AM, Bruno P. Kinoshita wrote:
>
>> Hi Matt
>>
>>> As for the modularization, I went ahead and did this in the trunk. On
>>> the overall I think Bruno's work is proceeding in a good direction, so I
>>> agree that it s
Am 28.01.2013 um 21:28 schrieb Thomas Neidhart :
> On 01/28/2013 09:21 PM, Benedikt Ritter wrote:
>>
>>
>> Am 28.01.2013 um 19:08 schrieb Thomas Neidhart :
>>
>>> On 01/28/2013 07:02 PM, radai wrote:
Hi.
Is there any sort of estimate release date for 1.1.2?
the reason im a
Hello, Benedikt! I had the same concern about "Interruptible", TBH.
Thanks for weighing in. As I mentioned earlier, I am thinking of
PredicatedGenerator at this point.
Matt
On Mon, Jan 28, 2013 at 2:30 PM, Benedikt Ritter wrote:
>
>
> Am 28.01.2013 um 21:12 schrieb Matt Benson :
>
> > On Mon,
(From time to time I am going to post an update about the progress I
have made so that everybody who is interested can comment.)
Just finished reworking MultiFileConfiguration to use the new builder
approach. There is now a MultiFileConfigurationBuilder class offering
pretty much the same func
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=25957&projectId=72
Build statistics:
State: Failed
Previous State: Ok
Started at: Mon 28 Jan 2013 21:20:07 +
Finished at: Mon 28 Jan 2013 21:22:11 +
Total time: 2m 4s
Build Trigger: Schedule
Build
Sure - But as I've worked with CombinedConfiguration I became less enthralled
with it. The problem I had with the DynamicCombinedConfiguration was that
every CombinedConfiguration has to have its own copy of all the configurations.
Attempting to share a configuration led to all kinds of corrupt
Hi all,
The CollectionTransformer in [functor] has the following TODO:
TODO revisit this class... it could stand a more-descriptive name. Also,
it's a little
hard to say whether, for an instance constructed without a specific target
collection,
#evaluate() should return a new ArrayL
Ops, turns out I had already started a thread [1] about this TODO here in the
mailing list. Quoting other names that I had thought:
"GeneratorToCollectionTransformer (...) Listify, Eagerlize and Lazy List
Builder."
Sorry,
[1] http://markmail.org/thread/l552rd6xrr2afcvl
Bruno P. Kinoshita
htt
Hmm, I'm struggling with the package name. oacf.generator.flow? I wonder
if we should just merge this package back into oacf.generator.
Matt
On Mon, Jan 28, 2013 at 8:15 PM, Matt Benson wrote:
> I think so, yes. :) Knew there was something I forgot!
>
> Matt
>
>
> On Mon, Jan 28, 2013 at 7
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-vfs2 has an issue affecting its community integration.
This issue
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-jexl3 has an issue affecting its community integration.
This issue
24 matches
Mail list logo
