On Saturday 21 July 2007 20:36, Wouter de Vaal wrote: > Hi, > > I'm experimenting with pax construct and I was wondering the following > thing: When using pax construct one needs to do pax-import-bundle for all > bundles used within the project, especially when using eclipse > (right?), but with a lot of dependencies, my project root dir gets > cluttered with what I call external bundles (like the whole bundle > spring osgi generated bundles). > What I did is create a folder external-bundles, copy the external > bundles there and update the main pom and all the project pom's. > > So my question is, can this be automated? Or can this already be done > and did I just miss something?
This is probably my fault. Initially, Pax Construct used imported/, compiled/ and wrapped/ folders in the main project directory. I thought that created too deep levels and not giving enough overview. Perhaps a middle ground is needed, where the "compiled/" remain as now is the case and the wrapped and/or imported/ are moved a level down. Cheers Niclas _______________________________________________ general mailing list general@lists.ops4j.org http://lists.ops4j.org/mailman/listinfo/general
