[
https://issues.apache.org/jira/browse/OFBIZ-7796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15420762#comment-15420762 ]
Jacques Le Roux commented on OFBIZ-7796:
----------------------------------------
Actually as Taher suggested, in production you can change the repository and not use jcenter but your own, this to avoid possible issues on jcenter. You though need to prodive a well formated repository. Accordind to
https://docs.gradle.org/current/userguide/artifact_dependencies_tutorial.html#N10660
bq. A repository is really just a collection of files, organized by group, name and version. Gradle understands several different repository formats, such as Maven and Ivy, and several different ways of accessing the repository, such as using the local file system or HTTP.
> Running OFBiz as a service fails
> --------------------------------
>
> Key: OFBIZ-7796
> URL:
https://issues.apache.org/jira/browse/OFBIZ-7796> Project: OFBiz
> Issue Type: Sub-task
> Affects Versions: Trunk
> Environment: Ubuntu 16.04, openjdk-8-jdk
> Reporter: Pierre Smits
> Assignee: Pierre Smits
> Priority: Minor
> Attachments: OFBIZ-77796-rc.ofbiz.for.debian.patch, OFBIZ-7796-rc.ofbiz.for.debian-v2.patch
>
>
> In a new ubuntu environment I performed a checkout from trunk and ran the loadDefault build script.
> After this had completed, I moved the ofbiz directory from my user folder to the /opt folder, and configured the Ubuntu environment to be able to run OFBiz as a service.
> This entails:
> * deploy a script in /etc/init.d
> * set the correct permissions of the service script
> * create the service user
> * changed the owner and ownergroup of the files and folders in /opt/ofbiz
> and then fire the service:
> sudo /etc/init.d/ofbiz start
> This normally starts the proces java -jar ofbiz.jar
> But now nothing happens.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Locked
