thanks, I'll take a look at it.
On 01/31/2012 10:48 AM, Ate Douma wrote: > On 01/31/2012 09:42 AM, Niels van Dijk wrote: >> Hi Ate, >> >> In the Jira ticket you show the result of a scan that tested for >> potential isssues. Is it also possible to let such a scan actually list >> the files it thinks are in error? that would already be a lot less work >> that browse trough all source code. > > I don't think rat can be configured to only report potential issues, > however it took me 2 minutes to strip down the report for surfconext > only (potential) issues, see the new attachment I've added to > RAVE-450, including my remarks what I stripped. If you consider > dropping (deleting) the older tags, the report now is down to less > than 300 lines :) > > BTW: I just noticed that the trunk/pom.xml refers to a parent > coin-portal-parent:1.0.3-SNAPSHOT:pom which seems never have been > contributed. Not that might be important, but maybe good to be aware of. > > Regards, Ate > >> >> Cheers, >> Niels >> >> On 01/30/2012 01:40 AM, Ate Douma wrote: >>> On 01/16/2012 07:08 PM, Ate Douma wrote: >>>> On 01/16/2012 05:12 PM, Franklin, Matthew B. wrote: >>>>> On 1/16/12 10:56 AM, "Ross Gardler"<[email protected]> >>>>> wrote: >>>>> >>>>>> >>>>>>> * Check and make sure that the files that have been donated have >>>>>>> been >>>>>>> updated to reflect the new ASF copyright. >>>>>> >>>>>> Already done, surely? >>>>> >>>>> >>>>> I am not sure about all three donations. We should probably double >>>>> checkŠ >>>> >>>> Yes, we need to make sure. I think I went through that in the >>>> beginning, but its >>>> too long ago already to recall if it was complete(d). >>>> >>>> I'll volunteer doing the due diligence on this one, although it might >>>> take me a >>>> few days before I find time to do so. >>>> I will create a JIRA ticket for this. >>>> >>> Please see my follow up on >>> https://issues.apache.org/jira/browse/RAVE-425 >>> >>> I think we've got still quite some work on our place for this ... >>> >>> As I wrote in the issue, this is something we (the Mentors) clearly >>> dropped the ball on and should have followed up long time ago already, >>> for which I'd like to apologize for not doing so. >>> >>> I tried to provide a set of steps we can follow to resolve this, but >>> for myself this also is something I haven't dealt with before, so I'd >>> like the other mentors to chime in as well what they think should be >>> the right way to proceed. >>> >>> If needed we can consult the other IPMC members to help us out too as >>> there should be plenty of experience with these things. >>> >>> And I'm definitely willing to help out directly, with whatever is >>> needed to speed this up, just let me know. >>> >>> Regards, Ate >>> >>> >>> > >
