Re: vhostTest is not detected as a Test dir
Niclas Hedhman a écrit : > What happens is that src/perf and src/vhost-test are "Sources" (blue) > directories instead of "Tests" (green) directories. Yeah, I get that too. Not a big issue. > Dependencies were incorrect, so that dnsjava was not seen. But, dependencies are correct and I can navigate to dnsjava source code. Maybe Jetbrains fixed some stuff between 2016.2 and 2016.3.
Re: vhostTest is not detected as a Test dir
What happens is that src/perf and src/vhost-test are "Sources" (blue) directories instead of "Tests" (green) directories. Dependencies were incorrect, so that dnsjava was not seen. On Wed, Dec 7, 2016 at 7:30 PM, Paul Merlinwrote: > Niclas Hedhman a écrit : > > I also don't use the plugin, but open the build.gradle file directly. > > > > I am on Intellij 2016.2.4 UE > > Using 2016.3 CE here, but it *should* work with 2016.2.4 UE. > > What exactly is happening after import for the vhost and perf tests? > Dependencies are missing and source code is all red? > > > > Niclas Hedhman a écrit : > > Also, instead of a vhost-test, why not have tests/jdk8 and tests/jdk9 > which > > are specific tests for each platform? > I'm not sure we'll have much tests like that. > At least not until we tackle jigsaw support. > And some built-in support for this is coming into Gradle soon. > > -- Niclas Hedhman, Software Developer http://zest.apache.org - New Energy for Java
Re: vhostTest is not detected as a Test dir
Niclas Hedhman a écrit : > I also don't use the plugin, but open the build.gradle file directly. > > I am on Intellij 2016.2.4 UE Using 2016.3 CE here, but it *should* work with 2016.2.4 UE. What exactly is happening after import for the vhost and perf tests? Dependencies are missing and source code is all red? Niclas Hedhman a écrit : > Also, instead of a vhost-test, why not have tests/jdk8 and tests/jdk9 which > are specific tests for each platform? I'm not sure we'll have much tests like that. At least not until we tackle jigsaw support. And some built-in support for this is coming into Gradle soon.
Re: vhostTest is not detected as a Test dir
Also, instead of a vhost-test, why not have tests/jdk8 and tests/jdk9 which are specific tests for each platform? On Wed, Dec 7, 2016 at 7:22 PM, Niclas Hedhmanwrote: > I also don't use the plugin, but open the build.gradle file directly. > > I am on Intellij 2016.2.4 UE > > On Wed, Dec 7, 2016 at 7:20 PM, Paul Merlin wrote: > >> To get the project into IDEA, I just import it directly from IDEA and I >> don't get any dependency trouble. >> >> I'm not using ./gradlew idea anymore. >> >> >> Niclas Hedhman a écrit : >> > The same problem exists for src/perf/java in tests/performance. >> > >> > Could we name this back to src/test? >> > >> > And if so, should we move the vhostTest stuff to a tests/vhost as well? >> > >> > >> > The above assumes that Paul doesn't have a "Oh, just do..." answer to >> this >> > issue. >> > >> > >> > Cheers >> > Niclas >> > >> > On Wed, Dec 7, 2016 at 5:22 PM, Niclas Hedhman >> wrote: >> > >> >> Paul, >> >> isn't it cool that we have a Gradle expert in the team :-) >> >> >> >> Your very elaborate handling of JDK 9 in libraries/http creates a >> problem >> >> in the IDEA-Gradle integration. >> >> >> >> The vhostTest sourceSet is recognized as a "main/java" and not >> "test/java" >> >> in IntelliJ. I have no idea where to start looking, in our build >> script, in >> >> gradle or IntelliJ. Did some naive searches on Google, but could only >> find >> >> something somewhat related, but not, https://discuss.gradle.org/t/ >> >> intellij-dependencies-not-appearing-with-custom-configuration/5757 >> >> >> >> And it is quite bad, because it will not bring in the dnsjava >> dependency, >> >> so even if I change it manualy to a "test/java" it is not resolved, >> and as >> >> soon as the dependencies are recomputed, we are back to "src/java". >> >> >> >> Any ideas? >> >> >> >> Cheers >> >> -- >> >> Niclas Hedhman, Software Developer >> >> http://zest.apache.org - New Energy for Java >> >> >> > >> > >> > >> > > > > -- > Niclas Hedhman, Software Developer > http://zest.apache.org - New Energy for Java > -- Niclas Hedhman, Software Developer http://zest.apache.org - New Energy for Java
Re: vhostTest is not detected as a Test dir
I also don't use the plugin, but open the build.gradle file directly. I am on Intellij 2016.2.4 UE On Wed, Dec 7, 2016 at 7:20 PM, Paul Merlinwrote: > To get the project into IDEA, I just import it directly from IDEA and I > don't get any dependency trouble. > > I'm not using ./gradlew idea anymore. > > > Niclas Hedhman a écrit : > > The same problem exists for src/perf/java in tests/performance. > > > > Could we name this back to src/test? > > > > And if so, should we move the vhostTest stuff to a tests/vhost as well? > > > > > > The above assumes that Paul doesn't have a "Oh, just do..." answer to > this > > issue. > > > > > > Cheers > > Niclas > > > > On Wed, Dec 7, 2016 at 5:22 PM, Niclas Hedhman > wrote: > > > >> Paul, > >> isn't it cool that we have a Gradle expert in the team :-) > >> > >> Your very elaborate handling of JDK 9 in libraries/http creates a > problem > >> in the IDEA-Gradle integration. > >> > >> The vhostTest sourceSet is recognized as a "main/java" and not > "test/java" > >> in IntelliJ. I have no idea where to start looking, in our build > script, in > >> gradle or IntelliJ. Did some naive searches on Google, but could only > find > >> something somewhat related, but not, https://discuss.gradle.org/t/ > >> intellij-dependencies-not-appearing-with-custom-configuration/5757 > >> > >> And it is quite bad, because it will not bring in the dnsjava > dependency, > >> so even if I change it manualy to a "test/java" it is not resolved, and > as > >> soon as the dependencies are recomputed, we are back to "src/java". > >> > >> Any ideas? > >> > >> Cheers > >> -- > >> Niclas Hedhman, Software Developer > >> http://zest.apache.org - New Energy for Java > >> > > > > > > > -- Niclas Hedhman, Software Developer http://zest.apache.org - New Energy for Java
Re: vhostTest is not detected as a Test dir
To get the project into IDEA, I just import it directly from IDEA and I don't get any dependency trouble. I'm not using ./gradlew idea anymore. Niclas Hedhman a écrit : > The same problem exists for src/perf/java in tests/performance. > > Could we name this back to src/test? > > And if so, should we move the vhostTest stuff to a tests/vhost as well? > > > The above assumes that Paul doesn't have a "Oh, just do..." answer to this > issue. > > > Cheers > Niclas > > On Wed, Dec 7, 2016 at 5:22 PM, Niclas Hedhmanwrote: > >> Paul, >> isn't it cool that we have a Gradle expert in the team :-) >> >> Your very elaborate handling of JDK 9 in libraries/http creates a problem >> in the IDEA-Gradle integration. >> >> The vhostTest sourceSet is recognized as a "main/java" and not "test/java" >> in IntelliJ. I have no idea where to start looking, in our build script, in >> gradle or IntelliJ. Did some naive searches on Google, but could only find >> something somewhat related, but not, https://discuss.gradle.org/t/ >> intellij-dependencies-not-appearing-with-custom-configuration/5757 >> >> And it is quite bad, because it will not bring in the dnsjava dependency, >> so even if I change it manualy to a "test/java" it is not resolved, and as >> soon as the dependencies are recomputed, we are back to "src/java". >> >> Any ideas? >> >> Cheers >> -- >> Niclas Hedhman, Software Developer >> http://zest.apache.org - New Energy for Java >> > > >
Re: vhostTest is not detected as a Test dir
The same problem exists for src/perf/java in tests/performance. Could we name this back to src/test? And if so, should we move the vhostTest stuff to a tests/vhost as well? The above assumes that Paul doesn't have a "Oh, just do..." answer to this issue. Cheers Niclas On Wed, Dec 7, 2016 at 5:22 PM, Niclas Hedhmanwrote: > Paul, > isn't it cool that we have a Gradle expert in the team :-) > > Your very elaborate handling of JDK 9 in libraries/http creates a problem > in the IDEA-Gradle integration. > > The vhostTest sourceSet is recognized as a "main/java" and not "test/java" > in IntelliJ. I have no idea where to start looking, in our build script, in > gradle or IntelliJ. Did some naive searches on Google, but could only find > something somewhat related, but not, https://discuss.gradle.org/t/ > intellij-dependencies-not-appearing-with-custom-configuration/5757 > > And it is quite bad, because it will not bring in the dnsjava dependency, > so even if I change it manualy to a "test/java" it is not resolved, and as > soon as the dependencies are recomputed, we are back to "src/java". > > Any ideas? > > Cheers > -- > Niclas Hedhman, Software Developer > http://zest.apache.org - New Energy for Java > -- Niclas Hedhman, Software Developer http://zest.apache.org - New Energy for Java