[
https://issues.apache.org/jira/browse/OOZIE-1702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15879058#comment-15879058
]
Eva Andreasson commented on OOZIE-1702:
---------------------------------------
There seems to be (at least in my recently cleaned up build environment) three
types of warnings:
1. The build system detecting a non-regular file
2. The build system detects an entry longer than 100 characters
3. Patterns not triggered in exclusion filters
I will attach a file with the full list of warnings, grouped into the three
categories.
However, since I don't know Oozie build system or code too well I need advise
on two matters:
a) where do the code triggering these warnings reside? I could not find them
easily.
b) what would be the best practice for each of these warnings?
1 - change the file description or format or the build process?
2 - change the character length accept level or change the path names/file
names to fit the limit?
3 - what is the purpose of warning on non-triggered patterns?
> Reduce warnings thrown while building
> -------------------------------------
>
> Key: OOZIE-1702
> URL: https://issues.apache.org/jira/browse/OOZIE-1702
> Project: Oozie
> Issue Type: Wish
> Components: build
> Affects Versions: trunk
> Reporter: Mona Chitnis
> Priority: Minor
> Labels: documentation, newbie
>
> A lot of warnings are thrown during Oozie compilation, complaining about
> javadoc mistakes, missing links etc among probably other severe ones. This
> clutters the output. This JIRA is to fix these warnings
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
