On 5/22/08, Chris Helck <[EMAIL PROTECTED]> wrote:
> Rich,
> It's very common for corperations to implement this sort of thing. It
> helps ensure that the products can be rebuilt from the source code, and
> that helps certain audit/security processes. In any case, this is what
> my company does
s they could do a multi-module build,
> > which builds each project in turn.
> >
> > Rich
> >
> > -Original Message-
> > From: Chris Helck [mailto:[EMAIL PROTECTED]
> > Sent: 22 May 2008 17:11
> > To: Maven Users List
> > Subject: RE: Certifica
May 2008 17:11
> To: Maven Users List
> Subject: RE: Certification build question
>
> Rich,
> It's very common for corperations to implement this sort of thing. It
> helps ensure that the products can be rebuilt from the source code, and
> that helps certain audit/security pro
From: Chris Helck [mailto:[EMAIL PROTECTED]
Sent: 22 May 2008 17:11
To: Maven Users List
Subject: RE: Certification build question
Rich,
It's very common for corperations to implement this sort of thing. It
helps ensure that the products can be rebuilt from the source code, and
that hel
t for internal and informal releases of test tools
and report generators.
-Chris
-Original Message-
From: Richard Chamberlain [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 22, 2008 12:00 PM
To: Maven Users List
Subject: RE: Certification build question
Why do the team need to build
Why do the team need to build your application? Can you not give them a
built version for them to test?
If you can do this, have an application project that depends on all the
components that you use. Configure the assembly plugin to zip all the
dependencies into a kit. You can then tell them to pi
