The test project POM file adds the Maven assembly to the build cycle. The assembly plugin uses the src/main/assembly/create-lib.xml file as a descriptor.
When you build the project, in the package phase, the assembly plugin copies all the dependencies that are not part of JSystem to the project lib folder.
This is done because JSystem is not using the Maven dependency mechanism, so copying the jars to the lib folder allows JSystem to add them to the class path.
If something turned sour in the process, first make sure that you have executed Maven install on the infra project and that the build was completed successfully. Then make sure that you included the infra project as a dependency in the test project and that you have successfully built the test project with no error messages in the console.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have two projects , test and infra project .
in Runner lib there is the infra jar .
Runner JSystem.proporites points for classes in Test Project .
JSystem could not recognize dependencies added to test project .
anybody know how to solve it ?
Thanks,
khilo
Hi Khilo.
The test project POM file adds the Maven assembly to the build cycle. The assembly plugin uses the src/main/assembly/create-lib.xml file as a descriptor.
When you build the project, in the package phase, the assembly plugin copies all the dependencies that are not part of JSystem to the project lib folder.
This is done because JSystem is not using the Maven dependency mechanism, so copying the jars to the lib folder allows JSystem to add them to the class path.
If something turned sour in the process, first make sure that you have executed Maven install on the infra project and that the build was completed successfully. Then make sure that you included the infra project as a dependency in the test project and that you have successfully built the test project with no error messages in the console.
Thanks