[ 
https://issues.apache.org/jira/browse/OOZIE-669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13456278#comment-13456278
 ] 

Hadoop QA commented on OOZIE-669:
---------------------------------

Testing JIRA OOZIE-669

Cleaning local svn workspace

{code}
----------------------------

+1 PATCH_APPLIES
   CLEAN cleaned target directories
-1 RAW_PATCH_ANALYSIS
    +1 the patch does not introduce any @author tags
    +1 the patch does not introduce any tabs
    +1 the patch does not introduce any trailing spaces
    +1 the patch does not introduce any line longer than 132
    -1 the patch does not add/modify any testcase
+1 RAT
    +1 the patch does not seem to introduce new RAT warnings
+1 JAVADOC
    +1 the patch does not seem to introduce new Javadoc warnings
+1 COMPILE
    +1 HEAD compiles
    +1 patch compiles
    +1 the patch does not seem to introduce new javac warnings
+1 BACKWARDS_COMPATIBILITY
    +1 the patch does not change any JPA Entity/Colum/Basic/Lob/Transient 
annotations
    +1 the patch does not modify JPA files
+1 TESTS
   Tests run: 910
   Tests failures: 0
   Tests errors: 0
+1 DISTRO
    +1 distro tarball builds with the patch 

----------------------------
{code}

The full output of the test-patch run is available at

   https://builds.apache.org/job/oozie-trunk-precommit-build/100/
                
> Remove oozie-start.sh, oozie-stop.sh & oozie-run.sh scripts, leaving oozied.sh
> ------------------------------------------------------------------------------
>
>                 Key: OOZIE-669
>                 URL: https://issues.apache.org/jira/browse/OOZIE-669
>             Project: Oozie
>          Issue Type: Improvement
>            Reporter: Alejandro Abdelnur
>            Assignee: Robert Kanter
>         Attachments: OOZIE-669.patch
>
>
> The start/stop/run scripts just delegate to the oozied script.
> This woud simplify usage a& documentation.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to