Re: DependencyManager and car-maven-plugin problem
The answer to this post is:
For a lot of standard components, this type of error message is not fatal. Geronimo or the car-maven-plugin can load the basics.
For your target project (e.g. custom plugin) it's a different story.
For Geronimo 3.0.1, to generate CAR packaging, the maven project that compiles your program must generate a bundle with the dependencies embedded. During packaging, when the car-maven-plugin boots the geronimo kernel, the dependency manager will have all the info to resolve the dependencies. It is no longer sufficient to generate a simple jar artifact. For a basic Geronimo bean, the plugin to generate the bundle looks like this.
The packaging for the target project must be "bundle" instead of "jar"
The geronimo kernel has no access to maven repository when it processes a bundle, so the bundle has to contain everything that geronimo is not providing in its processing container (or already loaded in a previously processed bundle?). This example is for a project that does compilation and packaging only (no test).
I was reluctant to spend much time with books on Geronimo 2.
I verified this solution on a simplified example, but it gets more interesting. The build for this project is still throwing the same error even though I corrected my plan. That means there is another issue in my build or my plan causing a problem. But at least I know now how it's suppose to work.
I might publish a tutorial when I get done with this.