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.

Bug 134694 - Apisupport does not play well with SCMs that use strict locking
Summary: Apisupport does not play well with SCMs that use strict locking
Status: RESOLVED WONTFIX
Alias: None
Product: apisupport
Classification: Unclassified
Component: Templates (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Jesse Glick
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-05-07 18:54 UTC by _ rkubacki
Modified: 2008-05-09 02:22 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description _ rkubacki 2008-05-07 18:54:35 UTC 
Using NetBeans with perforce is a pain and most of wizards like new project template will fail at unexpected place
because it cannot write to some file. This often leaves sources in the state of middle of transaction.

Typically
- project infrastructure wants to access nbproject/* files + build.xml
- apisupport needs to update layer.xml and Bundle.properties files
Comment 1 Jesse Glick 2008-05-09 02:22:50 UTC 
Sorry, you would need to solve this at a more general level by having an integration module for Perforce that acquires
locks on demand when FileObject write methods are called.