Community
Participate
Working Groups
The launcher fragments currently specify an upper bound on their Fragment-Host directive. The coupling between the host and the fragment is very loose. The only real dependency here is on the package for the JNIBridge and Main classes as well as Main#run(String[]) and the default constructor for Main. We can at least relax the dependency to [1.0.0, 2.0.0) Bug 323488 is an example of p2 resolution problems that come from restrictions here.
+1 I think this would be a fine thing to do for 3.7. At runtime the relationship is quite artificial since by the time the framework is up and discovers a fragment to attach to the launcher host we are way past the point of loading and executing the launcher (both java and native portions have been loaded already).
Andrew, I'm not sure if you want to do this at this stage in 3.7. Feel free to defer it.
Defer to 3.8
Move all 3.8 bugs to Juno.
Moving to inbox
Don't think we should do that right now.
Assigning to Arun. Arun feel free to close as wontfix. But if you see value in doing this I suggest we do it now for M7. Otherwise I would close as wontfix.
(In reply to Thomas Watson from comment #7) > Assigning to Arun. Arun feel free to close as wontfix. But if you see > value in doing this I suggest we do it now for M7. Otherwise I would close > as wontfix. Closing as wontfix. This bug has gone on long enough. If it proves to be painful in the future we can consider fixing again.
