| Summary: | R3 and R3_1 contain unnecessary files | ||
|---|---|---|---|
| Product: | [Tools] GEF | Reporter: | Jacek Pospychala <jacek.pospychala> |
| Component: | RelEng | Assignee: | Anthony Hunter <ahunter.eclipse> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | ahunter.eclipse |
| Version: | 3.1 | ||
| Target Milestone: | 3.4.0 (Ganymede) RC3 | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
Jacek Pospychala
Yes, I know of the issue. Since refactoring does not preserve history (like SVN), when I refactored these classes, I copied them in CVS to maintain their version history. I fixed the issues you mentioned in the 3.4 and R3_3_maintenance streams, which are the two active streams when the refactor occurred. I did not care about the older streams as they are effectively dead. There are no further builds in R3_Maintenance and R3_1_Maintenance. I can go back into these streams and remove these new entries, but I am wondering why we would do this. CVS access is meant for GEF development. Since there is no development in these streams, it does not make sense to address this issue. Why do we need CVS access to these old streams? The GEF SDK has the source right? Anthony, thanks for quick response. If you know then ok, I can live with WONTFIX :) It's just hard to figure out what's happening if you check out R* code and see it doesn't even compile. I needed code to check possibility of patch for our internal product based on GEF 3.0. So CVS was more comfortable than creating patch using SDK zip. (In reply to comment #2) > I needed code to check possibility of patch for our internal product based on > GEF 3.0. So CVS was more comfortable than creating patch using SDK zip. OK, I get it, creating a patch pretty much requires CVS. If this is painful for you, let me know the stream you want fixed and I can make it so. it's R3_Maintenance. Alternatively you could create folder (e.g. removed/history/...) not on classpath to contain these files to keep the history. thanks (In reply to comment #1) > I did not care about the older streams as they are effectively dead. There are > no further builds in R3_Maintenance and R3_1_Maintenance. Fixed the CVS repo issue for R30_Maintenance, R31_Maintenance and R32_Maintenance |