Last modified check does not work with merge mappings
-----------------------------------------------------
Key: CORE-117
URL: http://jira.andromda.org/browse/CORE-117
Project: AndroMDA Core
Type: Bug
Versions: 3.2 RC1
Environment: Linux
Reporter: David Allen
Assigned to: Chad Brandon
When the AndroMDA configuration file has a mergeMappingsUri specified for any
cartridges, the resource history file in the temp directory contains each of
the merged vsl files under /tmp/<user.name>/.andromda/velocity/merge... While
monitoring these directories with AndroMDA running, the velocity/merge
directory only existed while the bpm4struts cartridge was running (the one
which has a mergeMappingsUri provided by the andromdapp generator). Once other
cartridges started running, the directory was gone; however, the history file
always contains those paths which are used in subsequent runs to compare dates
between the model and those files.
Clearly it is a problem if these files disappear but are left in the history.
On the other hand, perhaps they should not be in the history in the first place
since they are not derived from the model. Actually, they are derived from the
mergeMappingsUri file which could change on its own independently from the
model, but this would make the last modified check more complex to include
things like that.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.andromda.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
