The previous practice is:
Suppose JBUILDER's engineering path is:
E: /jb/myproject/myproject.jbx
So E: / JB / MyProject / Newly built a libjars directory,
Then copy all the LIBs to be used to this directory.
Next in Tool -> Configure -> Libraries -> New -> Folder Select Project (this is very important).
Then add all JAR all. References in the project.
This approach ensures that when a project is copied to another machine, you can use it directly to open the project.
But such an engineering will result in a lot of JAR file redundancy.
So finding a better approach should be considered.
Set up a file first, such as mine: E: / javalibs.
Then put the javalib I want to use below.
E.g
E: / javalibs directory
2004-11-29 11:47
2004-11-29 11:47
2004-11-29 11:49
2004-05-11 12:54
2004-11-29 11:56
2004-11-29 11:57
2004-11-29 11:57
2004-11-29 12:35
2004-11-29 12:37
2004-11-29 15:09
2004-11-29 15:19 443 javamail1.3.2.library
2004-11-29 15:25 396 JAF1.0.2.Library
2004-11-29 15:25 1,297 Sitemesh2.2.1.library
Then it is
Tool -> Configure -> Libraries -> Add Folder ->
E: / javalibs.
Next, add a new LIB.
NEW -> Folder Select E: / Javalibs (this is very important).
Because the path generated by such a Library generated is the relative path.
The time after copying works to other computers. Copy the E: / Javalibs directly, then
TOOL -> Configure -> Libraries -> Add Folder -> Select the directory you copy,
LIB in this directory is automatically configured and available.
An example of a library file:
E: /javalibs/javamail1.3.2.library
