Creating a project - Code intelligence
Enable code intelligence: Upsource will be able to execute static code analysis in your repository and provide related features including displaying code issues, "Find usages", "Go to Declaration" etc.
With code intelligence enabled, specify the following:
Run code inspections: Upsource will detect and visualise compiler and runtime errors as well as less severe issues like typos or dead code. See Displaying code inspections in files for details.
- Choose Do not convert:
If an IDEA-based IDE is used to maintain code regardless of the build system, and if the project's .idea folder is committed into your repository (for example, if your project is built with Ant but you're using an IntelliJ IDEA-based IDE, then IntelliJ IDEA would be your choice of build system.).
If your team developers configure their IDE so each has different .idea folder, it's still recommended to store most of the .idea folder contents in version control, only omitting the user-specific settings, such as .idea/workspace.xml and .idea/shelf. Otherwise Upsource will not be able to provide code insight for your project.
- If Maven is selected as build system:
- Directory containing pom.xml: Enter a path to the parent _pom.xml_ file (relative to project root). Leave the field blank, if the file is in the root directory. If your project modules are hosted in multiple repositories (e.g. each module in their own repository), you can configure them all in one Upsource project, and keep the parent pom.xml in the first repo.
If you're planning to work on Gradle projects without a wrapper:
- In the
<upsource_home>/confdirectory, create a file
- Add the following line to that file:
gradle.home.directory=<gradle_home>. Use double backslashes in the specified path (e.g.
- Restart Upsource
Code insights can be extended if PHP Composer is used in your project. In order for Upsource to recognize it, the main Composer configuration file composer.json should be located in the root of the project repository.