Hi,
as promised I did some testing with beta 1. Looks good so far (overall), but I
found some issues (only one is prio 2) and put them into issuezilla.
(Much more time needed to test, but anyway...)
Because I've got noth enough time, I didn't check for duplicates.
Regards,
Thomas
P.S.: here is the raw data of what I've hacked into issuezilla, sorry no time
to copy issue numbers here:
Issue 6386: Name of template parameters for classes ignored in explorer and
class property panel
Steps to reproduce:
1. create a class
2. in its property panel, create a template parameter
3. select the template parameter in the explorer
4. enter a name for the template parameter
5. navigate to the class in the property panel
The name is not shown in the explorer ("TemplateParameter:"), and also it is
not shown in the classes property panel ("TP (unnamed TemplateParameter)"). But
in the Source tab, the template parameter is correctly generated with its name.
Issue 6387: Link to template parameter in class property panel is not navigable
Steps to reproduce:
1. create a class
2. in its property panel, create a template parameter
The created property panel is shown as a link in the classes property panel,
but clicking on it does nothing.
Issue 6388: Base class not available for classes that are base class of a
classifier role in another seq/collab diagram
Steps to reproduce:
1. create a class, give it a name
2. create a sequence diagram with a classifier role
3. add the class as a base to the classifier role
4. create another sequence diagram (or collaboration diagram) and another
classifier role in it
The second classifier role cannot have the same base class as the one in the
other diagram.
There is always a way to circumvent this, so I suggest to drop the restriction.
It is more in the way then helpful, for a long time now.
Issue 6389: Loading project fails when done several times
Steps to reproduce:
1. Save a project and open it several times (3 or 4 times)
Eventuall the following error happens:
Cause : org.argouml.model.InvalidElementException:
javax.jmi.reflect.InvalidObjectException: Object with MOFID
127-0-0-1-6981beab:133fdc310a0:-8000:0000000000000C55 no longer exists.
Issue 6390: Guard and Effect too small in height when empty
Steps to reproduce:
1. create a transition in a behavioral diagram
2. navigate to its property panel
Guard and Effect fields are too small in height when empty. After adding
something, the problem is gone. After removing, these fields are again too
small in height.
Issue 6391: Argument Prop panel shows exceptions (at least when it is for an
action)
Steps to reproduce:
1. in any behavioral diagram, create an action
2. add an argument in its property panel
At the right hand of the Argument property panel, two Exceptions are shown:
"Exception caught building a control list for ..."
I found no way to fix this.
Issue 6392: Deletion of a component thows excetion
Steps to reproduce:
1. create a deployment diagram
2. create a node and make it large enough to hold a component
3. draw a component inside a node
4. delete the component with "Delete from model"
Exception in console:
org.argouml.model.InvalidElementException:
javax.jmi.reflect.InvalidObjectException: Object with MOFID
127-0-0-1-6327304:133fe07ac97:-8000:0000000000000868 no longer exists.
--
NEU: FreePhone - 0ct/min Handyspartarif mit Geld-zurück-Garantie!
Jetzt informieren: http://www.gmx.net/de/go/freephone
------------------------------------------------------
http://argouml.tigris.org/ds/viewMessage.do?dsForumId=450&dsMessageId=2889991
To unsubscribe from this discussion, e-mail:
[[email protected]].
To be allowed to post to the list contact the mailing list moderator, email:
[[email protected]]
