Hi,
I think the structure of the binaries can be:
(Structure 1):
.
├── LICENSE
├── NOTICE
├── bin
│ ├── export-csv.bat
│ ├── export-csv.sh
│ ├── import-csv.bat
│ ├── import-csv.sh
│ ├── run-client.bat
│ ├── start-WalChecker.bat
│ ├── start-WalChecker.sh
│ ├── start-client.bat
│ ├── start-client.sh
│ ├── start-grafana-connector.bat
│ ├── start-grafana-connector.sh
│ ├── start-server.bat
│ ├── start-server.sh
│ ├── start-sync-client.bat
│ ├── start-sync-client.sh
│ ├── stop-server.bat
│ ├── stop-server.sh
│ ├── stop-sync-client.bat
│ └── stop-sync-client.sh
├── changes.txt
├── conf
│ ├── error_info_cn.properties
│ ├── error_info_en.properties
│ ├── iotdb-engine.properties
│ ├── iotdb-env.bat
│ ├── iotdb-env.sh
│ ├── iotdb-sync-client.properties
│ ├── logback.xml
│ └── tsfile-format.properties
├── lib
│ └── *.jar
└── licenses
└── LICENCES
(Structure 2):
.
├── LICENSE
├── NOTICE
├── changes.txt
├── client
│ ├── bin
│ │ ├── export-csv.bat
│ │ ├── export-csv.sh
│ │ ├── import-csv.bat
│ │ ├── import-csv.sh
│ │ ├── run-client.bat
│ │ ├── start-client.bat
│ │ └── start-client.sh
│ └── lib
│ └── *.jar
├── grafana-connector
│ ├── bin
│ │ ├── start-grafana-connector.bat
│ │ └── start-grafana-connector.sh
│ └── iotdb-grafana-0.8.0-SNAPSHOT.war
├── licenses
│ └── LICENCES
└── server
├── bin
│ ├── start-WalChecker.bat
│ ├── start-WalChecker.sh
│ ├── start-server.bat
│ ├── start-server.sh
│ ├── start-sync-client.bat
│ ├── start-sync-client.sh
│ ├── stop-server.bat
│ ├── stop-server.sh
│ ├── stop-sync-client.bat
│ └── stop-sync-client.sh
├── conf
│ ├── error_info_cn.properties
│ ├── error_info_en.properties
│ ├── iotdb-engine.properties
│ ├── iotdb-env.bat
│ ├── iotdb-env.sh
│ ├── iotdb-sync-client.properties
│ ├── logback.xml
│ └── tsfile-format.properties
└── lib
└── *.jar
In structure 1, CLI and server scripts are in the same folder, so does the
libs. In structure 2, CLI and server module are seperated.
The first one has smaller size because the two modules have some duplicated
libs.
Best,
-----------------------------------
Xiangdong Huang
School of Software, Tsinghua University
黄向东
清华大学 软件学院
Christofer Dutz <christofer.d...@c-ware.de> 于2019年7月16日周二 下午7:10写道：
> Bash scripts are not portable.
> I would strongly advise not to use them and with the assembly plugin, the
> binary stuff gets packaged alongside the source bundle during the release
> build.
>
> Chris
>
> Holen Sie sichOutlook für Android<https://aka.ms/ghei36>
>
> ________________________________
> From: Julian Feinauer <j.feina...@pragmaticminds.de>
> Sent: Tuesday, July 16, 2019 12:39:51 PM
> To: dev@iotdb.apache.org
> Subject: AW: Binary Release of IoTDB
>
> Hey Chris,
>
> I also thought about that and... Contacting you :P
> But I thought about a bash script :)
>
> Julian
>
> Von meinem Mobiltelefon gesendet
>
>
> -------- Ursprüngliche Nachricht --------
> Betreff: Re: Binary Release of IoTDB
> Von: Christofer Dutz
> An: dev@iotdb.apache.org
> Cc:
>
> We could whip up a maven assembly für building that binary distribution. I
> could help with that, if you exactly define how it should look.
>
> Chris
>
> Holen Sie sichOutlook für Android<https://aka.ms/ghei36>
>
> ________________________________
> From: Kevin A. McGrail <kmcgr...@apache.org>
> Sent: Tuesday, July 16, 2019 12:30:21 PM
> To: dev@iotdb.apache.org
> Subject: Re: Binary Release of IoTDB
>
> +1 to a binary release along side a source release as a convenience.
>
> On Tue, Jul 16, 2019, 05:40 Justin Mclean <jus...@classsoftware.com>
> wrote:
>
> > Hi,
> >
> > Apache releases source code not binaries, but you make can also release a
> > convenance binary along side a source release as noted in the link Julian
> > provided. Note that the LICENSE and NOTICE requirements may be diffract
> as
> > a binary contents may differ.
> >
> > Thanks,
> > Justin
>
