Actually the opposite. We have several non-base classes checked into svn and I need to keep them from getting overwritten by the generate plugin. What we are currently doing is keeping the svn files in the src directory and then generating all classes into a folder under target. After generate completes the files in src are copied into the generated folder before compilation. By doing this we never worry about overwriting a file in svn with generated content but it does make our build a little fragile. I'm wondering if there is a better solution.
Geoff On Aug 28, 1:42 pm, Marvin Froeder <[email protected]> wrote: > You mean you don't wanna/need to version non-base? > VELO > > On Fri, Aug 28, 2009 at 2:30 PM, geoff.schneider > <[email protected]>wrote: > > > > > Hi All > > > We are updating our auto-generation to use 3.3.0 and I had a question > > about best practices. We pretty regularly need to make modifications > > to the non-base bean classes that are generated by gas3. These are > > then stored in our svn and combined with the other generated as files > > during the the build. What I'm wondering is if there is a better way > > to achieve this same result without copying files from the src > > directory to a generated sources directory before compilation? Thanks > > > Geoff --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Flex Mojos" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/flex-mojos?hl=en?hl=en http://blog.flex-mojos.info/ -~----------~----~----~----~------~----~------~--~---
