My guess is it's not ignoring that target directory because the hbase app
package is no longer listed as a submodule in the top level pom file.
On Jul 8, 2014 10:58 AM, "Steve Loughran" <ste...@hortonworks.com> wrote:

> that's RAT isn't it?
>
> you need to update the org.apache.rat plugin in pom.xml with a pattern that
> gets rid of the noise. I'm surprised it's picking up stuff in target/
> though ... I don't see filters for this in the other projects
>
>
> On 8 July 2014 18:53, Ted Yu <yuzhih...@gmail.com> wrote:
>
> > Hi,
> > Once I produce app package for hbase, the next build would complain about
> > the following.
> >
> > Unapproved licenses:
> >
> >
> app-packages/hbase/target/archive-tmp/appConfig.json.1746534752.filtered
> >   app-packages/hbase/target/archive-tmp/appConfig.json.727813455.filtered
> >
> >
> >
> app-packages/hbase/target/maven-status/maven-compiler-plugin/testCompile/default-testCompile/createdFiles.lst
> >
> >
> >
> app-packages/hbase/target/maven-status/maven-compiler-plugin/testCompile/default-testCompile/inputFiles.lst
> >
> >
> >
> app-packages/hbase/target/failsafe-reports/TEST-org.apache.slider.funtest.hbase.HBaseMonitorSSLIT.xml
> >
> >
> >
> app-packages/hbase/target/failsafe-reports/TEST-org.apache.slider.funtest.hbase.HBaseBasicIT.xml
> >
> >
> >
> app-packages/hbase/target/failsafe-reports/org.apache.slider.funtest.hbase.HBaseMonitorSSLIT.txt
> >
> >
> >
> app-packages/hbase/target/failsafe-reports/org.apache.slider.funtest.hbase.HBaseBasicIT.txt
> >   app-packages/hbase/target/failsafe-reports/failsafe-summary.xml
> >
> > Suggestion on how these build output should be excluded from rat check is
> > welcome.
> >
> > Thanks
> >
>
> --
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity to
> which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified that
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. Thank You.
>

Reply via email to