OK, i'll try that thanks! but what is the alternative?
can i "mvn install" (like yum install) a maven project (let's say sql utils) to the file system, and a new project that depends on that project will be able to use it (by looking in CLASSPATH?) i mean, i assume that if i have some infrastucture JARs (for e.g. log4j or fileUtils) i won't want them packed with every new project, the new project will need them to operate and install them if they are missing (just like yum install does with dependencies..) perhaps this is more of a JAVA question than MAVEN, but unfourtunatly i'm new to both :( been programming in Perl for the last few years.. so i'm dusting off the rust of my java knowladge ;) On Mon, Nov 16, 2009 at 5:55 PM, Wayne Fay <[email protected]> wrote: > > I noticed I'm having this in other projects as well (my own projects). > > > > what am i missing? > > Maven does not, by default, build a jar package which you can simply > run with "java -jar" from the command line. You have to include all of > your dependencies (including transitive deps) with the -cp parameter. > > If you want to build "fat" jars, google "maven jar with dependencies". > > Wayne > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Eyal Edri
