We know a little more about this problem now. *If* the first thing that builds in the multi-project build is of the osgi-bundle *type*, then things seem to work OK. If instead, the first thing that is built from the top level is something else (say, a normal JAR file) then things do *not* work, and the mapping from osgi-bundle to jar are not getting properly registered.
Someone please help! John Wells (Aziz) [EMAIL PROTECTED] -----Original Message----- From: John Wells Sent: Monday, March 06, 2006 4:21 PM To: [email protected] Cc: Larry Feigen Subject: M202: Multi-module builds and Maven plugins Here is a weird situation we are having: I have a maven plugin that maps a type ("osgi-bundle") to a .jar. I also have a multi-module build. This build has three tiers. In the upper layer pom file, I reference the osgi-bundler plugin in the "build" section, even though at the upper layer nothing is built (or referenced via dependency) with that type. Then in the middle tier multi-module build, we reference some of the osgi-bundle types (because we want those osgi-bundles to be included in every test that is run). Then in the lowest tier, we build a real osgi-bundle type. Here is the behavior we are seeing: If we build from the top directory (which is our build "monkey" does) all of the osgi-bundle types are being uploaded to the maven repository with the "osgi-bundle" extension (which is wrong - they should have gotten mapped to ".jar"). If we build from the individual directory (the lowest tier) instead, the jar is put into the maven repository properly with the "jar" extension. We have tried the following: 1. Remove the reference to the plugin in the top-most pom file. The trouble with this is that the middle layer pom files, which reference dependencies of type osgi-bundle, do not know the osgi-bundle -> jar mapping and hence cannot find the dependent things, because it is looking for "thing.osgi-bundle" rather than "thing.jar". 2. Simply live with "osgi-bundle" in the repository. The problem with that is then when we *do* build from the lowest tier, it cannot find its dependencies, because it is looking for "thing.jar" (since it has the proper mapping) and not finding it, because in the repository it is in there as "thing.osgi-bundle"! 3. We have tried various combinations of having an osgi-bundle dependency in the top level pom (hoping this would cause the mapping to get loaded) or adding a reference to the osgi-bundler plugin in all the tiers. Can someone please help with this? This is extremely important to our adoption of maven. What we have is for the build "monkey" to be building from the top layer, and who is responsible for deploying jars. However, individual developers are building in the particular modules they are working on. Suffice to say, this is not currently working right now! John Wells (Aziz) [EMAIL PROTECTED] _______________________________________________________________________ Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it. _______________________________________________________________________ Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
