[
https://issues.apache.org/jira/browse/ATLAS-318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15135883#comment-15135883
]
Selvamohan Neethiraj commented on ATLAS-318:
--------------------------------------------
The above comment is from an automated patch validation process. This will
ensure that,
(a) The patch can be applied on master branch successfully w/out any error
(b) Has one or more Junit test cases - added/modified to validate the change
(c) No javac compilation warnings are added - due to the patch [It compares
the javac warnings before and after the patch]
(d) No javadoc warnings are introduced by the patch
(e) No findbugs warnings are introduced by the patch
(f) No Release Audit failures (like not having apache license headers in
source) due to the patch
(g) No JUNIT tests are failing after applying the patch
This automated test is run on any patch that are attached to ATLAS jira -
marked with PATCH_AVAIL status
You should check and fix the patch and attach again to the JIRA and the
validation process should automatically run and provides the feedback again.
You should check-in the patch only if:
(a) you get +1 for over-all patch
OR
(b) Have one of the ATLAS committers (other than the patch provider) to provide
a +1 with enough justification.
> UI. Config file conatining UI: API endpoint + all api calls to be centralized
> -- config JS file for stand alone
> ---------------------------------------------------------------------------------------------------------------
>
> Key: ATLAS-318
> URL: https://issues.apache.org/jira/browse/ATLAS-318
> Project: Atlas
> Issue Type: Task
> Reporter: roshni gadiyar
> Assignee: Darshan Kumar
> Priority: Minor
> Labels: Atlas-UI
> Attachments: ATLAS-318.patch
>
>
> Config file conatining API endpoint + all api calls to be centralized --
> config JS file for stand alone UI.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
