Re: [dev] IMPORTANT ANNOUNCEMENT: HEDABU DOESN'T EXIST ANYMORE

Bjoern Milcke wrote: > Now, this is the output of cwsresync: > >Resyncing 'inc/SchXMLExportHelper.hxx' remove file: removed, schedule > commit. > > This is the output of cwsanalyze: > >A inc/SchXMLExportHelper.hxx file removed on MWS but changed on CWS >M inc/SchXMLExpo

Re: [dev] IMPORTANT ANNOUNCEMENT: HEDABU DOESN'T EXIST ANYMORE

Hi Bjoern, >> However, Mathias seemed to suggest that cwsanalyze is able to detect >> problems which are not detected by cwsresync. At least this is how I >> understood his mail. And that's the part I don't understand. > > I don't understand that, too. But, I have evidence that it is true. > ...

Re: [dev] IMPORTANT ANNOUNCEMENT: HEDABU DOESN'T EXIST ANYMORE

Hi Frank, I know that cwsresync cannot detect everything. No automated tool can, and knowing and understanding what you do instead of relying on automatisms is always a good idea :) However, Mathias seemed to suggest that cwsanalyze is able to detect problems which are not detected by cwsresyn

Re: [dev] IMPORTANT ANNOUNCEMENT: HEDABU DOESN'T EXIST ANYMORE

Hi Rüdiger, > there always may be special cases which cannot be detected automatically. > Image f.e. on your CWS you removed a header. With m209's hedaburemove01 > that header got moved on the master workspace. CVS does not know about > moving files, so it is a removal and a new file elsewhere.

Re: [dev] IMPORTANT ANNOUNCEMENT: HEDABU DOESN'T EXIST ANYMORE

Frank Schönheit - Sun Microsystems Germany wrote: Hi Mathias, In case you wonder how you can find out which header files you might have changed: use cwsanalyze to find all changes in your CWS. This is the best way to avoid problems, it is known that not all possible combinations of header chan

Re: [dev] IMPORTANT ANNOUNCEMENT: HEDABU DOESN'T EXIST ANYMORE

Hi Mathias, > In case you wonder how you can find out which header files you might > have changed: use cwsanalyze to find all changes in your CWS. This is > the best way to avoid problems, it is known that not all possible > combinations of header changes cause errors or alerts in the resync > pro

Re: [dev] IMPORTANT ANNOUNCEMENT: HEDABU DOESN'T EXIST ANYMORE

Rüdiger Timm wrote: > If you did not touch headers, no action is required. > > If you changed existing headers or introduced new ones, check in > prj/d.lst, whether those headers are subject to 'headbu' action. If they > are not: no action required. > > If your header was 'hedabu'ed it most pr

Re: [dev] IMPORTANT ANNOUNCEMENT: HEDABU DOESN'T EXIST ANYMORE

Actually, fist do resync, "deliver -delete", update sources, replicate changes in headers, if needed- move headers+correct "#includes", build sources. You will see quite quickly if you did something wrong, what to to will be obvious... Vladimir Was the only thing the move of some headers? D

Re: [dev] IMPORTANT ANNOUNCEMENT: HEDABU DOESN'T EXIST ANYMORE

Hi Rüdiger, Bjoern Milcke wrote: Hi Vladimir, IMPORTANT IMPORTANT IMPORTANT IMPORTANT IMPORTANT IMPORTANT === [...] Do we have to do any changes in CWS chart2mst3, where we added a new module with new headers? -Bjoern I more d

Re: [dev] IMPORTANT ANNOUNCEMENT: HEDABU DOESN'T EXIST ANYMORE

Bjoern Milcke wrote: Hi Vladimir, IMPORTANT IMPORTANT IMPORTANT IMPORTANT IMPORTANT IMPORTANT === Hi all, the ongoing SRC680 m209 build brings important change to our build environment. Since that milestone hedabu procedure will not wo

Re: [dev] IMPORTANT ANNOUNCEMENT: HEDABU DOESN'T EXIST ANYMORE

Hi Vladimir, IMPORTANT IMPORTANT IMPORTANT IMPORTANT IMPORTANT IMPORTANT === Hi all, the ongoing SRC680 m209 build brings important change to our build environment. Since that milestone hedabu procedure will not work. To make it happen, m

[dev] IMPORTANT ANNOUNCEMENT: HEDABU DOESN'T EXIST ANYMORE

IMPORTANT IMPORTANT IMPORTANT IMPORTANT IMPORTANT IMPORTANT === Hi all, the ongoing SRC680 m209 build brings important change to our build environment. Since that milestone hedabu procedure will not work. To make it happen, many headers are