nebula-plugins / nebula-hollow-plugin

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

hard coded relativeJavaSourcesPath

eNkru opened this issue · comments

The project I am currently working is a mix of Java and Groovy. The source path is actually named as "src/main/groovy" instead of "src/main/java".

Is that a way to configure the source path in the gradle/maven configuration?

@eNkru Currently, there is no way to configure it. Speaking about maven plugin, for now it can build api classes for sources outside src/main/java only in multi-module configuration (I haven't checked it yet, but it uses classpath scanner which is not about parsing files recursively, so it should be fine). I'm going to implement this logic for single-module configuration in a few days and provide some examples, I can give you more information on that when it ready.

Great work. Actually I am using Gradle for now. I am back to the manual triggering the APIGenerator at the moment. Once the Gradle plugin support the customise the source path. I can include this plugin into the project 👍

Just to clarify things up - your datamodel is groovy files and are placed under src/main/groovy right? There will be support for finding them, but the result files is still Java classes, so they will be placed under src/main/java/your/package/name anyway.

@eNkru 3 years late 😅 but I am trying to address this in #21. I have tested with Kotlin but should work with Groovy too

always be good to see more feature supported 👍