2 %% Licensed to the Apache Software Foundation (ASF) under one
3 %% or more contributor license agreements. See the NOTICE file
4 %% distributed with this work for additional information
5 %% regarding copyright ownership. The ASF licenses this file
6 %% to you under the Apache License, Version 2.0 (the
7 %% "License"); you may not use this file except in compliance
8 %% with the License. You may obtain a copy of the License at
10 %% http://www.apache.org/licenses/LICENSE-2.0
12 %% Unless required by applicable law or agreed to in writing,
13 %% software distributed under the License is distributed on an
14 %% "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
15 %% KIND, either express or implied. See the License for the
16 %% specific language governing permissions and limitations
19 %%% -*- mode:erlang -*-
20 {application, thrift, [
21 % A quick description of the application.
22 {description, "Thrift bindings"},
24 % The version of the applicaton
27 % All modules used by the application.
29 thrift_base64_transport,
30 thrift_binary_protocol,
31 thrift_buffered_transport,
34 thrift_disk_log_transport,
35 thrift_file_transport,
36 thrift_framed_transport,
37 thrift_http_transport,
40 thrift_membuffer_transport,
44 thrift_reconnecting_client,
48 thrift_socket_transport,
49 thrift_transport_state_test,
53 % All of the registered names the application uses. This can be ignored.
56 % Applications that are to be started prior to this one. This can be ignored
57 % leave it alone unless you understand it well and let the .rel files in
58 % your release handle this.
59 {applications, [kernel, stdlib]},
61 % OTP application loader will load, but not start, included apps. Again
62 % this can be ignored as well. To load but not start an application it
63 % is easier to include it in the .rel file followed by the atom 'none'
64 {included_applications, []},
66 % configuration parameters similar to those in the config file specified
67 % on the command line. can be fetched with gas:get_env
69 % If an error/crash occurs during processing of a function,
70 % should the TApplicationException serialized back to the client
71 % include the erlang backtrace?
72 {exceptions_include_traces, true}