Separation of src and target generated artifacts
------------------------------------------------
Key: CORE-29
URL: http://team.andromda.org:8080/jira/browse/CORE-29
Project: AndroMDA Core
Type: Improvement
Reporter: Martin West
Assigned to: Chad Brandon
One of the problems I have with a copy strategy is with eclipse. I cannot have
my modified copy of java file and the generated one both in the eclipse source
folders. It complains of a duplicate class. It occurred to me that you could
solve this problem and possibly the jsp modification problem by tweaking the
generator to have a modifications directory. The process would be:
1. Do the first build, this would generate the source into the src / target
directories.
2. Move a file from the src generation tree to the modifications directory tree
and modify it.
3. On subsequent builds the generator would check for the existence of the file
in the modification directory and only regenerate if it did not exist in the
modifications directory and the src directory tree.
This would give you a clearer idea of what you had and had not modified. There
would only be one copy of a "src" file. By src I mean the files that are
generated and are expected to be modified.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://team.andromda.org:8080/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-------------------------------------------------------
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
_______________________________________________
Andromda-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/andromda-devel
