On 18/12/2007, Steinar Bang <[EMAIL PROTECTED]> wrote: > > >>>>> "Wayne Fay" <[EMAIL PROTECTED]>: > > > That's just not the way Maven works. What libraries in particular do > > you need -- many should be available in the Maven repo already, so its > > simply a matter of writing the proper pom.xml <dependency> entries. > > That's not always sufficient.
well, there are system scope dependencies that let you refer to library artifacts in a fixed location like "/usr/share/lib/..." but their use is discouraged, because it makes things less portable: http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html Eg. if you want to start an OSGi application based on equinox, then you > have to use a jar for the OSGi runtime, that resides in a directory that > have a ./configuration/config.ini file, and in the same directory as the > OSGi bundles the config.ini tells the OSGi runtime to load and start. > > (...says the experience of someone who tried using the version of the > very same file in the maven repo, and didn't understand why the app > didn't start, last Friday...) FYI, you might be interested in: http://wiki.ops4j.org/confluence/x/A4A6 Pax-Runner http://wiki.ops4j.org/confluence/x/8Q Pax-Construct which aim to make OSGi development and deployment a breeze with Maven --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Cheers, Stuart
