Navigation Menu

Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

VerveineJ keeps the history of old entities, when invoked from the Moose interface #762

Closed
seandenigris opened this issue Aug 3, 2015 · 7 comments
Closed

VerveineJ keeps the history of old entities, when invoked from the Moose interface #762

seandenigris opened this issue Aug 3, 2015 · 7 comments

Comments

@seandenigris
Copy link
Contributor

Originally reported on Google Code with 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.

Reported by usman.bhatti on 2011-12-14 17:09:47
@seandenigris
Copy link
Contributor Author 

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.

Reported by tudor.girba on 2011-12-15 23:52:14

  • Labels added: Milestone-4.6, Component-Finder

@seandenigris
Copy link
Contributor Author

Reported by tudor.girba on 2012-02-11 09:46:35

  • Labels added: Milestone-4.7
  • Labels removed: Milestone-4.6

@seandenigris
Copy link
Contributor Author 

Not going to be solved in 4.7

Reported by tudor@tudorgirba.com on 2012-11-24 23:27:31

  • Labels removed: Milestone-4.7

@seandenigris
Copy link
Contributor Author 

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)

Reported by anquetil.nicolas on 2012-11-26 18:55:53

@seandenigris
Copy link
Contributor Author 

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.

Reported by tudor@tudorgirba.com on 2012-11-26 20:18:51

  • Labels added: Component-VerveineJ

@seandenigris
Copy link
Contributor Author 

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

Reported by anquetil.nicolas on 2012-11-27 15:02:56

  • Status changed: Fixed

@seandenigris
Copy link
Contributor Author 

Thanks.

Reported by tudor@tudorgirba.com on 2012-11-27 15:31:53

  • Labels added: Milestone-4.7

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@seandenigris