On 9/14/06, Martijn Dashorst [EMAIL PROTECTED] wrote:
Just out of interest, what would this tool specifically check for?
there are a number of mechanical checks that i perform. they are slow
to perform manually. i can't scale. so i've made a start on automating
them. it's a work in progress.
On 9/14/06, Eelco Hillenius [EMAIL PROTECTED] wrote:
Just curious: what kind of issues does it track down?
whatever issues it's coded to track down ;-)
it's a work in progress. it turned up the potential issues with source
document in the last servicemix candidate.
- robert
On 9/14/06, robert burrell donkin [EMAIL PROTECTED] wrote:
i have a basic tool that i've been running against the source releases
recently. it's simple but helps to track down some basic issues. no
documentation.
would this tool be useful for podlings (mentors and release managers
in
On Sep 14, 2006, at 2:40 PM, Daniel Kulp wrote:
I would suggest it go into:
https://svn.apache.org/repos/private/committers/tools/
as it would be applicable for non-incubator projects as well.
Unless there's something special, how about a public tree? A podling
it's own right?
--
Jeremy
On 9/15/06, Jeremy Boynes [EMAIL PROTECTED] wrote:
On Sep 14, 2006, at 2:40 PM, Daniel Kulp wrote:
I would suggest it go into:
https://svn.apache.org/repos/private/committers/tools/
as it would be applicable for non-incubator projects as well.
Unless there's something special, how about a
i have a basic tool that i've been running against the source releases
recently. it's simple but helps to track down some basic issues. no
documentation.
would this tool be useful for podlings (mentors and release managers
in particular)?
if so, would it be appropriate to check the source in
On 9/14/06, robert burrell donkin [EMAIL PROTECTED] wrote:
i have a basic tool that i've been running against the source releases
recently. it's simple but helps to track down some basic issues. no
documentation.
would this tool be useful for podlings (mentors and release managers
in
Just curious: what kind of issues does it track down?
Eelco
On 9/14/06, robert burrell donkin [EMAIL PROTECTED] wrote:
i have a basic tool that i've been running against the source releases
recently. it's simple but helps to track down some basic issues. no
documentation.
would this tool be
Just out of interest, what would this tool specifically check for? In
what does it differ from checkstyle, pmd and findbugs?
Will it work with Java/C/C++/Python sources?
Best regards,
Martijn
On 9/14/06, robert burrell donkin [EMAIL PROTECTED] wrote:
i have a basic tool that i've been
On Thursday September 14 2006 5:31 pm, robert burrell donkin wrote:
i have a basic tool that i've been running against the source releases
recently. it's simple but helps to track down some basic issues. no
documentation.
would this tool be useful for podlings (mentors and release managers
10 matches
Mail list logo
