I'll create RC4 tomorrow. Shinichiro Abe
On 2012/04/03, at 23:38, Karl Wright wrote: > Update: I'm just about ready to ask for a new RC that contains the following: > > - No checked-in binaries at all > - A new "XXX-lib" target just containing license files and binaries > - Patched jars built on the fly from patch files included in the > source distribution > > In order to make all this work, the ant build has been extended with > the following targets, which replace download-dependencies: > > make-core-deps (downloads and/or builds dependent jars and puts them in lib) > make-deps (downloads proprietary jars) > > Thus, to build from source, you need to either: > > (1) Unpack source tar, unpack lib tar, and run "ant build", or > optionally "ant make-deps build" > (2) Unpack source tar, run "ant make-core-deps", and then either "ant > build" or "ant make-deps build" > > If the make-core-deps target is objectionable, I can of course remove > it from ant help so it is hidden. It's essential, though, for release > engineering purposes. > > Karl > > On Mon, Apr 2, 2012 at 5:25 PM, Karl Wright <daddy...@gmail.com> wrote: >> If this is the next thing the community wants to try, I won't stand in >> the way. I just got the impression that there's more wrong with our >> build than just including dependent binaries - we also have problems >> with the dependent binaries themselves in some cases. >> >> Nevertheless, should I call a vote on (say) reverting to RC1 and >> applying the stated shell commands to the resulting artifacts? The >> commands should also include .wsp files as well as jars, but that is a >> minor issue. >> >> Karl >> >> >> On Mon, Apr 2, 2012 at 3:42 PM, Jukka Zitting <jukka.zitt...@gmail.com> >> wrote: >>> Hi, >>> >>> On Mon, Apr 2, 2012 at 8:15 PM, Karl Wright <daddy...@gmail.com> wrote: >>>> Possible solutions include: >>> >>> There's also the alternative that I brought up earlier: >>> >>> (5) Extract all dependencies from the existing pre-CONNECTORS-437 >>> source tree to a separate -lib package like this: >>> >>> $ tar zxf apache-manifoldcf-0.5-incubating-src.tar.gz >>> $ find apache-manifoldcf-0.5-incubating -type f -name '*.jar' > lib.txt >>> $ echo apache-manifoldcf-0.5-incubating/LICENSE.txt >> lib.txt >>> $ echo apache-manifoldcf-0.5-incubating/NOTICE.txt >> lib.txt >>> $ tar zcf apache-manifoldcf-0.5-incubating-lib.tar.gz -T lib.txt >>> >>> We can then publish that -lib package along with the official source >>> release and include build instructions like the following: >>> >>> $ tar zxf apache-manifoldcf-0.5-incubating-src.tar.gz >>> $ tar zxf apache-manifoldcf-0.5-incubating-lib.tar.gz >>> $ cd apache-manifoldcf-0.5-incubating >>> $ ant build >>> >>> That gives us something that's immediately releasable even with the >>> newly reinterpreted Apache rules. And it gives us more time and >>> breathing room for following up on the various improvement ideas that >>> in terms of simplifying the build and the way dependencies are handled >>> would make sense even regardless of policy requirements. >>> >>> BR, >>> >>> Jukka Zitting
