In order to resolve the parent project, these possible sources are checked: relativePath local repository remote repositories The relative path, if not given explicitly, defaults to .., i.e. the pom in the parent directory of the current project. So Maven checks whether a) there is a pom file in that directory and b) that pom … Read more
IntelliJ 13 supports “refreshing” the Gradle project. When the project is refreshed any dependency changes are picked up as well as any changes to the project structure. In order to do so go to View -> Tool Windows and open the Gradle Tool Window you find the refresh button in the upper bar.
Found this when searching for “typescript references has not been built from source file”. My mistake was that I was running tsc -p tsconfig.json when I should’ve been using the –build flag: tsc –build tsconfig.json. If you run with -p TypeScript will not build the referenced projects. Only if you run with –build.
Try cleaning the Java language server workspace: Cmd + Shift + P (Ctrl + Shift + P on Windows) to show the command palette Choose “Java: Clean the Java language server workspace” Restart and Delete It just worked for me.
Update 19 March 2019 A new experience someone has just faced recently even though he/she did add a library module in app module, and include in Setting gradle as described below. One more thing worth trying is to make sure your app module and your library module have the same compileSdkVersion (which is in each … Read more
*.iml files have nothing to do with your code/Java. It is a hidden file created by Intellij on the root folder of your project which contains your module information. This is the reason you should not version this kind of file, afterall other developers using a different IDE won’t need them. If you closed Intellij, … Read more
A Package is basically a folder with __init__.py file under it and usually some Modules, where Module is a *.py file. It has to do with import mainly. If you add __init__.py to Indicators you can use: from Indicators.Stochastics import * or from Indicators import Stochastics By the way, I would recommend to keep module/package … Read more
I had this same issue, and fixed it by modifying my project’s .iml file: From: <content url=”file://$MODULE_DIR$”> <sourceFolder url=”file://$MODULE_DIR$/src/wrong/entry/here” isTestSource=”false” /> <sourceFolder url=”file://$MODULE_DIR$/test” isTestSource=”true” /> <excludeFolder url=”file://$MODULE_DIR$/target” /> </content> To: <content url=”file://$MODULE_DIR$”> <sourceFolder url=”file://$MODULE_DIR$/src” isTestSource=”false” /> <sourceFolder url=”file://$MODULE_DIR$/test” isTestSource=”true” /> <excludeFolder url=”file://$MODULE_DIR$/target” /> </content> Somehow a package folder became specified as the root source directory … Read more
To get a good start, you can use the bundle gem command and rspec –init. ~/code $ bundle gem my_lib create my_lib/Gemfile create my_lib/Rakefile create my_lib/LICENSE.txt create my_lib/README.md create my_lib/.gitignore create my_lib/my_lib.gemspec create my_lib/lib/my_lib.rb create my_lib/lib/my_lib/version.rb Initializating git repo in /Users/john/code/my_lib ~/code $ cd my_lib/ ~/code/my_lib $ git commit -m “Empty project” ~/code/my_lib $ rspec … Read more
I think that is pretty much spot on. By default, Rubygems will add the lib directory to the loadpath, but you can push any directory you want onto that using the $: variable. i.e. $:.push File.expand_path(File.dirname(__FILE__) + ‘/../surfcompstuff’) That means when you have say, surfer.rb in that dir, you can require “surfer” anywhere and the … Read more