Hi Igor -
Attached is a small zip file will all the parts. There is a bundle-parent project that provides several Maven definitions, a BundleGuava project that should be the simple "wrapper" project, and a BundleUser project that should be launchable as an Eclipse application. Maven build all three (in order above), import the projects into Eclipse, and try to launch the BundleUser project (from an Eclipse sample).
When I click on the provided action (the Eclipse icon), I get the "java.lang.ClassNotFoundException: com.google.common.base.Joiner cannot be found by BundleUser_1.0.0.qualifier".
This should be nearly identical to the zip file attached in the original email. Some small tweaks to BundleGuava project. This was created by cp -r of my sample projects, deleting the .git and */target directories, and zip -r over the remaining tree.
I'm actually working on a much larger project (DepAn), with 8+ third-party libraries (asm, guava, jogl, joda, jung, xstream, etc.). Having a systematic scheme for creating third party libraries in Maven versus using hacked-up custom Eclipse builds will be a boon for generating releases.
Thanks for taking the time to look into the details.
Lee