Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Received-SPF: error (nike.apache.org: local policy)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.0 \(1990.1\))
Subject: Re: [Fortress] package generation
From: Shawn McKinney <smckinney@apache.org>
In-Reply-To: <551DA44F.7030708@gmail.com>
Date: Thu, 2 Apr 2015 18:42:03 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <D05640D2-5829-4860-A36D-CF993B60A76F@apache.org>
References: <551D9E36.2020708@symas.com> <551DA44F.7030708@gmail.com>
To: Apache Directory Developers List <dev@directory.apache.org>


> On Apr 2, 2015, at 3:19 PM, Emmanuel L=C3=A9charny =
<elecharny@gmail.com> wrote:
>=20
> I have some doubt about the fortress-core-1.0-RC40-SNAPSHOT-bin*
> tarballs, which contains a lib/ and a dist/ directories. First, I =
don't
> see why we have all the used libs beside the jar (either the user will
> not use those jars, and they are useless, or they want a standalone =
jar,
> which contains all the jars in one single file. In any case, we have =
to
> add the LICENSE.* files (2 are missing).

The /lib (which is where ivy put the dependencies) and /dist (build =
artifacts) folders are remnants of the, now deprecated ant build.  Now =
that we are using maven, the built artifacts go in /target and the =
dependencies under .m2 repo.  I don=E2=80=99t think we should be =
packaging up anything under the lib and dist.

Shawn
smckinney@apache.org