Mailing-List: contact dev-help@oodt.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@oodt.apache.org
Received-SPF: pass (nike.apache.org: local policy)
From: "Resneck, Gabriel M (388J)" <Gabriel.M.Resneck@jpl.nasa.gov>
To: "dev@oodt.apache.org" <dev@oodt.apache.org>
Subject: Including Workflow Manager in Resource Manager Package using Maven
 Assembly Plug-In
Thread-Topic: Including Workflow Manager in Resource Manager Package using
 Maven Assembly Plug-In
Thread-Index: AQHOEfyw/CzkK6nwSU+deeaoZcRexw==
Date: Sat, 23 Feb 2013 19:33:44 +0000
Message-ID: <CD4E5996.117E%gabriel.m.resneck@jpl.nasa.gov>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/14.3.0.121105
Content-Type: multipart/alternative;
	boundary="_000_CD4E5996117Egabrielmresneckjplnasagov_"
MIME-Version: 1.0

--_000_CD4E5996117Egabrielmresneckjplnasagov_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi, all!
I know that the OODT community is home to some Maven gurus, and I'm hoping =
to tap into that expertise.
I have recently changed the SMAP code in such a way that our project-specif=
ic extensions to the Workflow Manager depend upon our extensions to the Res=
ource Manager.  This is actually similar to the setup in OODT 0.5, however,=
 these changes have upset how the Maven assembly plug-in builds our project=
.  Before, the dependency went the other way, which meant that JARs importa=
nt to the Workflow Manager would make their way into the lib directory of R=
esource Manager which needed those JARs.
Our assembly specification is basically the same as the one used in the cor=
e.  Does anyone happen to know how I could change it to include the Workflo=
w Manager JAR that we create in the lib directory of the Resource Manager.
Thanks heaps!

Gabe =3D)


--_000_CD4E5996117Egabrielmresneckjplnasagov_--