undefined local variable or method `owner' for FastlaneCore::Helper::AppcenterHelper:Class (NameError) - fastlane

while I am trying to distribute the iOS app to appcenter Using Fastlane I am getting error like [!] undefined local variable or method `owner' for FastlaneCore::Helper::AppcenterHelper:Class (NameError).
+------+------------------+-------------+
| fastlane summary |
+------+------------------+-------------+
| Step | Action | Time (in s) |
+------+------------------+-------------+
| 💥 | appcenter_upload | 1 |
+------+------------------+-------------+
[11:49:06]: fastlane finished with errors
Looking for related GitHub issues on fastlane/fastlane...
➡️ appcenter upload error
https://github.com/fastlane/fastlane/issues/14907 [closed] 1 💬
5 days ago
🔗 You can ⌘ + double-click on links to open them directly in your browser.
/Users/capgemini/.gem/gems/fastlane-plugin-appcenter-1.0.1/lib/fastlane/plugin/appcenter/helper/appcenter_helper.rb:373:in get_app': [!] undefined local variable or methodowner' for FastlaneCore::Helper::AppcenterHelper:Class (NameError)
from /Users/capgemini/.gem/gems/fastlane-plugin-appcenter-1.0.1/lib/fastlane/plugin/appcenter/actions/appcenter_upload_action.rb:173:in get_or_create_app'
from /Users/capgemini/.gem/gems/fastlane-plugin-appcenter-1.0.1/lib/fastlane/plugin/appcenter/actions/appcenter_upload_action.rb:201:inrun'
from /Users/capgemini/.gem/gems/fastlane-2.125.2/fastlane/lib/fastlane/runner.rb:256:in block (2 levels) in execute_action'
from /Users/capgemini/.gem/gems/fastlane-2.125.2/fastlane/lib/fastlane/actions/actions_helper.rb:50:inexecute_action'
from /Users/capgemini/.gem/gems/fastlane-2.125.2/fastlane/lib/fastlane/runner.rb:235:in block in execute_action'
from /Users/capgemini/.gem/gems/fastlane-2.125.2/fastlane/lib/fastlane/runner.rb:227:inchdir'
from /Users/capgemini/.gem/gems/fastlane-2.125.2/fastlane/lib/fastlane/runner.rb:227:in execute_action'
from /Users/capgemini/.gem/gems/fastlane-2.125.2/fastlane/lib/fastlane/runner.rb:157:intrigger_action_by_name'
from /Users/capgemini/.gem/gems/fastlane-2.125.2/fastlane/lib/fastlane/fast_file.rb:154:in method_missing'
from Fastfile:51:inblock in parsing_binding'
from /Users/capgemini/.gem/gems/fastlane-2.125.2/fastlane/lib/fastlane/lane.rb:33:in call'
from /Users/capgemini/.gem/gems/fastlane-2.125.2/fastlane/lib/fastlane/runner.rb:49:inblock in execute'
from /Users/capgemini/.gem/gems/fastlane-2.125.2/fastlane/lib/fastlane/runner.rb:45:in chdir'
from /Users/capgemini/.gem/gems/fastlane-2.125.2/fastlane/lib/fastlane/runner.rb:45:inexecute'
from /Users/capgemini/.gem/gems/fastlane-2.125.2/fastlane/lib/fastlane/lane_manager.rb:56:in cruise_lane'
from /Users/capgemini/.gem/gems/fastlane-2.125.2/fastlane/lib/fastlane/command_line_handler.rb:36:inhandle'
from /Users/capgemini/.gem/gems/fastlane-2.125.2/fastlane/lib/fastlane/commands_generator.rb:108:in block (2 levels) in run'
from /Library/Ruby/Gems/2.3.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:178:incall'
from /Library/Ruby/Gems/2.3.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:153:in run'
from /Library/Ruby/Gems/2.3.0/gems/commander-fastlane-4.4.6/lib/commander/runner.rb:476:inrun_active_command'
from /Users/capgemini/.gem/gems/fastlane-2.125.2/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:76:in run!'
from /Library/Ruby/Gems/2.3.0/gems/commander-fastlane-4.4.6/lib/commander/delegates.rb:15:inrun!'
from /Users/capgemini/.gem/gems/fastlane-2.125.2/fastlane/lib/fastlane/commands_generator.rb:333:in run'
from /Users/capgemini/.gem/gems/fastlane-2.125.2/fastlane/lib/fastlane/commands_generator.rb:41:instart'
from /Users/capgemini/.gem/gems/fastlane-2.125.2/fastlane/lib/fastlane/cli_tools_distributor.rb:119:in take_off'
from /Users/capgemini/.gem/gems/fastlane-2.125.2/bin/fastlane:23:in'
from /Users/capgemini/.gem/bin/fastlane:22:in load'
from /Users/capgemini/.gem/bin/fastlane:22:in'

Take a look at the following link.
There is a error in the source code which hides the correct error. I also experienced that I got:
[!] undefined local variable or methodowner' for FastlaneCore::Helper::AppcenterHelper:Class (NameError)
No matter what I changed. My "real" error was that the app_name (and owner_name has hard to figured out) was wrong. This post helped me. Hopefully it can help you solve the real problem.

Related

Cannot run VSCode source code because its unable to find electron app in directory

Overview:
When I attempt to run VSCode with the instructions given in the contributions page to download all the packages, build the source code, and then run it all on the terminal, an error message pops up saying that I don't have the electron app in the vscode directory. Shouldn't have the electron app been installed when I ran the yarn command to install and build all the dependencies?
Steps to reproduce the bug:
$ yarn //building and installing all dependencies
$ yarn watchd //building vscode
$ ./scripts/code.sh //running vscode
Error Message:
Error launching app
Unable to find Electron app at /home/juan/Desktop/Projects/vscode
Cannot find module '/home/juan/Desktop/Projects/vscode/out/main'. Please verify that the package.json has a valid "main" entry
System Details:
CPUs | Intel(R) Core(TM) i7-6600U CPU # 2.60GHz (4 x 3200)
-- | --
GPU Status | 2d_canvas: unavailable_softwareflash_3d: disabled_softwareflash_stage3d: disabled_softwareflash_stage3d_baseline: disabled_softwaregpu_compositing: disabled_softwaremultiple_raster_threads: enabled_onoop_rasterization: disabled_offprotected_video_decode: disabled_offrasterization: disabled_softwareskia_renderer: disabled_off_okvideo_decode: disabled_softwareviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_off_okwebgl: unavailable_softwarewebgl2: unavailable_software
Load (avg) | 1, 1, 1
Memory (System) | 7.63GB (0.12GB free)
Process Argv | . --no-sandbox
Screen Reader | no
VM | 0%
OS|Ubuntu 18.04 LTS
Extensions:
Extension | Author (truncated) | Version
-- | -- | --
Bookmarks | ale | 11.2.0
vscode-sqlite | ale | 0.8.2
code-gnu-global | aus | 0.2.2
npm-intellisense | chr | 1.3.0
vscode-svgviewer | css | 2.0.0
vscode-markdownlint | Dav | 0.36.0
jshint | dba | 0.10.21
vscode-eslint | dba | 2.1.5
vscode-html-css | ecm | 0.2.3
EditorConfig | Edi | 0.15.1
vscode-npm-script | eg2 | 0.3.12
vscode-firefox-debug | fir | 2.8.0
beautify | Hoo | 1.5.0
vscode-emacs-friendly | lfs | 0.9.0
rainbow-csv | mec | 1.7.0
python | ms- | 2020.5.80290
cpptools | ms- | 0.28.2
debugger-for-chrome | msj | 4.12.8
sqltools | mtx | 0.22.5
material-icon-theme | PKi | 4.1.0
rust | rus | 0.7.8
lc2k | vio | 1.1.1
Here is the bug report I filled in the vscode github page: https://github.com/microsoft/vscode/issues/99537
I got this same error myself when the code did not build correctly.
In your second step you do:
yarn watchd
I tried this command myself, but ran into the same issue that you have stated here. Although the official wiki suggests this as a tip, I would just ignore it.
Instead, do either of these instead (this is what the official wiki originally suggest to do):
Type: Ctrl + Shift + B
Or alternatively use the Command Palette:
Type: Ctrl + Shift + P
Search for the option called: Tasks: Run Build Task and select it.
Once you start the build task you'll see a couple of things:
Firstly, at the bottom of VS Code (on your status line), VS Code will let you know the code is building.
Secondly, The build command will open two terminals:
Task - Build VS Code
Task - Build VS Code Extensions
Watch the output for both of terminals, make sure:
Task - Build VS Code terminal outputs: [some time] Finished compilation ...
and
Task - Build VS Code Extensions terminal outputs: [some time] Finished compilation extensions ...
If not and the build fails, you'll probably get a notification from VS code saying so (You'll probably get the error twice, one for each task):
yarn ... exited with code [some non-zero integer]
A common error that may occur is the ENOSPC error from inotify (also documented well in a medium blog). You'll want to issue this command:
echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p
Arch users would issue:
echo fs.inotify.max_user_watches=524288 | sudo tee /etc/sysctl.d/40-max-user-watches.conf && sudo sysctl --system
After fixing this, trying to build again should work. Start the build task again and make sure both tasks succeed. (You'll notice that the tasks do not end after they succeed. This is because they will watch for changes you make in the code while developing and automatically recompile for you).
If successful you may finally issue:
./scripts/code.sh
A new instance of VS Code should open called: Code - OSS dev. This is the version of VS Code you just built.

documenting error Jazzy "0% documentation coverage with 0 undocumented symbols"

So I'm trying to run Jazzy to document my code but I'm not getting very far.
This is what happens when i run Jazzy on my Xcode project written in swift(and some functions in # objc). Do i need to prepare the project in any way? I can't find anything about this, but it's my first time using Xcode and jazzy.
Can anyone tell me why it's not able to run properly am i doing something wrong while running the command?
jazzy
Running xcodebuild
Checking xcodebuild -showBuildSettings
Assuming New Build System is used.
Parsing AppDelegate.swift (1/4)
Parsing Card.swift (2/4)
Parsing SceneDelegate.swift (3/4)
Parsing ViewController.swift (4/4)
0% documentation coverage with 0 undocumented symbols
skipped 4 private, fileprivate, or internal symbols (use `--min-acl` to specify a different minimum ACL)
building site
building search index
jam out ♪♫ to your fresh new docs in `docs`
I tried doing jazzy --min-acl but this happens:
jazzy --min-acl
Traceback (most recent call last):
15: from /usr/local/bin/jazzy:23:in `<main>'
14: from /usr/local/bin/jazzy:23:in `load'
13: from /Library/Ruby/Gems/2.6.0/gems/jazzy-0.13.2/bin/jazzy:15:in `<top (required)>'
12: from /Library/Ruby/Gems/2.6.0/gems/jazzy-0.13.2/lib/jazzy/config.rb:442:in `parse!'
11: from /Library/Ruby/Gems/2.6.0/gems/jazzy-0.13.2/lib/jazzy/config.rb:485:in `parse_command_line'
10: from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/optparse.rb:1678:in `parse!'
9: from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/optparse.rb:1656:in `permute!'
8: from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/optparse.rb:1562:in `order!'
7: from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/optparse.rb:1568:in `parse_in_order'
6: from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/optparse.rb:1568:in `catch'
5: from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/optparse.rb:1582:in `block in parse_in_order'
4: from /Library/Ruby/Gems/2.6.0/gems/jazzy-0.13.2/lib/jazzy/config.rb:54:in `block in attach_to_option_parser'
3: from /Library/Ruby/Gems/2.6.0/gems/jazzy-0.13.2/lib/jazzy/config.rb:35:in `set'
2: from /Library/Ruby/Gems/2.6.0/gems/jazzy-0.13.2/lib/jazzy/config.rb:35:in `instance_exec'
1: from /Library/Ruby/Gems/2.6.0/gems/jazzy-0.13.2/lib/jazzy/config.rb:342:in `block in <class:Config>'
/Library/Ruby/Gems/2.6.0/gems/jazzy-0.13.2/lib/jazzy/source_declaration/access_control_level.rb:64:in `from_human_string': cannot initialize AccessControlLevel with '' (RuntimeError)
For the sake of people searching on google, when jazzy reports skipped items and generates 0% of documentation, invoke jazzy in the following way:
jazzy --min-acl <internal|fileprivate|private>
Swift is internal unless you specify the access otherwise.
Here is a link to the github readme discussing this topic: https://github.com/realm/jazzy#controlling-what-is-documented

Capistrano upload fails with incorrect arguments error?

I'm running
upload('bin/rvm_install.sh','~/rvm_install.sh')
in my Capistrano deploy script. And it's spitting out the following error:
capistrano-2.14.2/lib/capistrano/configuration/namespaces.rb:110:in `block in define_task': wrong number of arguments (2 for 0) (ArgumentError)
Why is this happening?
Changing
upload('bin/rvm_install.sh','~/rvm_install.sh')
to
top.upload('bin/rvm_install.sh','~/rvm_install.sh')
solved my problem.

Upgraded from Rails 2.3.5 to 2.3.11 and am getting this error now: "uninitialized constant AssignmentsPresenter::OrderedHash

After upgrading, when I try to login to my Rails app, I get the following:
NameError in ApplicationsController#index
uninitialized constant AssignmentsPresenter::OrderedHash
RAILS_ROOT: /Users/jasonbodak
Application Trace | Framework Trace | Full Trace
/Users/jasonbodak/.rvm/gems/ree-1.8.7-2011.03#janova-local_app/gems/activesupport-2.3.11/lib/active_support/dependencies.rb:131:in `const_missing'
/Users/jasonbodak/janova/janova/lib/assignments_presenter.rb:4:in `present'
/Users/jasonbodak/janova/janova/app/controllers/applications_controller.rb:12:in `index'
/Users/jasonbodak/.rvm/gems/ree-1.8.7-2011.03#janova-local_app/gems/actionpack-2.3.11/lib/action_controller/base.rb:1333:in `send'
/Users/jasonbodak/.rvm/gems/ree-1.8.7-2011.03#janova-local_app/gems/actionpack-2.3.11/lib/action_controller/base.rb:1333:in `perform_action_without_filters'
/Users/jasonbodak/.rvm/gems/ree-1.8.7-2011.03#janova-local_app/gems/actionpack-2.3.11/lib/action_controller/filters.rb:617:in `call_filters'
/Users/jasonbodak/.rvm/gems/ree-1.8.7-2011.03#janova-local_app/gems/actionpack-2.3.11/lib/action_controller/filters.rb:610:in `perform_action_without_benchmark'
/Users/jasonbodak/.rvm/gems/ree-1.8.7-2011.03#janova-local_app/gems/actionpack-2.3.11/lib/action_controller/benchmarking.rb:68:in `perform_action_without_rescue'
/Users/jasonbodak/.rvm/gems/ree-1.8.7-2011.03#janova-local_app/gems/activesupport-2.3.11/lib/active_support/core_ext/benchmark.rb:17:in `ms'
/Users/jasonbodak/.rvm/gems/ree-1.8.7-2011.03#janova-local_app/gems/activesupport-2.3.11/lib/active_support/core_ext/benchmark.rb:17:in `ms'
/Users/jasonbodak/.rvm/gems/ree-1.8.7-2011.03#janova-local_app/gems/actionpack-2.3.11/lib/action_controller/benchmarking.rb:68:in `perform_action_without_rescue'
/Users/jasonbodak/.rvm/gems/ree-1.8.7-2011.03#janova-local_app/gems/actionpack-2.3.11/lib/action_controller/rescue.rb:160:in `perform_action_without_flash'
/Users/jasonbodak/.rvm/gems/ree-1.8.7-2011.03#janova-local_app/gems/actionpack-2.3.11/lib/action_controller/flash.rb:151:in `perform_action'
/Users/jasonbodak/.rvm/gems/ree-1.8.7-2011.03#janova-local_app/gems/actionpack-2.3.11/lib/action_controller/base.rb:532:in `send'
/Users/jasonbodak/.rvm/gems/ree-1.8.7-2011.03#janova-local_app/gems/actionpack-2.3.11/lib/action_controller/base.rb:532:in `process_without_filters'
/Users/jasonbodak/.rvm/gems/ree-1.8.7-2011.03#janova-local_app/gems/actionpack-2.3.11/lib/action_controller/filters.rb:606:in `process'
/Users/jasonbodak/.rvm/gems/ree-1.8.7-2011.03#janova-local_app/gems/actionpack-2.3.11/lib/action_controller/base.rb:391:in `process'
/Users/jasonbodak/.rvm/gems/ree-1.8.7-2011.03#janova-local_app/gems/actionpack-2.3.11/lib/action_controller/base.rb:386:in `call'
/Users/jasonbodak/.rvm/gems/ree-1.8.7-2011.03#janova-local_app/gems/actionpack-2.3.11/lib/action_controller/routing/route_set.rb:438:in `call'
Request
Parameters:
None
Show session dump
Response
Headers:
{"Content-Type"=>"",
"Cache-Control"=>"no-cache"}
Does this mean anything to anyone? Thanks.
OK, I figured it out. I don't know why upgrading Rails from 2.3.5 to 2.3.11 did this, but I had to change the line assignments_by_status = OrderedHash.new to assignments_by_status = ActiveSupport::OrderedHash.new and now it works just fine.

Can't deploy Play application into Heroku

I'm having issues deploying a Play application into Heroku. I've had no problems deploying other basic applications without modules, but this one is giving me the following error:
#ubuntu:~/$ git push heroku master
Counting objects: 812, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (699/699), done.
Writing objects: 100% (794/794), 2.00 MiB, done.
Total 794 (delta 145), reused 0 (delta 0)
-----> Heroku receiving push
-----> Play! app detected
-----> Installing ivysettings.xml..... done
-----> Building Play! application...
~ _ _
~ _ __ | | __ _ _ _| |
~ | '_ \| |/ _' | || |_|
~ | __/|_|\____|\__ (_)
~ |_| |__/
~
~ play! 1.2.3, http://www.playframework.org
~
1.2.3
Play! application root found at ./mods/playcopy/crud-1.2.3/
./mods/playcopy/greenscript-1.2.6h/samples-and-tests/use-gs-in-tags/
./mods/playcopy/greenscript-1.2.6h/samples-and-tests/demo/
./mods/playcopy/greenscript-1.2.6h/samples-and-tests/inline-dependency-declaring/
./mods/playcopy/greenscript-1.2.6h/samples-and-tests/jquery-ui/
./mods/playcopy/greenscript-1.2.6h/samples-and-tests/booking/
./mods/playcopy/greenscript-1.2.6h/samples-and-tests/less-and-coffee/
./mods/playcopy/greenscript-1.2.6h/samples-and-tests/chat/
./mods/playcopy/greenscript-1.2.6h/
./
Resolving dependencies: .play/play dependencies ./mods/playcopy/crud-1.2.3/
./mods/playcopy/greenscript-1.2.6h/samples-and-tests/use-gs-in-tags/
./mods/playcopy/greenscript-1.2.6h/samples-and-tests/demo/
./mods/playcopy/greenscript-1.2.6h/samples-and-tests/inline-dependency-declaring/
./mods/playcopy/greenscript-1.2.6h/samples-and-tests/jquery-ui/
./mods/playcopy/greenscript-1.2.6h/samples-and-tests/booking/
./mods/playcopy/greenscript-1.2.6h/samples-and-tests/less-and-coffee/
./mods/playcopy/greenscript-1.2.6h/samples-and-tests/chat/
./mods/playcopy/greenscript-1.2.6h/
./ --forceCopy --silent -Duser.home=/tmp/build_1hn7e8ahaqrso 2>&1
~ Resolving dependencies using /tmp/build_1hn7e8ahaqrso/mods/playcopy/crud-1.2.3/conf/dependencies.yml,
~
~
~ No dependencies to install
~
~ Done!
~
~ _ _
~ _ __ | | __ _ _ _| |
~ | '_ \| |/ _' | || |_|
~ | __/|_|\____|\__ (_)
~ |_| |__/
~
~ play! 1.2.3, http://www.playframework.org
~
/app/slug-compiler/lib/../language_packs/play/bin/compile: line 64: ./mods/playcopy/greenscript-1.2.6h/samples-and-tests/use-gs-in-tags/: is a directory
/app/slug-compiler/lib/../language_packs/play/bin/compile: line 65: ./mods/playcopy/greenscript-1.2.6h/samples-and-tests/demo/: is a directory
/app/slug-compiler/lib/../language_packs/play/bin/compile: line 66: ./mods/playcopy/greenscript-1.2.6h/samples-and-tests/inline-dependency-declaring/: is a directory
/app/slug-compiler/lib/../language_packs/play/bin/compile: line 67: ./mods/playcopy/greenscript-1.2.6h/samples-and-tests/jquery-ui/: is a directory
/app/slug-compiler/lib/../language_packs/play/bin/compile: line 68: ./mods/playcopy/greenscript-1.2.6h/samples-and-tests/booking/: is a directory
/app/slug-compiler/lib/../language_packs/play/bin/compile: line 69: ./mods/playcopy/greenscript-1.2.6h/samples-and-tests/less-and-coffee/: is a directory
/app/slug-compiler/lib/../language_packs/play/bin/compile: line 70: ./mods/playcopy/greenscript-1.2.6h/samples-and-tests/chat/: is a directory
/app/slug-compiler/lib/../language_packs/play/bin/compile: line 71: ./mods/playcopy/greenscript-1.2.6h/: is a directory
/app/slug-compiler/lib/../language_packs/play/bin/compile: line 72: ./: is a directory
! Failed to build Play! application
! Cleared Play! framework from cache
/app/slug-compiler/lib/language_pack.rb:35:in `block in compile': failed to compile Play! app (Slug::CompileError)
from /app/slug-compiler/lib/language_pack.rb:32:in `fork'
from /app/slug-compiler/lib/language_pack.rb:32:in `compile'
from /app/slug-compiler/lib/slug.rb:490:in `block in run_language_pack'
from /app/slug-compiler/lib/utils.rb:117:in `log'
from /app/slug-compiler/lib/slug.rb:727:in `log'
from /app/slug-compiler/lib/slug.rb:489:in `run_language_pack'
from /app/slug-compiler/lib/slug.rb:110:in `block (2 levels) in compile'
from /app/slug-compiler/lib/utils.rb:98:in `block in timeout'
from /usr/local/lib/ruby/1.9.1/timeout.rb:57:in `timeout'
from /app/slug-compiler/lib/utils.rb:98:in `rescue in timeout'
from /app/slug-compiler/lib/utils.rb:93:in `timeout'
from /app/slug-compiler/lib/slug.rb:99:in `block in compile'
from /app/slug-compiler/lib/utils.rb:117:in `log'
from /app/slug-compiler/lib/slug.rb:727:in `log'
from /app/slug-compiler/lib/slug.rb:98:in `compile'
from /app/slug-compiler/bin/slugc:85:in `block in <main>'
from /app/slug-compiler/lib/slug.rb:498:in `block in lock'
from /app/slug-compiler/lib/repo_lock.rb:44:in `call'
from /app/slug-compiler/lib/repo_lock.rb:44:in `run'
from /app/slug-compiler/lib/slug.rb:498:in `lock'
from /app/slug-compiler/bin/slugc:66:in `<main>'
-----> Discovering process types
Procfile declares types -> web
-----> Compiled slug size is 36.4MB
-----> Launching... done, v6
http://billeteo.herokuapp.com deployed to Heroku
To git#heroku.com:billeteo.git
53b789c..24f66a4 master -> master
Although I'm running from the root of my project, Heroku believes that my root is at:
Play! application root found at ./mods/playcopy/crud-1.2.3/
which, of course, doesn't contain the code and the process fails.
My application is standard Play app with the following dependencies.xml:
# Application dependencies
# Notes:
# play is an alias for play -> play $currentVersion
# play -> crud is an alias for play -> crud $currentVersion
# play -> secure is an alias for play -> secure $currentVersion
# Modules from the main repository use 'play' as organisation
require:
- play
- playcopy -> crud 1.2.3
- playcopy -> betterlogs 1.0
- playcopy -> cobertura 2.1
- playcopy -> mockito 0.1
- playcopy -> greenscript 1.2.6h
- custom -> useragentcheck 1.0
- org.hibernate -> hibernate-search 3.4.0.Final
repositories:
- localModules:
type: local
artifact: "${application.path}/mods/[organisation]/[module]-[revision]"
contains:
- playcopy
- custom
I'm using a local repository for some official Play modules as they may have some custom code (remove some unnecessary classes, change security, some logs, etc).
Anyone knows how to make Heroku find the right root? Could not find anything on Google...
The Play setup on Heroku didn't anticipate your particular setup here. Like you indicated, it's confused about where the root of your application is. I think we can push a fix to resolve this, but in the mean time, you should be able to work around it. Try this:
Zip your custom modules and change your dependencies.yml file to
...
repositories:
- localModules:
type: local
artifact: "${application.path}/mods/[organisation]/[module]-[revision].zip"
contains:
- playcopy
- custom
...
During dependency resolution, Play should unzip your custom modules and put them in the right place. Also, Heroku shouldn't get confused about where the root of your app is.