This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | deadlock while creating new maven web app | ||
---|---|---|---|
Product: | projects | Reporter: | Lukas Jungmann <jungi> |
Component: | Maven | Assignee: | Milos Kleint <mkleint> |
Status: | VERIFIED FIXED | ||
Severity: | normal | CC: | anebuzelsky, mkleint, mmirilovic |
Priority: | P1 | Keywords: | RANDOM, TEST |
Version: | 6.x | ||
Hardware: | PC | ||
OS: | Linux | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
Lukas Jungmann
2009-11-19 05:06:16 UTC
please verify. Might be worth backporting to 6.8 http://hg.netbeans.org/core-main/rev/187790b39c72 Integrated into 'main-golden', will be available in build *200911241400* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main/rev/187790b39c72 User: Milos Kleint <mkleint@netbeans.org> Log: #177188 unify synchronization lock for both EndorsedCP and BootCP v in trunk. I agree it's worth to backport this to 6.8 - feel free to do that. Thanks! review: fix is correct. By unifying the lock between EndorsedClassPathImpl and BootClassPathImpl we assure that sections don't get executed simultaneously waiting on each other, and deadlock is gone. Reopening per HR process. Milosi, prepare backport to 6.8. Thanks. OK, we'll do that for RC2/FCS not for RC1 Marian, what exactly does that mean? can i integrate today to release68 clone? or do I have to wait for some later "go"? Yes, you can integrate it today into release68 ... just wanted to stress that this is not a stoper for RC1 that will be released today. This issue was already fixed in release68 : http://hg.netbeans.org/release68/rev/67e1cd9be2ea ... wasn't it ? v. in 6.8rc2 |