Hi Scott and Pascal, I followed Pascal's suggestion to install the source bundles with the director application using naming conventions to relate them to the runtime bundles. I forked SimplePlanner: right before the slicer is called I create an optional requirement for the source bundle of each available bundle.
If this is useful to someone here is the EPL code: http://github.com/intalio/org.eclipse.equinox.p2.director.extended If you would consider this more than a temporary hack let me know and I'll file it in bugzilla re-factored as an actual patch. Cheers, Hugues. On Thu, Jul 8, 2010 at 9:21 PM, Pascal Rapicault <[email protected]> wrote: > Not that I know of. This was something we wanted to do in 3.6 but did not > manage to get to. > One difficulty is that the metadata does not capture the binary / source > relationship, so at this point one would have to go by naming convention. > > > > On 2010-07-08, at 4:49 PM, Scott Lewis wrote: > >> Hi p2ers, >> >> Is there any support anywhere for importing a bundle(s)...with p2 repo as >> source...into an Eclipse workspace as a project(s)? >> >> I imagine this could fairly readily be done...given the PDE jar import >> wizard...and p2's APIs for accessing artifacts in repos...but does it exist >> somewhere already? >> >> Thanksinadvance, >> >> Scott >> >> >> _______________________________________________ >> p2-dev mailing list >> [email protected] >> https://dev.eclipse.org/mailman/listinfo/p2-dev > > _______________________________________________ > p2-dev mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/p2-dev > _______________________________________________ p2-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/p2-dev
