Gang,
JetBrains used to, and probably still do, provide Ultimate Edition to
Apache committers. I personally don't use that anymore, as the "full suite
of apps" are now (to me) reasonably priced compared to a few years ago.
I think opensou...@jetbrains.com should be used to request. State that it
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 navig
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 Merlin wrote:
> Niclas Hedhman a écrit :
> > I also don't use the plugin, but
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 c
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 Hedhman wrote:
> 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
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 an
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, shoul
Niclas Hedhman a écrit :
> I didn't really notice all the nice things that Paul has done in the build
> system.
:)
> I particularly like the
>
> compile zest.extension( 'entitystore-jdbm' )
>
> Would it be possible to create and distribute a "Polygene plugin", which
> does this for downstream
Actually, more like;
apply plugin: 'polygene' // also sets the repositories needed.
> dependencies {
> polygene.core() // sets up compile, runtime, testCompile
>
> if possible...
On Wed, Dec 7, 2016 at 6:58 PM, Niclas Hedhman wrote:
> I didn't really notice all the nice things that Paul h
I didn't really notice all the nice things that Paul has done in the build
system.
I particularly like the
compile zest.extension( 'entitystore-jdbm' )
Would it be possible to create and distribute a "Polygene plugin", which
does this for downstream users?
apply plugin: 'polygene' // also
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
The org.apache.zest.spi.module.ModuleSpi contains access methods to a bunch
of useful SPI internals, such as EntityStore, TypeLookup and more.
Should we not just kill this class and provide that via @Structure
injection, since that is what we do with factories (and ServiceFinder?)
If not, shouldn
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,
13 matches
Mail list logo
