One hack I have found is to add, inside the subprojects block of
the build.gradle file, the following task
task copyResourcesToIntelliJOutFolder(type: Copy) {
from "$subProject.buildDir/resources/test"
into 'out/test/resources'
}
Then in the IntelliJ gradle tool window locate the tas
With the new version of IntelliJ the only way I found to run tests from
inside the IDE is to override the hibernate.properties file in the
out/test/resources folder with the one in target/resources/test generated
by gradle
On 12 October 2017 at 13:22, Steve Ebersole wrote:
> I just upgraded to I
Hi,
Looks like IDEA rebuilds the project and generates the @db.dialect@ issue.
I tackled it with the following Bash script:
@echo off
> set db=%1
> set module="hibernate-core"
> if not "%2"=="" SET module="hibernate-%2"
> if "%2"=="doc" SET module="documentation"
> set target="d:\Vlad\Work\GitHu
Hi Steve,
Had the same issue. https://youtrack.jetbrains.com/issue/IDEA-175172
I solved it by running the processTestResources task and copying the
properties file from the build folder to the out folder.
Hope it helps!
Best,
Arnold
On Thu, Oct 12, 2017 at 2:22 PM, Steve Ebersole wrote:
> I
I just upgraded to IntelliJ 2017.3 EAP and am back to this frustrating
"Dialect class not found: @db.dialect@" problem. I run the
`processTestResources` (or `compile`, does not matter) and then when I try
to run a test in the IDE I get this error.
What is the magic incantation I am missing?
_
