batchee-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (BATCHEE-121) Make the default CLI lifecycle configurable
Date Fri, 23 Jun 2017 14:12:00 GMT

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

Hudson commented on BATCHEE-121:
--------------------------------

SUCCESS: Integrated in Jenkins build batchee #640 (See [https://builds.apache.org/job/batchee/640/])
BATCHEE-121 add a way to define a lifecycle via system properties (struberg: rev a07bf2c7c515da3eb783d3628dc7836160ceb467)
* (edit) tools/cli/src/main/java/org/apache/batchee/cli/command/JobOperatorCommand.java


> Make the default CLI lifecycle configurable
> -------------------------------------------
>
>                 Key: BATCHEE-121
>                 URL: https://issues.apache.org/jira/browse/BATCHEE-121
>             Project: BatchEE
>          Issue Type: Bug
>          Components: CLI
>    Affects Versions: 0.4-incubating
>            Reporter: Mark Struberg
>            Assignee: Mark Struberg
>             Fix For: 0.5-incubating
>
>
> Currently one has to define a lifecycle for batches in the CLI manually.
> But some batches do exactly know the lifecylce they need to run with.
> So it would be great if they could declare that intent in batchee.properties already.
> The decision tree would be
> * -lifecycle bla parameter on the CLI
> * if not given -> read org.apache.batchee.cli.lifecycle=bla from System.getProperties
> * if still not given -> run without Lifecycle
> Side note: we cannot use batchee.properties as those are most times just given inside
the -archive, e.g a mybatch.war
> But this archive is not yet in the ClassPath at this point in time.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message