[GUMP@vmgump]: Project commons-scxml-test (in module apache-commons) failed

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

[GUMP@vmgump]: Project commons-configuration-test (in module apache-commons) failed

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

[GUMP@vmgump]: Project commons-dbutils (in module apache-commons) failed

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

[GUMP@vmgump]: Project commons-proxy-test (in module apache-commons) failed

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

[GUMP@vmgump]: Project commons-chain2 (in module apache-commons) failed

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

[GUMP@vmgump]: Project commons-lang3-test (in module apache-commons) failed

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-lang3-test has an issue affecting its community integration. This

[GUMP@vmgump]: Project commons-digester3 (in module apache-commons) failed

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

[GUMP@vmgump]: Project commons-dbcp2 (in module apache-commons) failed

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

[GUMP@vmgump]: Project commons-dbcp (in module commons-dbcp-1.x) failed

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

Re: [beanutils] Property access on a fluent API

Am 05.12.2012 23:13, schrieb Benedikt Ritter: 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

Re: [BCEL] The BCEL issue tracker has moved from Bugzilla to JIRA

Thanks for your work on this, Mark T! Matt On Thu, Dec 6, 2012 at 2:36 PM, sebb wrote: > When BCEL moved to Commons from Jakarta it was using Bugzilla as the > issue tracker. > > As all other Commons components use JIRA, it was decided to move BCEL > issue handling to JIRA. > > This move has n

[BCEL] The BCEL issue tracker has moved from Bugzilla to JIRA

When BCEL moved to Commons from Jakarta it was using Bugzilla as the issue tracker. As all other Commons components use JIRA, it was decided to move BCEL issue handling to JIRA. This move has now happened and all Bugzilla issues have been imported into JIRA as the "BCEL" project, i.e. they can be

[GUMP@vmgump]: Project commons-configuration-test (in module apache-commons) failed

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

Re: [digester3] javadoc style

Yes. Gary On Dec 6, 2012, at 12:06, "iwo.diana" wrote: > I sent a patch for issue https://issues.apache.org/jira/browse/DIGESTER-173 > but I have some questions about javadoc style, can I use @see with external > resource (like to standard jdk javadoc)? > > > > -- > View this message in context

[digester3] javadoc style

I sent a patch for issue https://issues.apache.org/jira/browse/DIGESTER-173 but I have some questions about javadoc style, can I use @see with external resource (like to standard jdk javadoc)? -- View this message in context: http://apache-commons.680414.n4.nabble.com/digester3-javadoc-style-tp

Re: [weaver]/[bcel] WAS [privilizer] promotion plan

One of the stuff I heard way back was that BCEL still has no native Java7 support. Is this still true? Imo that was one of the reasons why openjpa went for doing parts of the bytecode stuff with ASM... Happy to get proved wrong ;) LieGrue, strub - Original Message - > From: Matt Be