Community
Participate
Working Groups
Build Identifier: 20100218-1602 This is a request, eclipse needs to create a separate thread for the processes. If the reason it's single threaded is too ensure things loaded in a project are done in a particular order then create a new thread per component. I'm trying to checkout but I'd like to clean and build a project while checking out. This has essentially stopped me from being able to test. This isn't the only case also, I'd be happy to add the fix so long as I can grab the code and check it in and know my efforts wouldn't be wasted. Reproducible: Always Steps to Reproduce: 1. Start a long process 2. Try to do something else that's added to the process queue 3. ???? 4. Profit?
(In reply to comment #0) > This is a request, eclipse needs to create a separate thread for the processes. This is a case-by-case basis thing. Only the action that is being performed would know whether it should be blocking any other jobs. > If the reason it's single threaded is too ensure things loaded in a project are > done in a particular order then create a new thread per component. I'm trying > to checkout but I'd like to clean and build a project while checking out. This > has essentially stopped me from being able to test. What version control system (plug-in) are you using?
Subclipse is the plug-in, so wait let me get this straight the plugin decides whether that is blocking or not?
(In reply to comment #2) > Subclipse is the plug-in If their checkouts are doing a full block you need to file a bug with them at their website. > so wait let me get this straight the plugin decides > whether that is blocking or not? That's the gist of it. Anyone can spawn a bunch of jobs to do "stuff". What that "stuff" is, well, only whoever spawned it (the plug-in) would know. If I'm doing a full build of the entire workspace then yeah I need to lock the whole workspace. If I'm just parsing one file then I probably don't need to lock the entire workspace but just lock the one file, right? It is up to the code spawning the job (the plug-in) to decide how "wide" their lock needs to be. Am I making any sense here?
Perfect sense, thanks!
