+1 for project files. There are ways to ensure that local, hardcoded paths
are not used.
We can put them in an ide/[ide name] folder to make it cross ide.
Thanks,
Om
On Mar 17, 2015 6:14 AM, "Tom Chiverton" wrote:
> On 17/03/15 12:38, Darrell Loverin wrote:
>
>> I've been working on improving
On 17/03/15 12:38, Darrell Loverin wrote:
I've been working on improving the existing Code Coverage Tool in
utilities. I'm getting ready to commit the work but I'm not sure
whether to commit the Eclipse project files with the code. Are they
considered helpful or clutter?
I believe that the norm
Darrell,
Awesome news, I'm loving it!
As to the project files, I think the opinions are about 50% in favour,
50% against ;-) As an example: some of the SDK projects do have Flash
Builder project files, some don't.
Personally I like them in version control, as they give new
contributors an easier
I've been working on improving the existing Code Coverage Tool in
utilities. I'm getting ready to commit the work but I'm not sure whether to
commit the Eclipse project files with the code. Are they considered helpful
or clutter?
I've attached an example code coverage report from the tool I took w
