Stephen McConnell wrote:
Have been thinking about how to handle the packaging of 4.1.4. In an earlier email I suggested that this could be done with some fine grain manipulation in the buildfile. While that is possible - it is also an approach that can easily lead to errors due to the non-inclusion of a file in a jar because a buildfile was not updated.
<snip/>
If this sounds reasonable I would like to recruit some help from someone who can "manipulate" the file system to create the copies of the current tree under a avalon-common, avalon-spec and avalon-impl. I can then dig into seperating what is in each without loosing CVS info.
Thoughts?
I am not crazy about the idea of doing so much CVS upheaval right before a release. That would push the inclusion of this feature further out than should be included for the release timefrime I want to shoot for. In the short term, we have to go for simple or not at all. The longer term will allow us to pursue avenues like this. However, I do want us to do the easiest thing to make it possible, and no more. If we apply that philosophy to everything, we can get releases out much more frequently. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
