On Wed, 2002-08-21 at 16:02, Leif Nelson wrote: > I'm currently setting up a project to use Maven B6, and was wondering if > what I'm doing is correct. It doesn't seem right for this situation... > > My application requires the Oracle BC4J .jar files in it's dependencies > list. BC4J consists of approximately 10 jar files named like this: > bc4jmt.jar > bc4jctejb.jar > bc4jdomorcl.jar > bc4jhtml.jar > bc4jimdomains.jar > bc4jct.jar > ( there are more variations...) > > In B4, I renamed all the bc4jxx.jar files to bc4jxx-9.0.2.7.94.jar (to > match the version of BC4J that I obtained the jars from) and placed them > all in repository root directory. > > In B6, now that the repository layout has changed, is it true that the ONLY > way to organize this stuff is to create a separate directory for EACH jar > file (as far as I can tell...): > bc4jmt/jars/bc4jmt-9.0.2.7.94.jar > bc4jctejb/jars/bc4jctejb-9.0.2.7.94.jar > etc...
You can put them all in the same directory if you wish. > Or, is it possible to include all of these jars in a single directory like: > bc4j/jars/bc4jmt-9.0.2.7.94.jar > bc4j/jars/bc4jctejb-9.0.2.7.94.jar > etc.. Yes you can put them in the same directory. The dependency notation is just a little different. http://jakarta.apache.org/turbine/maven/reference/naming-conventions.html You can a peek at that, though the notation will probably be changed to make it more readable. > It would sure be nice if the dependency tag allowed for this somehow to > "package up" jars that are really required to be used together.. The > reason they're split up into separate jar files, is so that you can use > separate pieces of functionality in different deployments, depending on the > use cases. > > Something like this, possibly... > > <dependency> > <id>bc4jct</id> > <version>9.0.2.7.94</version> > <url>http://www.oracle.com</url> > <group>bc4j</group> > </dependency> To get this to work you would use something like this: <dependency> <id>bc4j+mt</id> <version>9.0.2.7.94</version> </dependency> Maven will expect this jar to be here: ${maven.repo.local}/bc4j/jars/bc4j-mt-9.0.2.7.94 So there is a vague notion of a 'parent' project and this will be claried because we have many cases where there is a parent project. Like the commons, or avalon or any type of application that consists of several components. I know the notation is ugly but it will work to group the JARs in a single directory and we're going to make the dependency descriptors more friendly before the 1.0 release. > Thanks for any info on the subject, > > Leif Nelson > -- jvz. Jason van Zyl [EMAIL PROTECTED] http://tambora.zenplex.org In short, man creates for himself a new religion of a rational and technical order to justify his work and to be justified in it. -- Jacques Ellul, The Technological Society -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
