RE: [higgins-dev] WAR file builds

["Paul Trevithick" <paul@xxxxxxxxxxxxxxxxx>]

Jim,

Maybe what you are saying is we should make a distinction between what the Components page (and its associated nightly build scripts) addresses (e.g. plugins and JARs) and what the Deployments page addresses:

• Components page build scripts, ide/cli, etc. should only target plugins and JARs (not WARs.)
• Deployments page build scripts should create one very limited, specific WAR (or other deployable or executable packages of one or more Compontents/projects). [For deployments that are web services the intent is to host (using Eclipse servers) a running instance of the service at an URL in the “URL” column of the deployment description table.]

-Paul

 

 

 

---

From: higgins-dev-bounces@xxxxxxxxxxx [mailto:higgins-dev-bounces@xxxxxxxxxxx] On Behalf Of Jim Sermersheim
Sent: Thursday, February 01, 2007 12:01 PM
To: 'Higgins (Trust Framework) Project developer discussions'
Subject: [higgins-dev] WAR file builds

 

Until yesterday, I was under the assumption that we would want the ability to produce a nightly war file build for the STS' TokenService.war (as well as a target for developers to do the same), but now I'm not sure.

 

A war file is really a deployment package.  Deployments differ based on need.  What I'm getting at is this: 

 

Typically, a war file will include it's dependencies in WEB-INF/lib.  For our recent demos, this means we've been including the usernametoken jar, idas jar, the ldap CP jar and its dependencies.  This is for a specific deployment.

 

We could choose to cause the war target to include all Higgins STS extensions, IdAS, and all Higgins CP's and their dependencies -- and maybe that's what we should do, but this may grow into a pretty large war at some point.

 

In any case, do we need to explore ways of building custom war files (which only include what a deployment needs)?

 

Jim