--- "matthew.hawthorne" <[EMAIL PROTECTED]> wrote: > Stephen Colebourne wrote: > > Our maven scripts now depend on commons-build, > however > > this is of course not included in the release > zips. > > This is a problem and means that maven cannot be > used > > in releases. > > How is this any different that before, when the > Maven scripts depended > on jakarta-commons/project.xml?
It isn't, but its still wrong. The point is that it is difficult to obtain the commons-build/project.xml file. It can only be done via view-cvs really. Perhaps we could start by renaming project.xml in commons-build to project-common.xml. Then a release could copy it from commons-build to the individual project. Also, what about having the extends clause use a variable to define the location of commons-build. The default could be 'same folder' for releases. Stephen --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
