On Fri, Apr 26, 2013 at 7:06 AM, Michael McCandless < [email protected]> wrote:
> On Fri, Apr 26, 2013 at 6:57 AM, Robert Muir <[email protected]> wrote: > > > > i dont understand logging at all... needing 6 or 7 jars to > "System.out.println" is the most ridiculous thing in the world to me. So > someone else will have to comment about "which one is right", the .tgz or > maven > > > > but it seems totally broken for the war to have a bunch of extra jars in > maven that it doesnt have in the tgz. If a user has a problem with logging > (and since all these jars changed, i feel this is a possibility), no one > will have a clue how to proceed. We could only ask... 'Which 4.3 are you > using? 4.3-MAVEN or 4.3-TGZ?' > > > > Personally i'm -1 for us releasing different artifacts in maven than in > the tgz because i strongly believe we should only have "one release" and > not release different shit to different places. I'd rather us just not > release any maven artifacts at all than do this (if you have no time to > respin, just remove the maven artifacts from the RC and you will get my +1). > > I agree ... I think we should fix this and build a new RC. > I would try to help fix it: but its not clear to me which 'package' is correct or what happened to logging at all in 4.3 The TGZ seems broken that it has no logging jars at all but solr code relies upon it, so there is no way in hell thats actually working. This means that .war file is totally unusable by itself... I think thats broken?
