Conor,
Thanks very much for your prompt reply. I figured it out - it was just
a silly mistake on my part. I didn't end my manifest file with a blank
line, so it didn't recognize the final attribute, which in my case was
the Class-Path. I added a newline after that, and it worked without iss
Andrew,
It's a while since I worked on the ejb tasks, so forgive me if I'm a
little hazy.
Andrew Perez-Lopez wrote:
> I got the manifest attribute to work, but not completely. It seems to
> ignore my Class-Path attribute. When I use the jar task with the same
> manifest attribute, it creates a
Conor,
Thanks very much for your help. I'm half-way there now...
I got the manifest attribute to work, but not completely. It seems to
ignore my Class-Path attribute. When I use the jar task with the same
manifest attribute, it creates a jar with the proper attributes, but the
ejbjar task
Andrew Perez-Lopez wrote:
> Hey all,
>
> I'm working with EJBs using JBoss 4.x and Ant 1.6.5. I'm trying to set
> the Class-Path of the manifests of a big bunch of EJBs to a set of
> libraries that I've included in my EAR file. I can get ejbjar to
> generate all my jars, which is very nice, but
Hey all,
I'm working with EJBs using JBoss 4.x and Ant 1.6.5. I'm trying to set
the Class-Path of the manifests of a big bunch of EJBs to a set of
libraries that I've included in my EAR file. I can get ejbjar to
generate all my jars, which is very nice, but since the ejbjar task
doesn't all
