Summary: | [doc] [PII] | ||
---|---|---|---|
Product: | [Tools] GEF | Reporter: | Nick Boldt <nboldt> |
Component: | GEF-Legacy GEF (MVC) | Assignee: | Anthony Hunter <ahunter.eclipse> |
Status: | NEW --- | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | CC: | ahunter.eclipse, davidms, nboldt, nyssen |
Version: | unspecified | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Linux | ||
Whiteboard: |
Description
Nick Boldt
2008-01-15 17:53:17 EST
I trust you're still running builds periodically on emf.torolab to see these problems. As you prolly know, you can also run CHKPII locally to verify your fixes before committing them and spinning a build. I expect Dave is keeping emf.toro current with the latest releases of CHKPII? Nope, I am not, and I don't plan to. CHKPII testing needs to be done locally. I have the PII tool and I will run on our code again. Anthony, as the doc plug-ins are now properly build again, maybe we could check this as well to have the documentation in a fine shape again? Unset target milestone as the specified one is already passed. |