dependencies - How do I reference play framework third party modules without referencing an absolute path? -
This is my position I have a play app that uses to work with the navigation module:
- I've installed it using the
install button . It does this in the
$ PLAY_HOME / module which is fine by me, I do not want to edit the module files in any way.
- Then I announced the module in my
dependencies.yml :
- play -> Guice 1.2
- Within my app, I used to run
playback dependency , and this module runs properly and has a
modules / guice-1.2 < / Code creates> file that references the navigation module.
The problem is that the content of that file is something like the following:
/some-absolute-path/play-1.2.x/ module / guide-1.2 .
This works fine when working locally for development. But when I want to go to a production server with a different play!
So what's the best way to deal with this?
For now, I have resorted to declaring the module in the
application.conf file like this:
module.guice = $ {play.path} /modules/guice-1.2 . Unfortunately,
$ {play.path} magic does not work on those generated files.
The way I use version 1.2.3!
You should try with $ {application.path} in your dependencies.yml file, such as In this example,
is required: - Play - & gt; Crud - Provide - & gt; DateHelper 1.0 Repositories: - Provided: Type: Local Artifact: "$ {application.path} / Jar / [Module] - [Modification] .jar" includes: - provided - & gt; *
See this question:
- Then I announced the module in my
Comments
Post a Comment