Community
Participate
Working Groups
I'm not sure that strictly speaking this is a bug, but its a bit mysterious but judging from blog and bug traffic it seems like I'm not the only one who has run afoul of it. When I add Delta pack as an "Installation" product source, my export hangs under Mac. When I add it as a directory all seems to be well. (This appears to be not directly related to the well known JVM symlink bug, but its hard to know for sure because I can't even do a kill -3 on eclipse when it happens.) Does anyone have any ideas about what might be happening here and/or how we can give users a clue that setting up the delta pack that way is not the way to go? Sorry for vagueness here..
OK, scratch that previous explanation. I thought that that had solved the issue, but in fact it was my simplification of taking my non-native (win32) targets out. When I put Windows back in, it failed in the typical place, while generating metadata at 48%. So it sounds like our old friend bug 276005. But the UI issue has been fixed and I'm certain that I do not have a vm checked. One thing that is interesting is that each target gets to a certain plugin before things hang. That plugin happens to be org.junit.source_3.8.2.201006061616. And I note that it isn't the next plugin in the list (assuming they're all generated alphabetically) as when I remove it it doesn't change anything. So at this point I'm wondering if anyone has pointers to how I can diagnose further, given that I can't seem to get a stack trace with kill -3.
Currently we are not actively enhancing PDE build anymore. Therefore, I close this bug as WONTFIX. Please reopen, if you plan to provide a fix.
