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-scxml-test has an issue affecting its community integration.
This
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-configuration-test has an issue affecting its community
integrati
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-dbutils has an issue affecting its community integration.
This iss
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
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-chain2 has an issue affecting its community integration.
This issu
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
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-dbcp2 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-dbcp has an issue affecting its community integration.
This issue
On 5 December 2012 20:47, Thomas Neidhart wrote:
> On 12/04/2012 10:41 PM, sebb wrote:
>> On 4 December 2012 21:16, Thomas Neidhart wrote:
>>> On 12/03/2012 11:25 PM, sebb wrote:
On 3 December 2012 22:11, Thomas Neidhart
wrote:
> On 12/03/2012 11:01 PM, Gary Gregory wrote:
>>
Hi Oliver,
AFAIK beanutils is not restricted to pure JavaBeans. The project website
just says that the component provides simple wrappers around the java
refelct and introspect API. So I would say, that the functionality you
propsed would fit nicely into BU (maybe the scope has changed and now the
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=25422&projectId=72
Build statistics:
State: Failed
Previous State: Ok
Started at: Wed 5 Dec 2012 21:20:17 +
Finished at: Wed 5 Dec 2012 21:22:35 +
Total time: 2m 17s
Build Trigger: Schedule
Build
Hi all,
in [configuration] [beanutils] is used to initialize properties of Java
objects defined in configuration files. This works fine as long as the
objects conform to the Java Beans specification.
Now I would like to initialize other objects, too, which implement a
fluent interface as fol
On 12/04/2012 10:41 PM, sebb wrote:
> On 4 December 2012 21:16, Thomas Neidhart wrote:
>> On 12/03/2012 11:25 PM, sebb wrote:
>>> On 3 December 2012 22:11, Thomas Neidhart wrote:
On 12/03/2012 11:01 PM, Gary Gregory wrote:
> Note that Commons IO 2.4 requires a minimum of JDK 1.6.
>>
A [weaver] component as I envisioning it would provide e.g. a
BytecodeWeaver interface, a custom implementation of which could be
specified via:
- the Maven plugin
- the Antlib
- the Java API
Thus IMO it would be quite natural for [nabla] to make use of [weaver].
>From Torsten's/Mark's/Stephen's
On Dec 5, 2012, at 9:22, sebb wrote:
> On 5 December 2012 14:17, wrote:
>> Author: ggregory
>> Date: Wed Dec 5 14:17:42 2012
>> New Revision: 1417434
>>
>> URL: http://svn.apache.org/viewvc?rev=1417434&view=rev
>> Log:
>> maven-compiler-plugin 2.5.1 -> 3.0
>
> Does that still work with Maven 2
sebb wrote:
> On 5 December 2012 14:17, wrote:
>> Author: ggregory
>> Date: Wed Dec 5 14:17:42 2012
>> New Revision: 1417434
>>
>> URL: http://svn.apache.org/viewvc?rev=1417434&view=rev
>> Log:
>> maven-compiler-plugin 2.5.1 -> 3.0
>
> Does that still work with Maven 2.2.1 ?
Yes.
>
>> Modif
On 5 December 2012 14:17, wrote:
> Author: ggregory
> Date: Wed Dec 5 14:17:42 2012
> New Revision: 1417434
>
> URL: http://svn.apache.org/viewvc?rev=1417434&view=rev
> Log:
> maven-compiler-plugin 2.5.1 -> 3.0
Does that still work with Maven 2.2.1 ?
> Modified:
> commons/proper/commons-pa
Hi all,
Le 04/12/2012 23:54, Matt Benson a écrit :
> Well, it looks like the most comfortable avenue for everyone is Commons
> [weaver]. IMO [weaver] would look like a framework for implementing any
> kind of code weaving, so the most important decision is the look of the
> API, and it would seem
On 4 December 2012 23:05, Gary Gregory wrote:
> I like the name weaver.
>
> Does it make sense to allow different libs to be plugged in? BCEL,
> ASM... Or do do we have to pick one?
Based on what I see in various projects, ASM won, BCEL lost. Main
problem tends to be different versions of ASM bei
Le 04/12/2012 23:54, Matt Benson a écrit :
> Well, it looks like the most comfortable avenue for everyone is Commons
> [weaver]. IMO [weaver] would look like a framework for implementing any
> kind of code weaving, so the most important decision is the look of the
> API, and it would seem that eat
On 04/12/2012 22:54, Matt Benson wrote:
> Well, it looks like the most comfortable avenue for everyone is Commons
> [weaver]. IMO [weaver] would look like a framework for implementing any
> kind of code weaving, so the most important decision is the look of the
> API, and it would seem that eating
21 matches
Mail list logo
