I have a java project with related jars associated. This project is pushed to GIT. Now when I checkout code in a new machine and import project. I see Jar files in the workspace but it won't be associated by default. I need to manually go to the build path--> configure the build path and browse the jars and add to the library. This is blocking me to work with Jenkins as it's not identifying jars on every new workspace. How to avoid manually setting classpath on new workspace checkout.
Instructor
Ashish Thakur Replied on 23/02/2021
You have to use maven for that
It can avoid manual addition of the jars
The problem is the framework is already developed using Java Project and it's difficult to migrate to maven as some of the jars are build by developers within the project. There won't be any dependency on these jars. So could you please let me know is there any workaround for the java project itself?
Instructor
Ashish Thakur Replied on 25/02/2021
There is no work around. You have to use maven
May be you can submit those jars on maven repository online