On Fri, Apr 8, 2011 at 11:08 AM, Carsten Ziegeler <[email protected]> wrote: > > ...my wishlist for the next version is: >... > d) it would be nice if the bundle list is visible to the Maven > dependency resolution... ... > I guess from this list d) is the hardest - in addition we need > additional metadata for artifacts like the bundle start level which we > can't simply add in the pom.xml. > So I think we should forget about d) (unless someone knows how to do > it), and define everything in a single xml file....
Not having d) is a serious problem IMO, as it means bypassing dependency resolution, snapshot checks etc. completely. This leads to subtle problems at build time, which are easy to overlook in a large multi-module build. IIUC it's not possible to define everything in the pom? If we need an external xml file as is now, could we just define the bundle versions in the pom, and use the xml file only for additional info? What's in the pom would act like the dependencyManagement section in a parent pom, and the xml file would point to bundles but not mention their version, and can include any useful additional information. -Bertrand
