Community
Participate
Working Groups
When you use the repository transformer (Repo2Runnable) application and you pass in a list of IUs to transform, it treats that list as complete. That is, you just can't pass a root and expect it to automatically get everything under it. Pascal what are your thoughts on this? Are we going to run into the same problem as in the mirror app? (and why we don't do the transitive closure there yet either with the version ranges)
You are correct this is more or less the same problem than the mirroring application. Here are the set of problems that come to mind - Platform dependencies. How are dependencies that are protected by filters considered? (e.g. Do I download all SWT fragments?) - Resolve may ends up creating an "invalid" target because this operation would not take into account the dependencies of the system we are building. We could do something more general and follow all the possibilities, but then we could process too much. If we want to do something here, the easiest is to do the work equivalent to the sliver and include everything every dependency (in the case of SWT, we would dl all the fragments).
here we don't have to follow dependencies per se. just the things listed in the features right? This feels like the stuff we have to do in target provisioning (perhaps there is some reuse opportunity there). Not we are also looking at adding some similar (transitive walking) function in publisher for figuring out versions for the things in features (given a feature in a product, find all the versions it implies).
*** This bug has been marked as a duplicate of bug 291284 ***
