We hit exactly the same problem yesterday. The only ideas I had were to copy the dependency information somehow into a repository [is that what the pom/ directory is for in repostiory/?] or to embed the information in the jar [according to sun spec whatever].
A worse way would be to pull the information, but that only works for projects you own, so is weaker. I'm guessing the Mavenites are planning something to use http://www.ibiblio.org/maven/anttex/poms/ etc? I'm still on b0.7 btw. Hen On Wed, 19 Mar 2003, James CE Johnson wrote: > Hey All, > > [If you get something like six copies of this pleas forgive me. I'm having > a heck of a time posting today.] > > This one is whacky... > > I've got a project that has three sub-projects. We'll call them A, B and C > just for grins. > > Now... > Project A creates a jarfile (cleverly named A.jar) > To create that jar, A/project.xml lists a bunch of dependencies. > Anyone using that jar needs *some* of those dependencies at runtime. > > Which brings us to... > Project B creates an earfile (uncreatively named B.ear) of EJBs > B depends on A.jar at compiletime, so A.jar is in project.xml and is > marked with ear.bundle.jar == true. > At runtime, the earfile also needs to have the runtime-required files on > which A.jar depends. > > Finally... > Project C is a simple webapp that doesn't know diddly about A and only > uses the client-side jarfile from B. > > Where I'm going with this is that in B/project.xml I've had to copy/paste > a bunch of the dependencies in A/project.xml and add ear.bundle.jar == > true. I've heard something about project.xml actually being a jelly script > and, thus, executable. Can someone suggest a clever way for B/project.xml > to magically "import" the proper dependencies from A/project.xml? (I don't > mind adding ear.bundle.jar or some other property to the appropriate > dependencies of B/project.xml if necessary.) > > Thanks, > J > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
