Im planning on doing something on this with the ant refactoring. On Fri, 2005-03-25 at 18:50 +0100, Chad Brandon (JIRA) wrote: > [ http://galaxy.andromda.org:8080/jira/browse/MAVEN-12?page=history ] > > Chad Brandon closed MAVEN-12: > ----------------------------- > > Resolution: Not an issue > > I'm closing this, please re-open if you think it's still applicable. > > > Provide function to separate generation and cvs'able artifacts > > -------------------------------------------------------------- > > > > Key: MAVEN-12 > > URL: http://galaxy.andromda.org:8080/jira/browse/MAVEN-12 > > Project: Maven Plugins > > Type: Improvement > > Reporter: Martin West > > Assignee: Chad Brandon > > > > > It would be nice if the build process separated out the generation > > artifacts from those that are modified and are under cvs control for > > instance. Ideally a merge architecture, but a copy/replace process is ok. > > So the process would be: > > 1. Create the project structure > > 2. Add/Create the model(s) for the project > > 3. Build first time, this would create the generation artifacts and copy > > the modifiable sources to a source area. > > 4. Subsequent builds would execute the generation process, copy in the > > modifiable sources and continue the build. Copy new modifiable sources > > created to source area, this should be possible based on modified date. > > Perhaps add a build directory under the project directory where generated > > files would go. > > Thanks. > --
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Andromda-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/andromda-devel
