ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Artem Shutak <ashu...@gridgain.com>
Subject Re: How to fix build failure Check License Headers (by RAT) (Maven
Date Thu, 27 Aug 2015 16:51:53 GMT
Ken,

See check-licenses profile at parent/pom.xml.

But I don't understand, why you see this exception as long as you didn't
add new files. Can you merge to you dev-branch last version of master and
check again?

-- Artem --

On Thu, Aug 27, 2015 at 7:39 PM, Ken Cheng <kcheng.mvp@gmail.com> wrote:

> Who can help to add the new .net/C++ code to the exclusion list?
>
> Thanks,
> kcheng
>
> On Fri, Aug 28, 2015 at 12:22 AM, Branko ─îibej <brane@apache.org> wrote:
>
> > On 27.08.2015 18:13, Ken Cheng wrote:
> > > Summary
> > > -------
> > > Generated at: 2015-08-28T00:09:54+08:00
> > > Notes: 0
> > > Binaries: 0
> > > Archives: 0
> > > Standards: 41
> > >
> > > Apache Licensed: 0
> > > Generated Documents: 0
> > >
> > > JavaDocs are generated and so license header is optional
> > > Generated files do not required license headers
> > >
> > > 1 Unknown Licenses
> > >
> > > *******************************
> > >
> > > Unapproved licenses:
> > >
> > >
> > >
> >
> /Users/kcheng/sandbox/ignite/modules/platform/src/main/dotnet/Apache.Ignite.sln.DotSettings
> >
> >
> >
> > Ah, that would be a side-effect of the new .net/C++ code import. The RAT
> > exclusion list needs to be updated.
> >
> > -- Brane
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message