module-core | Core components and connectors for Reedelk Integration

The build script loads everything correctly. The module that you're trying to load no longer exists. You're trying to use an old version of the Real World OCaml book together with a very new version of OCaml and Core. The Janestreet Core library has changed a lot since those times. You should either switch to a newer book or downgrade to an older version of OCaml and Core library.

Since the admission of Dune and module aliases, it is no longer needed to have an extra Std submodule, therefore Janestreet removed it (after a two-year-long deprecation). Therefore, now we're writing

After a few hours of research, I finally solved my problem from below steps:

From Xcode, File -> Workspace Settings... -> Advanced... -> Build Location (Select "Unique" option)

The reason is because that the Xcode build intermediate files are not in the correct paths. By selecting above option, all those files went into the correct directories and my problems got solved.

I think you have run into Groovy-Eclipse issue #370 (https://github.com/groovy/groovy-eclipse/issues/370). If you switch Groovy compiler level to 2.4 or below, this should not occur.

Window > Preferences > Groovy > Compiler > Groovy Compiler settings section

Maven is a build tool and Log4j is a library that comes into play in runtime.

Hence it's not clear what exactly you're trying to achieve.

In order to get correct definitions of log4j its definitions (configurations) have to appear in the artifact, and maven "ends" when the artifact is prepared (ok, there are install and deploy but they do just "mechanical" actions on an already-prepared artifact and do not change it).

Now artifacts can be roughly divided into 2 types:

• Application intended to be deployed on server (usually these are WARs, EARs, spring-boot-applications, etc)
• Libraries intended for internal usage by the applications of your project or libraries that are supposed to be publicly accessible (like log4j itself, hibernate, spring, etc.)

Usually, only the first type of artifacts has logging definitions (log4j2.xml, whatever). Libraries while being able to use the logging framework, do not have their own definitions, because only the application that uses the library "knows" how to "serve" the logs (appenders, patterns to be applied and so forth)

Now, applying this knowledge to your question: I assume that module-core is a library, but module-a & module-b are applications.

If so, they should have their own log4j2.xml in the classpath in runtime. Usually, people place the configuration file into src/main/resources of these modules and they're done - each log4j2.xml can be different. Alternatively, they import the file from some "shared" location, if the goal is to preserve the same log4j behavior (again, in runtime) between the applications.

Now Having said all that, maven run tests during the build and this is actually the only place where you see maven running your code actually during the build.

Tests in maven have a different classpath, so if the goal is to establish the different behavior of log4j in tests you should place the logging configurations into src/test/resources. Neither this file nor tests themselves won't be packaged into the production artifact.

This practice is applicable to both "libraries" and "applications"

I'm able to build the workspace just enabling the property "private":true

file: demo-app/package.json

I finally found the answer. Npm Version 5 indeed changed the way the local dependencies are handled and it just makes npm link, which creates symbolic links or shortcuts in windows.

You can accomplish the same behavior as before with this:

you need to add maven-compiler-plugin into pom.xml. you can find the plugin code below and replace the source version by your jdk version:

I assumed Failsafe not showing up in ..help:describe.. next to respective phases was root of my issue, but it turns out it was not (see answer for failsafe not binding to X or Y ). The setup of two test types (int/unit) between two different source locations (src/it and src/test) was the problem, and it appears to be a common configuration pain when using Maven. This is because it goes against the convention for how Maven assumes a project will be setup.

In order to achieve the use of two different source folders for tests, I found [Kainulainen-2012] who demonstrates the use of [(org.codehaus.mojo:build-helper-maven-plugin)] which configures executions with additional sources for use during compilation. This solves the primary goal as defined above albeit in a non-conventional way while also introducing other problems. Alternatively, using Maven's convention would only require moving Integration tests into the "src/test" location of each module and possibly updating test names. I did not experience additional problems this way, and I found it to be the simpler solution.

1. Move Integration test to "src/test" classPath for each module.
2. Give names to integration test which include "IT" [Failsafe default name convention]
3. mvn install parent -> core -> backend modules

1. Add build-helper-maven-plugin to parent pom.xml under module-parent.
2. mvn install parent -> core -> backend modules