On 12/14/06, Greg Reddin <[EMAIL PROTECTED]> wrote:
shale-master.pom - This is the base POM for the whole project. It inherits from an org.apache parent. We only have to release a new version of this if the information contained in it changes, right (i.e. add new committer, mailing list, svn changes, etc.) And we can release it independently of everything else?
Yes, shale-master is released independently. It has to be released in advance of the framework so we don't have a snapshot as a <parent>.
shale-parent.pom - The base POM for shale subprojects. It defines the modules, base dependencies, etc. If we release anything (shale- remoting, for example), we also have to release shale-parent, which means we have to release everything, right?
Right now, the build process is set up to release everything together. It's not a Maven requirement-- consider the Maven plugins, which have a parent pom, yet get released one at a time. Whether to release "the framework" together or in pieces is just something we need to decide, figure out how to communicate to users, and then adjust the build to match. What about shipping shale-tiles in a directory other than 'lib' to indicate that it isn't part of the "normal" distribution? Something like the 'contrib' directory in Struts 1.2 that includes struts-el and struts-faces. -- Wendy
