Hi Xiangdong, good catch with with libs in the source ... as much as I hate to say it ... I have to change my vote :-( Even if it sort of puzzles me how this could happen. Usually the release plugin checks out clean into target/checkout and runs the "mvn deploy -P apache-release" there ... as the source bundle is built first, the libs should have been empty. Unless someone checked out the tagged version an ran the build again.
This is one of the side-effects I mentioned were a result of the redirecting of standard plugins outputs. If you want, I could make things more standard compliant. Chris Am 03.08.19, 17:30 schrieb "Xiangdong Huang" <[email protected]>: Hi, I checked the bin.zip and source-code.zip and then find that: - NOTICE file shows "Apache Hive Copyright 2008-2019 The Apache Software Foundation" while NOTICE-binary file shows "Apache Hive Copyright 2008-2018 The Apache Software Foundation" (I also checked github.com/apache/hive, and found it should be 2018..) - tools/start-WalChecker.sh or .bat: the script can only check $IOTDB_HOME$/data/wal folder... I submit a PR #330 to fix that. - the other scripts in bin.zip work well.. But I noticed that the source-code.zip (~26MB) is larger than bin.zip (~10MB)... After checking the subfolders, I find that server/iotdb/lib and client/cli/lib have jars... Do we need to remove them out of the source-code.zip file? Best, ----------------------------------- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Julian Feinauer <[email protected]> 于2019年8月3日周六 下午9:29写道： > Hi Chris, > > When thinking about it, I definitely agree. > I just copied over the mail template from an other poling where it was > created from an apache member which may not be named here :P > > But +1. > > Julian > > Von meinem Mobiltelefon gesendet > > > -------- Ursprüngliche Nachricht -------- > Betreff: [DISCUSS] Apache IoTDB (Incubating) 0.8.0 RC2 > Von: Christofer Dutz > An: [email protected] > Cc: > > Hi … > > I do have a proposal for future release-candidates: > I think the link usually posted as [2] should be [1] in the future. > The reason is that this IS THE RELEASE … the current Maven artifacts in > [1] are convenience binaries distributed by the PPMC. > Also might it make people think, this is what they have to verify and not > what’s currently in [2]. > > Will now start verifying the RC2 … > > Chris >
