> It appears that your ProjectA depends on ProjectB. > If you have the projectB listed as a dependency of project A and you do a > build of projectA, you will get a jar file that contains all of the classes > of projectA and ProjectB.
Ron's advice is sound and useful. I just wanted to clarify this comment. You won't get a "jar file that contains all the classes of A and B" by default if B is a dep of A and you simply build A. You would need to use the assembly plugin (or dependency plugin, unpack mojo) or something along those lines to produce such a "fat" jar. The default would simply produce a jar with A's classes in it, and you'd need to include B.jar on the classpath to run A successfully. Wayne --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
