Hi,

We have a very large set of WAR projects (web services, web applications,
static websites, etc) as part of a product offering.

Various versions and combinations of these are delivered to clients, but
there is no immediate understand of who gets what WARs, what versions, etc.

So I am using maven to manage this: I have a POM for each "delivery", which
just has the dependencies listed, and an assembly descriptor that ZIPs them
all conveniently, for deployment/DL to various environments.

Each developer has specified a finalName for their WAR, but there is no
convention, some require just the version info lopped off, some need a
totally different name from their artifact, etc.. there is no reliable way
to "calculate" the desired finalName, for various business reasons.

So in my ZIPs for each set of packaged goods, I would like the WARs to have
their finalNames, as opposed to their fully qualified maven names.

Shan


On Tue, Jul 20, 2010 at 4:54 PM, Kalle Korhonen
<kalle.o.korho...@gmail.com>wrote:

> Always a good idea to state *why* you might want to do this so people
> can provide alternatives. AFAIK the answer is no to your question, but
> if, for example, you just want to use the artifact name and strip out
> the version info from the filename, you can use outputFileNameMapping
> (see http://maven.apache.org/plugins/maven-assembly-plugin/component.html
> ).
>
> Kalle
>
>
> On Tue, Jul 20, 2010 at 1:26 PM, Shan Syed <shan...@gmail.com> wrote:
> > I know there is already a lot of discussion around the topic of artifacts
> > not using "finalName" when they are installed into a repository (remote
> or
> > local), but is there a way to enforce that the dependencies, when
> packaged
> > into the using project, are packaged with their finalNames?
> >
> > example:
> > Project A (a POM that ZIPs its WAR dependencies) uses B, C, D, etc.. as
> > dependencies (all WARs)
> >
> > B's finalName is "Bee", C's is "Cee", etc...
> > by default, when A packages, it creates a ZIP of all its dependencies
> (using
> > an assembly descriptor), with their fully qualified repository names, as
> > expected
> >
> > is there an easy way to ask maven to use the finalNames for the
> dependencies
> > instead?
> >
> > S
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Reply via email to