You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "#asfinfra Bot (JIRA)" <ji...@apache.org> on 2016/07/17 07:55:21 UTC

[jira] [Closed] (INFRA-11698) Update clover.license

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

#asfinfra Bot closed INFRA-11698.
---------------------------------
    Resolution: Won't Fix  (was: Unresolved)

Hi, 

This issue has been in state 'Pending Closed' for at least 5 days, and was previously waiting for at least 3 days for waiting for updates. 
  
We are closing this issue automatically, feel free to reopen the issue or open a new one should you need further help.


-- 
Cheers,
Apache Infrastructure Team

> Update clover.license
> ---------------------
>
>                 Key: INFRA-11698
>                 URL: https://issues.apache.org/jira/browse/INFRA-11698
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Jenkins
>            Reporter: Allen Wittenauer
>            Assignee: Gavin
>
> I was playing around a bit today and noticed that the clover license in /home/jenkins/tools/clover/latest/lib/clover.license is extremely out of date.  I'm guessing no one is using it?  Is there some other location that is supposed to be used to get a valid license?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)