[ 
https://issues.apache.org/jira/browse/LUCENE-8169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16359935#comment-16359935
 ] 

Uwe Schindler commented on LUCENE-8169:
---------------------------------------

I committed some updates that I missed to do:
- We no longer need to limit ourselves to {{org.apache}} package names, as 
OpenClover needs no license (the previous license was limited to Apache code). 
This affected Tartarus Snowball, which is now also instrumented.
- I removed a permgen setting, which is obsolete with Java 8.
- I also updated the link to the issue that OpenNLP faces: 
https://bitbucket.org/openclover/clover/issues/59 (OpenClover cannot instrument 
code with multi-dimensional array constructor references).

> Migrate build to use OpenClover 4.2.1
> -------------------------------------
>
>                 Key: LUCENE-8169
>                 URL: https://issues.apache.org/jira/browse/LUCENE-8169
>             Project: Lucene - Core
>          Issue Type: Task
>          Components: general/build
>            Reporter: Uwe Schindler
>            Assignee: Uwe Schindler
>            Priority: Major
>              Labels: clover
>             Fix For: master (8.0), 7.3
>
>         Attachments: LUCENE-8169.patch, LUCENE-8169.patch
>
>
> Last year, Atlassian opensourced Clover and stopped releasing new versions. 
> Latest supported version is 4.1.2: 
> https://www.atlassian.com/blog/announcements/atlassian-clover-open-source
> After opensourcing it was foked and OpenClover was founded: 
> http://openclover.org/
> The latest OpenClover version is 4.2.1.
> This will issue will migrate to the opensourced OpenClover 4.2.1 version 
> (also in preparation for Java 9). It will mainly remove the license file and 
> cleans up the build to no longer refer to it.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

Reply via email to