Merge with JGAAP Repo
Here is the request to merge the new JGAAP into the main repository,
Alright those changes should of been made.
Alright those changes should of been made.
Thank you!
Trying to use Gradle to build using the command line, I get the following error when building on Windows:
C:\Users\berdikd\Documents\JGAAP>gradlew.bat build
Downloading https://services.gradle.org/distributions/gradle-8.8-bin.zip
.............10%.............20%.............30%.............40%.............50%.............60%..............70%.............80%.............90%.............100%
Welcome to Gradle 8.8!
Here are the highlights of this release:
- Running Gradle on Java 22
- Configurable Gradle daemon JVM
- Improved IDE performance for large projects
For more details see https://docs.gradle.org/8.8/release-notes.html
Starting a Gradle Daemon (subsequent builds will be faster)
> Task :jgaap:processTestResources FAILED
FAILURE: Build failed with an exception.
* What went wrong:
Some problems were found with the configuration of task ':jgaap:processTestResources' (type 'ProcessResources').
- Gradle detected a problem with the following location: 'C:\Users\berdikd\Documents\JGAAP\jgaap\build\classes\java\main\com\jgaap\resources'.
Reason: Task ':jgaap:compileTestJava' uses this output of task ':jgaap:processTestResources' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed.
Possible solutions:
1. Declare task ':jgaap:processTestResources' as an input of ':jgaap:compileTestJava'.
2. Declare an explicit dependency on ':jgaap:processTestResources' from ':jgaap:compileTestJava' using Task#dependsOn.
3. Declare an explicit dependency on ':jgaap:processTestResources' from ':jgaap:compileTestJava' using Task#mustRunAfter.
For more information, please refer to https://docs.gradle.org/8.8/userguide/validation_problems.html#implicit_dependency in the Gradle documentation.
- Gradle detected a problem with the following location: 'C:\Users\berdikd\Documents\JGAAP\jgaap\build\classes\java\main\com\jgaap\resources'.
Reason: Task ':jgaap:jar' uses this output of task ':jgaap:processTestResources' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed.
Possible solutions:
1. Declare task ':jgaap:processTestResources' as an input of ':jgaap:jar'.
2. Declare an explicit dependency on ':jgaap:processTestResources' from ':jgaap:jar' using Task#dependsOn.
3. Declare an explicit dependency on ':jgaap:processTestResources' from ':jgaap:jar' using Task#mustRunAfter.
For more information, please refer to https://docs.gradle.org/8.8/userguide/validation_problems.html#implicit_dependency in the Gradle documentation.
* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
> Get more help at https://help.gradle.org.
BUILD FAILED in 1m 32s
8 actionable tasks: 8 executed
Trying to use Gradle to build using the command line, I get the following error when building on Windows:
C:\Users\berdikd\Documents\JGAAP>gradlew.bat build Downloading https://services.gradle.org/distributions/gradle-8.8-bin.zip .............10%.............20%.............30%.............40%.............50%.............60%..............70%.............80%.............90%.............100% Welcome to Gradle 8.8! Here are the highlights of this release: - Running Gradle on Java 22 - Configurable Gradle daemon JVM - Improved IDE performance for large projects For more details see https://docs.gradle.org/8.8/release-notes.html Starting a Gradle Daemon (subsequent builds will be faster) > Task :jgaap:processTestResources FAILED FAILURE: Build failed with an exception. * What went wrong: Some problems were found with the configuration of task ':jgaap:processTestResources' (type 'ProcessResources'). - Gradle detected a problem with the following location: 'C:\Users\berdikd\Documents\JGAAP\jgaap\build\classes\java\main\com\jgaap\resources'. Reason: Task ':jgaap:compileTestJava' uses this output of task ':jgaap:processTestResources' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed. Possible solutions: 1. Declare task ':jgaap:processTestResources' as an input of ':jgaap:compileTestJava'. 2. Declare an explicit dependency on ':jgaap:processTestResources' from ':jgaap:compileTestJava' using Task#dependsOn. 3. Declare an explicit dependency on ':jgaap:processTestResources' from ':jgaap:compileTestJava' using Task#mustRunAfter. For more information, please refer to https://docs.gradle.org/8.8/userguide/validation_problems.html#implicit_dependency in the Gradle documentation. - Gradle detected a problem with the following location: 'C:\Users\berdikd\Documents\JGAAP\jgaap\build\classes\java\main\com\jgaap\resources'. Reason: Task ':jgaap:jar' uses this output of task ':jgaap:processTestResources' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed. Possible solutions: 1. Declare task ':jgaap:processTestResources' as an input of ':jgaap:jar'. 2. Declare an explicit dependency on ':jgaap:processTestResources' from ':jgaap:jar' using Task#dependsOn. 3. Declare an explicit dependency on ':jgaap:processTestResources' from ':jgaap:jar' using Task#mustRunAfter. For more information, please refer to https://docs.gradle.org/8.8/userguide/validation_problems.html#implicit_dependency in the Gradle documentation. * Try: > Run with --stacktrace option to get the stack trace. > Run with --info or --debug option to get more log output. > Run with --scan to get full insights. > Get more help at https://help.gradle.org. BUILD FAILED in 1m 32s 8 actionable tasks: 8 executed
UUUGGGHHH This is because I put int he test code from the old JGAAP test base into my base, and I guess Gradle is adding Test proceedures. Ill look into disabling or porting the tests over.
UUUGGGHHH This is because I put int he test code from the old JGAAP test base into my base, and I guess Gradle is adding Test proceedures. Ill look into disabling or porting the tests over.
Thanks! Good luck!