search

ikuraj / alloy4eclipse

Automatically exported from code.google.com/p/alloy4eclipse
0 stars 0 forks source link

Not Intuitive Behavior: Run command don't react to saved changes. #63

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Write the model:
module teste

sig E {}

sig B extends E {}

sig A extends E {}

assert WrongT {
 all a:E | a in B
}

check WrongT for 3

2. Run As -> Alloy Specification and see the counterexample

3. Delete the assert and check commands.

4. See: Error: Check WrongT for 3 not found.

What is the expected output? What do you see instead?

Expect reaction in order to new model. 
It react to old file.

What version of the product are you using? On what operating system?
Eclipse SDK Version: 3.3.2 Build id: M20080221-1800
Alloy Plug-in 0.2.28
Ubuntu Hardy Heron

Please provide any additional information below.

The Run command, in my opinions, should do the necessary actions, in order
to alloy consider the new version of file.
Or in alternative, the plugin should provide a "build" command.

Workaround.

Not found.
Using java -jar alloy4.jar teste.als

Original issue reported on code.google.com by avelinor...@gmail.com on 1 May 2008 at 10:41

GoogleCodeExporter commented 8 years ago 
I just checked your example. I can indeed see the error message if I try to 
relaunch
the commands after deleting them.

The behavior is maybe non intuitive but is coherent with other Eclipse plugin
behavior: in JDT, if you remove a main method, the Run/Run as command will not 
be
modified. The editor just warns you that removing a main method might break 
scripts
or Run commands.

We will however try to do a better job on this.

Thanks for pointing that out.

Original comment by daniel.l...@gmail.com on 1 May 2008 at 3:55