Mailing-List: contact dev-help@edgent.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@edgent.apache.org
From: Dale LaBossiere <dml.apache@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 10.1 \(3251\))
Subject: mvn, Edgent samples, and the broader app development and packaging
 topic
Message-Id: <73CA0ECA-4C20-4D24-817D-20AF245A96EA@gmail.com>
Date: Wed, 21 Jun 2017 09:21:51 -0400
To: dev@edgent.apache.org
archived-at: Wed, 21 Jun 2017 13:22:12 -0000

Today (pre-mvn), Edgent has a number of sample programs under /samples.  =
They are pre-built and included in the binary release bundle as a =
collection of jars edgent.samples.{apps,=E2=80=A6}.jar and are run via =
scripts under /scripts.

Your thoughts on samples in the new world? As things are now, the =
scripts don=E2=80=99t work. They presume a (binary release) directory =
tree where all of the edgent jars reside in a particular layout.  They =
also use the non-version-labeled-name form of the Edgent jars.

At a high level there's =E2=80=9Chow do I build and package/assemble my =
app for execution on a device, and run my app=E2=80=9D.  Edgent, mostly, =
isn=E2=80=99t in the business of how to package the bits or get them to =
/ install them on the device.

Today=E2=80=99s binary release bundle only addresses the =E2=80=9Crun=E2=80=
=9D part of that.  The binary bundle includes the sample sources but =
doesn=E2=80=99t include tooling/scripts to build them. How lame is that? =
 :-)

In my mind it=E2=80=99s NOT a hard requirement that we (a) provide =
pre-built samples, nor (b) provide an Edgent binary release bundle =
(containing all the Edgent jars and deps).  I think it=E2=80=99s just =
the opposite :-)

I=E2=80=99ll stop there just to kickoff this thread.

=E2=80=94 Dale