havardh / javaflow-maven-plugin Goto Github PK

When using the wrong package name, the error produced looked like this:

[ERROR] Failed to execute goal com.github.havardh:javaflow-maven-plugin:1.0.0:build (default-cli) on project cap: Could not generate types: Parameter 'directory' is not a directory -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

This turned out to be because the package defined in packageName was incorrect, thus generating an invalid baseSourceDirectory in

Contents of the paramter 'directory' could be useful information

Let's say we have the following (Maven) project structure:

common
  src/main/java/com/example/common/Address.java
domain
  src/main/java/com/example/domain/User.java
ui
  src/some-page.js

and we want to generate types for the ui module.

Currently, there is no way to specify the two input directories common and domain (along with packages com.example.common and com.example.domain) as input directories.

It's possible to give multiple <api> sections in the config of this plugin, but then the generation of domain will fail because type User has an unknown type Address

Add a simple sample project to verify that the plugin is working on circleci.

1. Create a subfolder called sample
2. Implement a small project with a model and pom.xml depending on the latest snapshot of the maven plugin
3. Build and install javaflow and javaflow-maven-pluginfrom source on the circleci env
4. Run mvn javaflow:build and verify successful exit code.

Hello,

While using the plugin, we ran into an issue where the target directory (custom one, not the default /target) was not existing so we got an NoSuchFileException. Creating the folder manually fixed this and we do not have this issue anymore.

However, I was thinking, what if there is an option which will tell the plugin to create the target folder (if missing)? Something like createIfMissing, or feel free to propose a better name.
What do you think about it?

I could submit a PR for that if that's fine with you.

Regards,
Goce