Community
Participate
Working Groups
Currently, a source archive attachment for a binary jar can have one explicit root, or multiple auto-detected roots. It would be useful to be able to have mutliple explicit roots, or be able to spec an explicit root within the archive where auto-detection of roots can start from. For example, to ship source for JUnit 3.8 and JUnit 4.0 in the same archive, auto-detect would not work well (since source names overlap). It would be possible with distinct/explicit roots. One could imagine a similar scenario where each explicit root could have sub-roots that need auto-detection.
Also see bug 202462. There are cases where plug-ins may want the flexibility to bundle source in the same archive.
If we could do this, it would help clean up extra folders in a binary plug-in project that might otherwise confuse users (ie. why is there a second MANIFEST.MF in my project?).
*** This bug has been marked as a duplicate of bug 173641 ***
Oops, this is not a dup of bug 173641 (which is about specifying multiple source attachments)
Targeting M5
Not for 3.5