Issue 762 in moose-technology: VerveineJ keeps the history of old entities, when invoked from the Moose interface
Status: New Owner: tudor.gi...@gmail.com Labels: Type-Defect Priority-Medium
New issue 762 by usman.bh...@gmail.com: VerveineJ keeps the history of old entities, when invoked from the Moose interface http://code.google.com/p/moose-technology/issues/detail?id=762
First, I invoke VerveineJ from Moose menu to analyse a program A. It analyses the program and imports its entities in a moose model. I invoke VJ once more from moose menu to analyse another program B. When VJ is executed and the entities of program B are imported, I also find in the same model the entities related to the program A. So, VerveineJ keeps the history of old entities, when invoked from Moose interface.
I think the problem can be resolved by deleting output.mse once VJ has finished its analysis and the entities are imported in a moose model.
On Wednesday 14 December 2011 17:10:09 moose-technology@googlecode.com wrote:
Status: New Owner: tudor.gi...@gmail.com Labels: Type-Defect Priority-Medium
New issue 762 by usman.bh...@gmail.com: VerveineJ keeps the history of old entities, when invoked from the Moose interface http://code.google.com/p/moose-technology/issues/detail?id=762
First, I invoke VerveineJ from Moose menu to analyse a program A. It analyses the program and imports its entities in a moose model. I invoke VJ once more from moose menu to analyse another program B. When VJ is executed and the entities of program B are imported, I also find in the same model the entities related to the program A. So, VerveineJ keeps the history of old entities, when invoked from Moose interface.
I think the problem can be resolved by deleting output.mse once VJ has finished its analysis and the entities are imported in a moose model.
definitely
When it starts VJ looks for the file output.mse. This allows incremental parsing of projects.
nicolas
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Updates: Labels: Milestone-4.6 Component-Finder
Comment #1 on issue 762 by tudor.gi...@gmail.com: VerveineJ keeps the history of old entities, when invoked from the Moose interface http://code.google.com/p/moose-technology/issues/detail?id=762
As Nicolas said, the problem is rooted in VerveineJ appending information to an existing output.mse.
The solution should probably be to rename the output.mse to the name of the target folder just after parsing and before importing.
Updates: Labels: -Milestone-4.6 Milestone-4.7
Comment #2 on issue 762 by tudor.gi...@gmail.com: VerveineJ keeps the history of old entities, when invoked from the Moose interface http://code.google.com/p/moose-technology/issues/detail?id=762
(No comment was entered for this change.)
Updates: Labels: -Milestone-4.7
Comment #3 on issue 762 by tu...@tudorgirba.com: VerveineJ keeps the history of old entities, when invoked from the Moose interface http://code.google.com/p/moose-technology/issues/detail?id=762
Not going to be solved in 4.7
Comment #4 on issue 762 by anquetil...@gmail.com: VerveineJ keeps the history of old entities, when invoked from the Moose interface http://code.google.com/p/moose-technology/issues/detail?id=762
Could change the behaviour of VerveineJ: - by default it would remove existing output.mse file - if one wants to add entities to an existing mse file, one would have to say so explicitly (command line argument)
Updates: Labels: Component-VerveineJ
Comment #5 on issue 762 by tu...@tudorgirba.com: VerveineJ keeps the history of old entities, when invoked from the Moose interface http://code.google.com/p/moose-technology/issues/detail?id=762
I think this would be a nice behavior. That is because there is little advantage in adding to the existing mse file. It would be cleaner to create a new one all the time.
Updates: Status: Fixed
Comment #6 on issue 762 by anquetil...@gmail.com: VerveineJ keeps the history of old entities, when invoked from the Moose interface http://code.google.com/p/moose-technology/issues/detail?id=762
Added new -i command line argument to say explicitly that one wants to reuse an existing mse file Without it, possibly existing mse file is overwritten
Updates: Labels: Milestone-4.7
Comment #7 on issue 762 by tu...@tudorgirba.com: VerveineJ keeps the history of old entities, when invoked from the Moose interface http://code.google.com/p/moose-technology/issues/detail?id=762
Thanks.
Actually, I just realized that another better solution would be to *not* reimport implicitly and silently an existing output.mse file.
This features was created to allow incremental parsing, but when one wants to do so, one should specify an option to explicitly say so. And the behaviour by default should be to ignore (erase) any pre-existing output.mse file.
nicolas
----- Mail original -----
De: moose-technology@googlecode.com À: moose-dev@iam.unibe.ch Envoyé: Mercredi 14 Décembre 2011 18:10:09 Objet: [Moose-dev] Issue 762 in moose-technology: VerveineJ keeps the history of old entities, when invoked from the Moose interface Status: New Owner: tudor.gi...@gmail.com Labels: Type-Defect Priority-Medium
New issue 762 by usman.bh...@gmail.com: VerveineJ keeps the history of old entities, when invoked from the Moose interface http://code.google.com/p/moose-technology/issues/detail?id=762
First, I invoke VerveineJ from Moose menu to analyse a program A. It analyses the program and imports its entities in a moose model. I invoke VJ once more from moose menu to analyse another program B. When VJ is executed and the entities of program B are imported, I also find in the same model the entities related to the program A. So, VerveineJ keeps the history of old entities, when invoked from Moose interface.
I think the problem can be resolved by deleting output.mse once VJ has finished its analysis and the entities are imported in a moose model.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-
moose-technology＠googlecode.com -
Nicolas Anquetil