From: Patrice C. <ch...@cs...> - 2003-06-27 16:24:50
|
Clyde Ruby wrote: > At 09:51 AM 6/27/2003 -0500, Gary T. Leavens wrote: > >> Hi Patrice, Curt, >> >> I just wanted to note that Curt's explanation, while accurate, doesn't >> take into consideration the scenario where you change a file in MJ, >> then before rebuilding in MJ, go over to JML2 and build in a >> subdirectory there. So while there is no mjc bug, and if you do >> things as you "should" by building on the MJ side first whenever you >> make a change there, it's easy to get confused, and thus it would be >> best to have the makefiles protect us from our own human falibility. >> >> -- > > Gary, Curt, Patrice, > > I think the way this happened to me is that I did an update in MJ, > went back to JML and did a "make debug-build". Similar to what has happened to me again this morning. I committed changes to MJ, then JML2. Returning to JML2 to make further changes and build causes .class files to be created in JML2/org/multijava ... . Note that I didn't go back to the MJ directory to rebuild because I had changed nothing, ... but I realized that committing does change the files (e.g. updating rcs tags) ... If someone has an idea about how to fix this problem, please let us know, otherwise we will be looking into it a little later on. Cheers, Patrice |