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: | CosChecker.cleanGeneratedClassfiles ineffective | ||
---|---|---|---|
Product: | projects | Reporter: | Jesse Glick <jglick> |
Component: | Maven | Assignee: | Milos Kleint <mkleint> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | ||
Priority: | P3 | ||
Version: | 7.2 | ||
Hardware: | PC | ||
OS: | Linux | ||
Issue Type: | DEFECT | Exception Reporter: | |
Bug Depends on: | |||
Bug Blocks: | 204907 |
Description
Jesse Glick
2012-03-21 00:34:53 UTC
what I understood from a chat with jlahoda: the default behaviour is after clean build keep the external build's classes around until Run is triggered, then all extrnally built classfiles are deleted and replaced by IDE's own. A marker is placed into the output directory and any subsequent file save just copies the IDE's class file. The purpose of the COSChecker appears to be to suppress this behaviour and attempt to skip the "delete external, copy all IDE's classfiles" step and always just copy the single class files. That might be because of the resource files we copy on our own.. at least one of the reason why it's like that is to support external CoS dependent things, like jrebel or javeleon works as intended within the current constraints. Why not delete the call to cleanGeneratedClassfiles, given that it does nothing in this context? Integrated into 'main-golden', will be available in build *201210120002* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-golden/rev/5b1815adfcfb User: Milos Kleint <mkleint@netbeans.org> Log: #209814 comment out noop code and fix handling when project is closed |