At then end, users would have to use the same kind of commands we use to build our own release, woulnd't they ? If we have a per-bundle release, i'm fine with users having to build them bundle by bundle too ...
On Mon, Feb 28, 2011 at 13:44, zoe slattery <[email protected]> wrote: > PS... >>> >>> buildable source distribution is a requirement for an ASF release, but >>> the build phase does not have to be a single command, as long as you >>> can build the same artifacts somehow , it's fine. >> >> Yes - and it works great if we stick with the existing multi-module >> release. But if we switch to release by bundle you will get the source for >> each bundle fine, if you want the source for the _whole module_ in a distro >> it's very hard. If the distro can just be a collection of released bundles >> (jars) that we know work together - that is easily done. Does that make >> sense? > > If your last sentence means that you would be happy to build each module > separately- then we don't need a module source zip. That would be much > easier. I think anyone who wants to build and modify the whole module could > quite easily grab the source from SVN, of if they were trying to build an > old release, they'd just have to build the bundles separately - or write > their own top level pom. I suppose building each one separately might be a > bit of a pita for application :-/ > > Z > > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ ------------------------ Open Source SOA http://fusesource.com
