[GUMP@vmgump]: Project commons-vfs2-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-vfs2-test has an issue affecting its community integration. This i

[GUMP@vmgump]: Project commons-id (in module commons-sandbox) 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-id has an issue affecting its community integration. This issue af

[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-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-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-collections4-testframework (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-collections4-testframework has an issue affecting its community i

[GUMP@vmgump]: Project commons-exec-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-exec-test has an issue affecting its community integration. This i

[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

Re: svn commit: r1300429 - in /commons/proper/commons-parent/trunk: pom.xml src/changes/changes.xml

On 14 March 2012 01:17, Gary Gregory wrote: > Here is what we have in [io] now: > >         >          ${basedir}/src/changes/changes.xml >          %URL%/%ISSUE% >          Fix > Version,Key,Component,Summary,Type,Resolution,Status >           >          Key DESC,Type,Fix Version DESC >          

Re: svn commit: r1300429 - in /commons/proper/commons-parent/trunk: pom.xml src/changes/changes.xml

Here is what we have in [io] now: ${basedir}/src/changes/changes.xml %URL%/%ISSUE% Fix Version,Key,Component,Summary,Type,Resolution,Status Key DESC,Type,Fix Version DESC Fixed Resolved,Closed Bug,

Re: [lang] Longest common substring / Suffix Tree

It would have come in handy for me while doing bioinformatics work in the past. But, you're right, they have very cool tools out there. I was amazed at some of the stuff they can do. On Mar 13, 2012 7:08 PM, "Thomas Neidhart" wrote: > On 03/13/2012 08:55 AM, Luc Maisonobe wrote: > > Le 13/03/20

Re: [lang] Longest common substring / Suffix Tree

On 03/13/2012 08:55 AM, Luc Maisonobe wrote: > Le 13/03/2012 00:53, James Carman a écrit : >> A lot of bioinformaticians would love us if we added this! I picked this topic up as I find it interesting to myself and it would be a useful addition for many other people too I guess, but from what I ha

Re: svn commit: r1300298 - in /commons/proper/io/trunk/src/site: site.xml xdoc/index.xml xdoc/upgradeto2_2.xml

On 13 March 2012 19:29, wrote: > Author: ggregory > Date: Tue Mar 13 19:29:16 2012 > New Revision: 1300298 > > URL: http://svn.apache.org/viewvc?rev=1300298&view=rev > Log: > Preparing 2.2 release. > > Added: >    commons/proper/io/trunk/src/site/xdoc/upgradeto2_2.xml > Modified: >    commons/pro

Re: [io] Help with CharSequenceInputStream [WAS: [GUMP@vmgump]: Project commons-io-test (in module apache-commons) failed]

On 13 March 2012 18:17, Gary Gregory wrote: > On Tue, Mar 13, 2012 at 12:27 PM, sebb wrote: > >> On 13 March 2012 13:23, Gary Gregory wrote: >> > Hello All, >> > >> > Can the author/committer of CharSequenceInputStream[Test] take a look at >> > why Gump is failing? >> >> Seems to be intermittent

Re: [io] Help with CharSequenceInputStream [WAS: [GUMP@vmgump]: Project commons-io-test (in module apache-commons) failed]

On Tue, Mar 13, 2012 at 12:27 PM, sebb wrote: > On 13 March 2012 13:23, Gary Gregory wrote: > > Hello All, > > > > Can the author/committer of CharSequenceInputStream[Test] take a look at > > why Gump is failing? > > Seems to be intermittent. > > I've added a bit more debug which I hope will hel

Re: [ALL] Commons Parent reports

On Mar 13, 2012, at 14:05, sebb wrote: > On 13 March 2012 17:59, Gary Gregory wrote: >> On Mar 13, 2012, at 12:40, Gilles Sadowski >> wrote: >> >>> Hi. >>> > >>> [...] >>> >>> The tools are there, but you have to tell people that they _must_ use >>> them. >> >> Com

Re: [ALL] Commons Parent reports

On 13 March 2012 17:59, Gary Gregory wrote: > On Mar 13, 2012, at 12:40, Gilles Sadowski > wrote: > >> Hi. >> >> [...] >> >> The tools are there, but you have to tell people that they _must_ use >> them. > > Commons has already enough rules and process. As long as t

Re: [ALL] Commons Parent reports

When I'm researching competing open-source implementations, I use reports as part of my evaluation. The ones that are important to me are: Javadoc Findbugs Surefire Failsafe Cobertura If I'm evaluating an upgrade, I'll look at: Changes Clirr Chas Honton >Le 13/03/2012 17:52, Gilles Sadowski

Re: [ALL] Commons Parent reports

On Mar 13, 2012, at 12:40, Gilles Sadowski wrote: > Hi. > >>> > [...] > > The tools are there, but you have to tell people that they _must_ use > them. Commons has already enough rules and process. As long as the releases are have clean code I wouldn't be too anal

Re: [ALL] Commons Parent reports

On Mar 13, 2012, at 12:40, Gilles Sadowski wrote: >>> > [...] > > The tools are there, but you have to tell people that they _must_ use > them. Commons has already enough rules and process. As long as the releases are have clean code I wouldn't be too anal about th

Re: [ALL] Commons Parent reports

On Mar 13, 2012, at 12:23, Emmanuel Bourg wrote: > I'd like to see less reports by default. Most of them are only useful for > checking a release candidate by the commons devs, otherwise it just clutters > the sites with useless information for a general usage. > > The most important reports to

Re: [ALL] Commons Parent reports

Le 13/03/2012 17:52, Gilles Sadowski a écrit : What about the "Useful for the developer" category? They are useful at release time only, then they become quickly outdated as the code evolves after the release. If I want to help Commons Math, I'll checkout the code and build the reports. Th

Re: [ALL] Commons Parent reports

On Tue, Mar 13, 2012 at 5:40 PM, Gilles Sadowski wrote: >> And thats what I meant with: as long as we don't have a common >> codestyle, i does not make much sense to have a common checkstyle >> configuration. > > I thought that the question was whether to generate a CheckStyle report, not > whethe

Re: [ALL] Commons Parent reports

On Tue, Mar 13, 2012 at 05:23:06PM +0100, Emmanuel Bourg wrote: > I'd like to see less reports by default. Most of them are only > useful for checking a release candidate by the commons devs, > otherwise it just clutters the sites with useless information for a > general usage. > > The most import

Re: [ALL] Commons Parent reports

Hi. > > > >> > [...] > >> > > >> > The tools are there, but you have to tell people that they _must_ use > >> > them. > >> > >> Commons has already enough rules and process. As long as the releases > >> are have clean code I wouldn't be too anal about the commits in > >> between. > > > > I think

Re: [io] Help with CharSequenceInputStream [WAS: [GUMP@vmgump]: Project commons-io-test (in module apache-commons) failed]

On 13 March 2012 13:23, Gary Gregory wrote: > Hello All, > > Can the author/committer of CharSequenceInputStream[Test] take a look at > why Gump is failing? Seems to be intermittent. I've added a bit more debug which I hope will help next time. > Thank you, > Gary > > On Mon, Mar 12, 2012 at 10

Re: [ALL] Commons Parent reports

I'd like to see less reports by default. Most of them are only useful for checking a release candidate by the commons devs, otherwise it just clutters the sites with useless information for a general usage. The most important reports to publish for the public are: - Javadoc - JXR - Clirr - Chan

Re: [ALL] Commons Parent reports

On Tue, Mar 13, 2012 at 5:00 PM, Gilles Sadowski wrote: > Hi. > >> > [...] >> > >> > The tools are there, but you have to tell people that they _must_ use them. >> >> Commons has already enough rules and process. As long as the releases >> are have clean code I wouldn't be too anal about the commi

Re: [ALL] Commons Parent reports

Hi. > > [...] > > > > The tools are there, but you have to tell people that they _must_ use them. > > Commons has already enough rules and process. As long as the releases > are have clean code I wouldn't be too anal about the commits in > between. I think that the main disagreement is here. Sou

Re: [ALL] Commons Parent reports

> Unless I'm missing something: > >  (Using CheckStyle) != (Using the same formatting style in all projects) +1 http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ -

Re: [ALL] Commons Parent reports

On Mar 13, 2012, at 6:44 AM, Benedikt Ritter wrote: > Am 13. März 2012 14:15 schrieb Gary Gregory : >> On Tue, Mar 13, 2012 at 8:39 AM, Torsten Curdt wrote: >> >>> I find checkstyle to be not very useful. It's more hassle than it's >>> worth. It's like pointing fingers instead of helping. If yo

Re: [ALL] Commons Parent reports

On Tue, Mar 13, 2012 at 03:08:01PM +0100, Christian Grobmeier wrote: > +1 on the mentioned plugins, except: > -1 on checkstyle. > > I dont see a benefit in making checkstyle default. If somebody wants > to use that tool, he can. > > What checkstyle-style would be the default? Sun conventions or m

Re: [ALL] Commons Parent reports

> I didn't think we disagreed on refusing to spend a lot of time of correcting > formatting mess. Not on that one :) I just argue that in the days of code formatters "lot of time" has become is quite significant. >> Then you are probably a vocal minority here. > > Because I don't use an IDE or

Re: [ALL] Commons Parent reports

+1 on the mentioned plugins, except: -1 on checkstyle. I dont see a benefit in making checkstyle default. If somebody wants to use that tool, he can. What checkstyle-style would be the default? Sun conventions or maven style? I am for sun, Simone is for maven (i guess). Probably there is another

Re: [ALL] Commons Parent reports

Hi again Torsten! I thought it would be useful having a checkstyle also becasue it is not just a matter of code formatting rules, there are also useful basic checks that help - me, at least - on taking care of some rules I can occasionally forget to

Re: [ALL] Commons Parent reports

On Tue, Mar 13, 2012 at 02:27:32PM +0100, Torsten Curdt wrote: > > CheckStyle reports should be checked regularly. Only doing so just before a > > release indeed leads to a lot of tedious work, because coders did not > > respect the basic, agreed on, style. > > I guess we are disagreeing here. I

Re: [ALL] Commons Parent reports

Am 13. März 2012 14:15 schrieb Gary Gregory : > On Tue, Mar 13, 2012 at 8:39 AM, Torsten Curdt wrote: > >> I find checkstyle to be not very useful. It's more hassle than it's >> worth. It's like pointing fingers instead of helping. If you want to >> foster a certain code style provide eclipse and

Re: [ALL] Commons Parent reports

> CheckStyle reports should be checked regularly. Only doing so just before a > release indeed leads to a lot of tedious work, because coders did not > respect the basic, agreed on, style. I guess we are disagreeing here. > I don't use an IDE, so for me, CheckStyle helps but formatter IDE plugins

[io] Help with CharSequenceInputStream [WAS: [GUMP@vmgump]: Project commons-io-test (in module apache-commons) failed]

Hello All, Can the author/committer of CharSequenceInputStream[Test] take a look at why Gump is failing? Thank you, Gary On Mon, Mar 12, 2012 at 10:04 PM, Gump wrote: > To whom it may engage... > > This is an automated request, but not an unsolicited one. For > more information please visit ht

Re: [ALL] Commons Parent reports

On Tue, Mar 13, 2012 at 8:39 AM, Torsten Curdt wrote: > I find checkstyle to be not very useful. It's more hassle than it's > worth. It's like pointing fingers instead of helping. If you want to > foster a certain code style provide eclipse and intellij formatter > settings instead - that's actua

Re: [ALL] Commons Parent reports

On Tue, Mar 13, 2012 at 01:39:40PM +0100, Torsten Curdt wrote: > I find checkstyle to be not very useful. It's more hassle than it's > worth. It's like pointing fingers instead of helping. If you want to > foster a certain code style provide eclipse and intellij formatter > settings instead - that'

Re: [ALL] Commons Parent reports

I find checkstyle to be not very useful. It's more hassle than it's worth. It's like pointing fingers instead of helping. If you want to foster a certain code style provide eclipse and intellij formatter settings instead - that's actually helping. Especially if you run them before a release. The b

Re: [ALL] Commons Parent reports

On Tue, Mar 13, 2012 at 8:14 AM, Simone Tripodi wrote: > Hi Torsten! > > > -1 for checkstyle > > With my +1 I meant that, as we discussed in another thread, the parent > could provide a default - but overridable - configuration; I think > that having at least one metric of code style measure in ea

Re: [ALL] Commons Parent reports

Hi Torsten! > -1 for checkstyle With my +1 I meant that, as we discussed in another thread, the parent could provide a default - but overridable - configuration; I think that having at least one metric of code style measure in each component would be nice to have, so unless other preferences, the

Re: [ALL] Commons Parent reports

> The following could be added: > > Findbugs > Checkstyle +1 for findbugs -1 for checkstyle cheers, Torsten - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.or

Re: [ALL] Commons Parent reports

Hi! > Commons Parent 24 includes the following reports: > > Javadoc > Jxr > Surefire > RAT > Cobertura > Clirr > JDepend > > I think the following should be added: > > Changes/JIRA +1 the pattern is always the same > > The following could be added: > > Findbugs > Checkstyle +1 > > Any others?

[ALL] Commons Parent reports

Commons Parent 24 includes the following reports: Javadoc Jxr Surefire RAT Cobertura Clirr JDepend I think the following should be added: Changes/JIRA The following could be added: Findbugs Checkstyle Any others? - To unsubs

Re: [csv] Headers

I think transforming the result of the parse process into instances of some class is a different concern. That should not be part of as CSVParser. In Hibernate they use ResultTransformers for this purpose [1]. I think we should separate this concerns as well. [1] http://docs.jboss.org/hibernate/o

Re: [MATH] Does website really need Javadoc for versions prior to 2.2?

On Tue, Mar 13, 2012 at 11:28 AM, Gilles Sadowski < gil...@harfang.homelinux.org> wrote: > On Mon, Mar 12, 2012 at 08:22:27PM +0100, Luc Maisonobe wrote: > > Le 12/03/2012 16:50, sebb a écrit : > > > In addition to Javadoc for 3.0 and 2.2, the website still offers the > following: > I have found

Re: [MATH] Does website really need Javadoc for versions prior to 2.2?

On Mon, Mar 12, 2012 at 08:22:27PM +0100, Luc Maisonobe wrote: > Le 12/03/2012 16:50, sebb a écrit : > > In addition to Javadoc for 3.0 and 2.2, the website still offers the > > following: > > > > Javadoc (2.1 release) > > Javadoc (2.0 release) > > Javadoc (1.2 release) > > Javadoc (1.1 release)

Re: [csv] Performance comparison

Le 13/03/2012 02:47, Niall Pemberton a écrit : IMO performance should be taken out of the equation by using the Readable interface[1]. That way the users can use whatever implementation suits them (for example using an underlying buffered InputStream) to change/improve performance. I you mean

[ANNOUNCE] Commons Parent 24 released

Commons Parent has been released. Main changes: - added tests and test-source jars to the release profile. - Added cobertura: 2.5.1 to reporting and buildManagement - Add default project info reports: excluded license/plugins/plugin management Release notes (including all changes): https://svn.a

Re: [csv] Performance comparison

On 13 March 2012 09:01, Emmanuel Bourg wrote: > Le 13/03/2012 01:44, sebb a écrit : > > >> I don't think we should be trying to recode JDK classes. > > > I'd rather not, but we have done that in the past. FastDateFormat and > StrBuilder come to mind. And now Java has StringBuilder, which means St

Re: [csv] Headers

Le 13/03/2012 09:56, sebb a écrit : It needs to be possible to access columns by index without having to use annotations. That's still possible with the low level API. I'm just exploring the features I would expect of a bean mapping. Emmanuel Bourg smime.p7s Description: S/MIME Cryptogra

Re: [csv] Performance comparison

Le 13/03/2012 01:44, sebb a écrit : I don't think we should be trying to recode JDK classes. I'd rather not, but we have done that in the past. FastDateFormat and StrBuilder come to mind. Emmanuel Bourg smime.p7s Description: S/MIME Cryptographic Signature

Re: [csv] Headers

On 13 March 2012 08:52, Emmanuel Bourg wrote: > Le 13/03/2012 09:21, Jörg Schaible a écrit : > > >>> If the file has a header, the fields are matched by attribute name, and >>> an annotation can override the name of the column associated to an >>> attribute. >> >> >> Yeah, but that's not required.

Re: [csv] Headers

Le 13/03/2012 09:21, Jörg Schaible a écrit : If the file has a header, the fields are matched by attribute name, and an annotation can override the name of the column associated to an attribute. Yeah, but that's not required. Just because you can read the names of the columns does not mean tha

Re: [csv] Headers

Emmanuel Bourg wrote: > Le 13/03/2012 00:56, sebb a écrit : > >>> 1. Do nothing and address it in the next release with the bean mapping. >>> Parsing the file would then look like this: >>> >>> CSVFormat format = CSVFormat.DEFAULT.withType(Person.class); >>> for (Person person : format.parse

Re: [lang] Longest common substring / Suffix Tree

Le 13/03/2012 00:53, James Carman a écrit : > A lot of bioinformaticians would love us if we added this! In the same spirit, I know an implementation of the Myers difference algorithm that runs on any object implementing equals and also provides an API for browsing the "edit script" resulting from

Re: [csv] Headers

Le 13/03/2012 00:56, sebb a écrit : > On 12 March 2012 22:11, Emmanuel Bourg wrote: >> [csv] is missing some elements to ease the use of headers. I have no clear >> idea on how to address this, here are my thoughts. >> >> Headers are used when the fields are accessed by the column name rather than