Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
engine
engine
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 3
    • Issues 3
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Pulse Physiology Suite
  • engineengine
  • Issues
  • #20

Closed
Open
Created Mar 24, 2020 by marinier@marinierDeveloper

Make location of substances and compounds customizable

In Java, the SESubstanceManager class loads the substances and compounds via the loadSubstanceDirectory() method. This method hard-codes the path to the substances and compounds directories as relative to the working directory. This method is called internally by Pulse when PulseEngine.initializeEngine(...) is called.

The problem is that when deploying a java application, how these directories are packaged with the application may require them to be elsewhere. Additionally, the current working directory cannot be reliably changed from within Java. Changing the user.dir system property and even using jnr-posix to change the directory from the OS side did not work. (I'm using Java 11 64-bit on Windows 10.)

Perhaps a configuration file or additional params to initializeEngine() could allow the location to be specified.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None