[ 
https://issues.apache.org/jira/browse/LUCENE-4332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Greg Bowyer updated LUCENE-4332:
--------------------------------

    Attachment: 
LUCENE-4332-Integrate-PiTest-mutation-coverage-tool-into-build.patch

I found and fixed a few things relating to security policies (ha!)

Also I thought about the javascript a bit, I know thats its standard in the JVM 
but when I tested on a 1.6 I found that my javascript was a bit too advanced 
for it.

That made me pause for thought and realise that I might have been a bit too 
clever for my own good there; I am not all that happy with the the JS so I went 
with the ugly approach for now.

It think the right solution is to work with the pitest people and get it to 
support junit style nested tags like sysproperty
                
> Integrate PiTest mutation coverage tool into build
> --------------------------------------------------
>
>                 Key: LUCENE-4332
>                 URL: https://issues.apache.org/jira/browse/LUCENE-4332
>             Project: Lucene - Core
>          Issue Type: Improvement
>    Affects Versions: 4.1, 5.0
>            Reporter: Greg Bowyer
>            Assignee: Greg Bowyer
>              Labels: build
>         Attachments: 
> LUCENE-4332-Integrate-PiTest-mutation-coverage-tool-into-build.patch, 
> LUCENE-4332-Integrate-PiTest-mutation-coverage-tool-into-build.patch, 
> LUCENE-4332-Integrate-PiTest-mutation-coverage-tool-into-build.patch, 
> LUCENE-4332-Integrate-PiTest-mutation-coverage-tool-into-build.patch
>
>
> As discussed briefly on the mailing list, this patch is an attempt to 
> integrate the PiTest mutation coverage tool into the lucene build

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to