Java Dependencies during Development and Deployment

Question

I have a general question on how to properly manage your jQuery compilation and deployment dependencies. I usually install dev directories as shown below for a simple library / application.

Calculator
   src
   test
   build
   lib
   …

There are many ways to do this, but this is my typical layout for general projects. My question revolves around the lib directory. I usually install jars that my project depends on the lib directory (log4j, etc.). So during compilation, I can set various paths like lib \ log4j.jar or something like that. Now that we are creating a distribution package, I have tended to reflect this layout.

dist
   Calculator.jar
   lib
      log4j.jar
      addition.jar
      subtraction.jar

script, , (Calculator.jar ). , , , , .

, , - , .

, , , Calculator . , :

dist
   ScentificCalculator.jar
   lib
      Calculator.jar
      lib 
         Log4j.jar
         addition.jar
         subtraction.jar

, - :

SuperWhizBangCalculator.jar
lib
   ScientificCalculator.jar
   lib 
      Calculator.jar
      lib
         log4j.jar
         addition.jar
         subtraction.jar

- :

SuperWhizBangCalculator
   lib
      ScientificCalculator.jar
      Calculator.jar
      log4J.jar
      addition.jar
      subtraction.jar

- . , , , . , , , .

...

Answer 1

. Apache Maven 2, " " .

, - Maven 2:)

, .

Answer 2

, , , , lib-in-a-lib . jar, . , ...

, - .

, , Eclipse ... ...

Answer 3

• , log4j

lib . .

Answer 4

: " Maven?"

Maven , , . Java , , Maven.

Answer 5

- lib. , , , ( , JAR).

- . , - Maven, ANT Ivy , , - (OSGi).

Answer 6

. A, B C, D. D , .

Answer 7

. "java -jar SuperWhizBang.jar" , . .

If you decide to have separate class loaders, then a hierarchy would be a good idea. This usually happens in OSGi setup, but it is probably too large for your solution.