[
https://issues.apache.org/jira/browse/QUARKS-118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15235810#comment-15235810
]
ASF GitHub Bot commented on QUARKS-118:
---------------------------------------
GitHub user vdogaru opened a pull request:
https://github.com/apache/incubator-quarks/pull/85
QUARKS-118 Move JobRegistryService to quarks.execution.services
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vdogaru/incubator-quarks QUARKS-118-vdogaru
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-quarks/pull/85.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #85
----
commit 453a1c817a64eecb036d38dbc507e35715dce62b
Author: Victor Dogaru <[email protected]>
Date: 2016-04-11T19:39:00Z
QUARKS-118 Move JobRegistryService to quarks.execution.services
----
> Move JobRegistryService to quarks.execution.services?
> -----------------------------------------------------
>
> Key: QUARKS-118
> URL: https://issues.apache.org/jira/browse/QUARKS-118
> Project: Quarks
> Issue Type: Task
> Reporter: Daniel John Debrunner
> Assignee: Victor Dogaru
>
> At first I couldn't find the interface as I expected it to be in the standard
> services package quarks.execution.services.
> So should it be moved there, any reasons for it to have its own package?
> If it stays then a package-info.java is needed describing the package.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
