Model Archiver appends the current model version number to each dependency
inside the model it's deploying
----------------------------------------------------------------------------------------------------------
Key: MAVEN-51
URL: http://jira.andromda.org/browse/MAVEN-51
Project: Maven Plugins
Type: Bug
Versions: 4.0-M1
Environment: Mac OS X 10.4, JDK 1.4.2, Maven 2.0.2
Reporter: Tim Dysinger
Assigned to: Chad Brandon
Priority: Blocker
I have my own profile which I wrote on top of Andromda's profiles. When I
publish it using model-archiver, it appends the version number of _my_ profile
to all the andromda profiles.
For example, I have a profile called profile-message which is version 0.1.
When it's published all the andromda-profile-xxx dependencies get appended with
0.1 which doesn't work
andromda-profile-xml-4.0-M1-SNAPSHOT.xml.zip
becomes
andromda-profile-xml-4.0-M1-SNAPSHOT-0.1.xml.zip
inside profile-message-0.1.xml.zip when it's published.
I am afraid that Andromda depends on the model-archiver functioning this way to
publish it's own models.
--
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: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
