Re: About classpathPrefix flexibility [was: Re: Generating manifest file]

[Paul Merlin <pa...@nosphere.org>]

Hi Wendy,

Le DATE, vous avez peut-être écrit : Wendy Smoak
> On 10/8/07, Paul MERLIN <pa...@nosphere.org> wrote:
>>
>> I'm using the pom snippet shown above but I would like to have some
>> dependencies prefixed and some others not.
>
> Why?  I'm curious because someone at work also wants to do this, and I
> don't see what would be gained by it.
>
> Does it have anything to do with WebSphere or WSAD?  (That's what this
> team is using, and I'm trying to sort out what things they really
> *need* vs. what they're trying to do just because that's the way WSAD
> has always done it.)

In fact it does have to do with JEE packaging. I do not use WebSphere or
WSAD but Glassfish.

When you package a JEE application (ear packaging) the ClassPath set in
the MANIFEST.MF file is important, so the packaging layout is.

EJB or WAR modules have to be at the EAR's root. The "lib/" subdirectory
contains librairies.

You can have a module (EJB-JAR, WAR, RAR) that needs some JARs from the
lib/ directory _and_ some others from the EAR's root.

The EAR plugin lets you arrange files easily but managing MANIFEST.MF
files when there's several modules in you application is a tedious task.

Here comes my question ;)

>> Is this doable with maven or will I have to write the MANIFEST.MF file
>> myself ?
>
> At the moment I think you'll have to maintain the MANIFEST.MF file
> manually, but I'd love to hear otherwise...

I built them manually today because we need to keep coding/testing. As our
application packaging will not evolve the sooner, I'll check back on this
issue later. It's in my inbox :)

Paul

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org