The maven-car-plugin has been implemented using bits and pieces from the geronimo packaging plugin. Please keep in mind that my answer refer to the original version.
--- Prasad Kashyap <[EMAIL PROTECTED]> wrote: > I'd like Anita who implemented the plugin confirm my answers. Please > see inline - > > On 7/24/06, Aaron Mulder <[EMAIL PROTECTED]> wrote: > > I guess I have a few more questions, now that I think about it: > > > > * Must you put the plan at src/plan/plan.xml or is there some way > to > > point it to a different file or use an embedded plan? > > There is a planFile config option in the mojos. So I suspect you may > specify a different location for the plan file. By default, it > expects > the plan to be in target/plan/plan.xml. yes, it is possile to configure <planFile)>, never tested.. > > > > * Must you put the plugin descriptor at > src/conf/geronimo-plugin.xml > > if <geronimoPlugin> is set to true? Is there some way to point it > to > > a different file? yes, it should be possible to point it to a different file. Again never tested.. The current car-maven-plugin lacks the ability to package geronimo-plugin.xml file. > > I don't see this config option handled in any of the mojos. I suspect > that either it got lost or it never got in, in the first place. So > the option is ignored. I would recommend that the config format used in the original plugin be used in car-maven-plugin. For example to package an application user can just say ${j2eeJettyServer} or {j2eeTomcatServer} and not have to worry about the order of the deployers. The original plugin allowed this format: <deploymentConfig>${j2eeTomcatServer}</deploymentConfig> > > > > * What dependencies should be listed in the POM for a CAR? Let's > say > > you have one module to build a JAR and another module to make a CAR > > out of that JAR. Shouldn't the CAR POM be virtually empty except > for > > the parent module dependencies and some indication of which JAR > you're > > trying to make the CAR out of? I assume it could get the rest as > > transitive dependencies from the JAR POM. > > This is true simply as a matter of transitive deps from M2. > > > > > > * How does the car plugin know what module you're trying to make a > > CAR out of? I looked at the console-jetty POM, for example, and it > > had loads of dependencies, and there was nothing obvious about the > > geronimo console EAR dependency to indicate that's the one that > should > > be turned into a CAR by this particular build. Aaron, we need your help to remove the unneeded dependencies from the console-* configurations. All the other applications have the right dependencies. I have some issues with the current car-maven-plugin. IIUC, this plugin is used outside the context of the build. The new car-maven-plugin has a goal car:installconfig (or something similar) which has no meaning ouside the context of assembly. Do we want users to add things to the server using car:installConfig? If not this should be removed and be put in its own assembly plugin. Thanks Anita > > The console-jetty must have been a case of cut&paste error from it's > project.xml. I looked at the welcome-jetty pom.xml and that seems > correct. The welcome app lists all the deps and the welcome-jetty > config lists just the welcome app. > > > > > > Thanks, > > Aaron > > Cheers > Prasad > > > > > On 7/24/06, Aaron Mulder <[EMAIL PROTECTED]> wrote: > > > Great. Is it the case that the plugin would have to be installed > > > manually to work by default? Is there something I can put in the > POM > > > that will make it fetch that one plugin from the snapshot repo > you > > > listed so each developer doesn't need to download it by hand? > > > > > > Thanks, > > > Aaron > > > > > > On 7/24/06, Jason Dillon <[EMAIL PROTECTED]> wrote: > > > > Well, the packaging plugging has been merged with the assembly > > > > plugin, so now there is just one car plugin that handles all > car > > > > related fluff. > > > > > > > > You need to enable it as an exention, as in: > > > > > > > > http://svn.apache.org/repos/asf/geronimo/sandbox/svkmerge/ > > > > m2migration/configs/pom.xml > > > > > > > > The set the packaging type to car and will package the plan for > you. > > > > > > > > If you need to specify additional classpath or package > configuration > > > > you need to define something, as in: > > > > > > > > http://svn.apache.org/repos/asf/geronimo/sandbox/svkmerge/ > > > > m2migration/configs/j2ee-system/pom.xml > > > > > > > > There is a 1.2-SNAPSHOT of the car-maven-plugin up here: > > > > > > > > http://people.apache.org/repo/m2-snapshot-repository/ > > > > > > > > Its a week or so old, but should work. > > > > > > > > --jason > > > > > > > > > > > > On Jul 24, 2006, at 12:08 PM, Aaron Mulder wrote: > > > > > > > > > What do I need to put in a POM to use a working Geronimo > Packaging > > > > > Plugin for Maven 2? Is there such a thing available on the > Maven > > > > > repos? Do I need specific configuration directives in the > POM or in > > > > > my Maven config to pull it down? > > > > > > > > > > Thanks, > > > > > Aaron > > > > > > > > > > > > > > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com