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: | Use EventSpy for more reliable build progress tracking | ||
|---|---|---|---|
| Product: | projects | Reporter: | Jesse Glick <jglick> |
| Component: | Maven | Assignee: | Milos Kleint <mkleint> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | theanuradha |
| Priority: | P2 | Keywords: | PERFORMANCE |
| Version: | 7.0 | ||
| Hardware: | All | ||
| OS: | All | ||
| URL: | http://jira.codehaus.org/browse/MNG-4936 | ||
| Issue Type: | ENHANCEMENT | Exception Reporter: | |
| Bug Depends on: | 206791 | ||
| Bug Blocks: | 198650, 206925, 227541 | ||
| Attachments: | Sources of demo | ||
|
Description
Jesse Glick
2011-01-06 14:57:00 UTC
Created attachment 108640 [details] Sources of demo See bug #198650 comment #4. Replacing MavenCommandLineExecutor.FindByName is a key driver; this is way too slow on big reactors. (Also cancellation does not seem to work reliably.) Not in 7.2. (In reply to comment #2) > Replacing MavenCommandLineExecutor.FindByName is a key driver Just realized that this can be done more easily and efficiently by just scanning Maven output for the error line after "After correcting the problems, you can resume the build with the command": mvn <goals> -rf :$artifactId http://hg.netbeans.org/core-main/rev/bd3fb75c97fd and a few previous commits. for maven 3.x we now collect events from the EventSpy and create at Session->project->mojo tree that we use to find out where to resume from. For the future we could even show the entire node tree with links back to the output printed. Cool. You saw the blocked issues, right? |