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
