Project jar package management, using. userlibraries files to increase the portability of jar packages, clear jar dependencies, multi-project common jar packages

When an ordinary project is not applicable to the jar package management tools such as MAVEN, usually I copy the jar package directly under the LIB, and add the additional jar package directly in the build path, or use the jar package of the User_libraries package

In a folder, and then make the project dependent on the User_libraries package. If I create a new project, but only some of the jar packages are different or the versions are different, I usually create a new folder again to put these jars in,

If there is a problem with the jar package I would like to look at the files under the Lib, looking very inconvenient, also inconvenient management.

Is there an XML file like maven that lists all the jar packages, at a glance of the native way?

View Eclipse's management of User_libraries

Exports one of the user_libraries files using export, with the suffix name. userlibraries

<?XML version= "1.0" encoding= "UTF-8" standalone= "no"?><eclipse-userlibrariesversion= "2">    <Libraryname= "Jbpm-lib"systemlibrary= "false">        <ArchivePath= "E:/ruanjian/jbpm-jar/activation.jar"/>        <ArchivePath= "E:/ruanjian/jbpm-jar/antlr.jar"/>        <ArchivePath= "E:/ruanjian/jbpm-jar/antlr-runtime.jar"/>        <ArchivePath= "E:/ruanjian/jbpm-jar/avalon-framework.jar"/>        <ArchivePath= "E:/ruanjian/jbpm-jar/bsh.jar"/>        <ArchivePath= "E:/ruanjian/jbpm-jar/cglib.jar"/>        <ArchivePath= "E:/ruanjian/jbpm-jar/commons-collections.jar"/>        <ArchivePath= "E:/ruanjian/jbpm-jar/commons-logging.jar"/>        <ArchivePath= "E:/ruanjian/jbpm-jar/core.jar"/>        <ArchivePath= "E:/ruanjian/jbpm-jar/dom4j.jar"/>        <ArchivePath= "E:/ruanjian/jbpm-jar/drools-api.jar"/>        <ArchivePath= "E:/ruanjian/jbpm-jar/drools-compiler.jar"/>        <ArchivePath= "E:/ruanjian/jbpm-jar/drools-core.jar"/>        <ArchivePath= "E:/ruanjian/jbpm-jar/errai-bus.jar"/>        <ArchivePath= "E:/ruanjian/jbpm-jar/errai-common.jar"/>        <ArchivePath= "E:/ruanjian/jbpm-jar/freemarker.jar"/>        <ArchivePath= "E:/ruanjian/jbpm-jar/gson.jar"/>        <ArchivePath= "E:/ruanjian/jbpm-jar/guice.jar"/>        <ArchivePath= "E:/ruanjian/jbpm-jar/guice-aopalliance.jar"/>        <ArchivePath= "E:/ruanjian/jbpm-jar/guice-servlet.jar"/>        <ArchivePath= "E:/ruanjian/jbpm-jar/gwt-console-rpc.jar"/>        <ArchivePath= "E:/ruanjian/jbpm-jar/gwt-console-server-integration.jar"/>        <ArchivePath= "E:/ruanjian/jbpm-jar/hibernate-core.jar"/>        <ArchivePath= "E:/ruanjian/jbpm-jar/hsqldb.jar"/>    </Library></eclipse-userlibraries>

The observation is that the Archive node path property specifies the jar path

So can we put some common jars in a folder (not every time the project goes to the jar, the jar is downloaded, such as the JAR rollup required by strtus, the jar rollup required by SSH), and then write a file like the one above

After we create a new project directly import this file can complete a project all the jar package import ...

The answer is yes: we just used the export, and there is an import on him that imports the. userlibraries file that we have written. The introduction of the jar package can then be completed by adding user_libraries to the project.

Project jar package management, using. userlibraries files to increase the portability of jar packages, clear jar dependencies, multi-project common jar packages