Hi Vio, > On 22. Apr 2020, at 19:25, Viorel Morari <viorel.mor...@averbis.com> wrote: > > .) Is see Spring Framework in use both in source- and bin-release. While the > LICENSE file of the bin-realease mentions it, in the LICENSE of the > source-release it is missing. No sure if that's intentional.
The binary release ZIP file includes the Spring JARs - that is why their license text is included. The source release only compiles against Spring, but does not ship it. So the license text is not included. > 2.) Building uimafit with Java 8 in Eclipse 2020-03 fails. The build fails in > the maven-plugin module: > [INFO] Building: default\pom.xml > [INFO] run post-build script verify.bsh > [INFO] default\pom.xml .................................. FAILED > (0.1 s) > [INFO] The post-build script returned false. > [INFO] Building: with-typesystem-in-descriptors\pom.xml > [INFO] run post-build script verify.bsh > [INFO] with-typesystem-in-descriptors\pom.xml ........... FAILED > (0.0 s) > [INFO] The post-build script returned false. > The build is successful in the console though. Don't know if that's an > Eclipse related problem or if I'm missing something. Right, it fails in Eclipse. However, I don't see it as a priority that the build works in Eclipse as long as the CLI build works. We can open an issue if you like and maybe track it down at some point, but for the time being, I personally consider it as a "nice to have" thing that the Maven build also works in Eclipse (note: the unit tests work in Eclipse and it also compiles without errors in Eclipse - just the integration tests from a Maven build triggered within Eclipse fail). -- Richard
