Ah, good ol' Documentum. I haven't worked with those jars in a while.
Vinnie, each jar is a separate artifact, so each jar must be installed separately. You'll want to add -DgeneratePom=true to the mvn command to generate a minimal POM and prevent maven from looking for that POM in remote repositories. Use a groupId like "com.documentum", or have they changed there packaging now to com.emc.document!?!??! FYI, if you're not the only developer in your organization, you'll be well served to create an intranet repository and place the Documentum (and other) jars there so everyone benefits from your work. In addition, you could create a POM-only project to bundle the various Documentum jars so they can be added to your projects transitively via a single dependency. -Doug On 5/25/06, vdiprenda - optonline <[EMAIL PROTECTED]> wrote:
I understand the mvn install:install-file should be used for third party jar files. I'm assuming that things like classes12.jar from oracle would be something I would have to install to use hibernate if I was in fact, looking to talk to Oracle. I'm assuming that's the intention for the command. What about a third party product that consists of multiple jar files. For instance, if I want to use a product like Documentum that has several jar files, would this be the way of loading the jars into the repository? I'm assuming that the way to look at the dependency is by the GroupId, ArtifactId and the versionId. Should/could the mvn install:install-file command be used to load several jars into one dependency? Thanks Vinnie --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
