> I want the 'free' zip/tar to be available for download from jboss.org, so that > I can reference an md5sum for it, to show that I haven't modified the code.
If we seperate the thirdparty, then this will be the case... though you MUST have the required thirdparty versions at the correct version for things to work. Let me think about how I might make this easy to do. > > I am open to ideas on how to seperate these, though I can tell you that > > things like 'go download x from x.com, y from y.com' and so on will not fly. > > I would expect that if this worked at all it would be, here is the > > jboss-xxx.zip with LGPL and here is jboss-thirdparty-xxx.zip with (long list > > of varing licenses which allow us to distribute it). > > > > A user would then unzip each at the same level and have a happy release to > > start using. > > cvs co jboss-all > cd jboss-all > # this gives jboss*, plus tools and thirdparty. > ant build free-dist > # This creates zips/tars of everything BUT tools/thirdparty. > ant build nonfree-dist > # This creates zips/tars of tools/thirdparty. > ant build dist > # This creates zips/tars of everything. You will still need to use 'build.sh', 'ant' won't work. Can you continue based on the current build, simply pretent that the non-free stuff isn't there and will be required. Todo this simply 'build/build.sh', then remove the non-free stuff (and document that for me) and go about your biz. Once I have time and can figure out a way to elegantly build seperate archives I will change this so you don't have to scrap out the non-free stuff. --jason _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
