Mailing-List: contact dev-help@apex.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@apex.incubator.apache.org
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
Subject: Re: [VOTE] Apache Apex Core Release 3.3.0-incubating (RC1)
From: Justin Mclean <justin@classsoftware.com>
In-Reply-To: <56AC21D1.1070408@datatorrent.com>
Date: Mon, 1 Feb 2016 13:00:13 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <FB1D3B9E-E05E-4440-B18E-6BC7F60711A6@classsoftware.com>
References: 
 <CAKJfLDObCRopOiN8kyg9FBcHAG=r6VqGz0R2Pzrm+RUtAEDBbg@mail.gmail.com>
 <56AC0108.3040303@gmail.com>
 <CAA7LveGZhMSqsDOxn5bpAA_mtsVV3KgSBu9e5LTdteqsQ3YcDQ@mail.gmail.com>
 <56AC102E.5050809@gmail.com>
 <CAA7LveEwOHEEPzhH7gek=WPaGXDgu9tHjNpvP-dqTzbWG3wQFA@mail.gmail.com>
 <56AC21D1.1070408@datatorrent.com>
To: dev@apex.incubator.apache.org

Hi,

This is a bit of an edge case (as there's no compiled code inside the =
jar) but would be best to not include it in a source release. It should =
be simple to create the jar when building the source or it could be =
included in a binary convenience release.

> Can we keep the file in github and remove it from the source =
distribution?

Please don't store the jar in Apache's version control, that=E2=80=99s =
not open source.

> We may create jar out of the .xml file, but this will require running =
the build prior to creating an IDE project and importing codestyle =
definition.

Another option is that the jar could be hosted elsewhere and you could =
include a script to download it. This sounds like an optional dependancy =
(i.e. in that=E2=80=99s it not required to run Apex) so it=E2=80=99s not =
required to be in the source release.

> Do we need to have license embedded into the .xml file that is =
currently inside the jar?

Jars usually have LICENSE and NOTICE files in the META_INF directory.

Thanks,
Justin=