|Re: Jar Files In Referenced Libraries Of A Project Across Computers [message #1793948 is a reply to message #1793158]
||Tue, 21 August 2018 02:27
| Ioannis Nearchou
Registered: February 2018
How are you? Thank you for the reply. I apologize for my own late reply. After your reply, I started looking into build systems and have started learning to use Gradle for dependency management. The focus of this question is distribution, because I want to make sure any dependencies required in my project are present in the hierarchy of the folder and are the most compatible versions relative to the platform someone is using, such as Mars vs. Photon.
As for a simple solution to save time, what is the upper bound on "few" for number of jars in a bundle? I counted nearly 40 jars required by my project. I also recall being able to use configure build path to create a Plug-in Dependencies folder in the build path. I suppose this would be a similar solution to the suggestion you gave about the jar bundling.
The particular problem I have is with a program that is used to load Ecore or UML files, created dynamic EMF models from them, and create OCL constraints that would be saved to instances of these models. To do this, I require jars such as org.eclipse.emf.mapping.ecore2xml_2.9.0.v20170609-0928.jar, but want to make sure they are portable as I zip and export the project from my computer and then unzip and import to another IDE on another computer. I was wondering what are the steps to add jars to a Plug-in Dependencies folder after it is created, instead of referencing local libraries from my file system? Is there also a similarly simple solution when considering dependency management?
Powered by FUDForum
. Page generated in 0.01878 seconds