mirror of
https://gitflic.ru/project/openide/openide.git
synced 2026-02-05 16:36:56 +07:00
f0dbb9a634
By convention, we use 'testFramework' suffix for modules containing common testing code in production source roots, and 'tests' suffix for modules containing actual tests only. Let's follow this convention in devkit for consistency and to simplify writing tests on project structure. GitOrigin-RevId: 23d78b951c0dcf04e388e83f5fc6d71fe1a59a5b
23 lines
1.3 KiB
XML
23 lines
1.3 KiB
XML
<?xml version="1.0" encoding="UTF-8"?>
|
|
<module type="JAVA_MODULE" version="4">
|
|
<component name="NewModuleRootManager" inherit-compiler-output="true">
|
|
<exclude-output />
|
|
<content url="file://$MODULE_DIR$">
|
|
<sourceFolder url="file://$MODULE_DIR$/testSrc" isTestSource="true" />
|
|
<sourceFolder url="file://$MODULE_DIR$/testData" type="java-test-resource" />
|
|
</content>
|
|
<orderEntry type="inheritedJdk" />
|
|
<orderEntry type="sourceFolder" forTests="false" />
|
|
<orderEntry type="library" name="jetbrains-annotations" level="project" />
|
|
<orderEntry type="module" module-name="intellij.xml.psi.impl" scope="TEST" />
|
|
<orderEntry type="module" module-name="intellij.spellchecker" scope="TEST" />
|
|
<orderEntry type="module" module-name="intellij.xml.analysis.impl" scope="TEST" />
|
|
<orderEntry type="module" module-name="intellij.devkit.testFramework" />
|
|
<orderEntry type="module" module-name="intellij.platform.testFramework" scope="TEST" />
|
|
<orderEntry type="module" module-name="intellij.properties" />
|
|
<orderEntry type="module" module-name="intellij.platform.core.ui" />
|
|
<orderEntry type="module" module-name="intellij.properties.psi.impl" />
|
|
<orderEntry type="library" name="CGLIB" level="project" />
|
|
<orderEntry type="library" name="org.codehaus.groovy:groovy" level="project" />
|
|
</component>
|
|
</module> |