You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ant.apache.org by Eddie Bernard <eb...@digitalthink.com> on 2002/01/10 01:54:22 UTC
Adding/extending a manifest using
OK, I've haven't completely given up on using <ejbjar> for my WebLogic 6.1
project.
The reason I want to use it is that I have approximately 75 EJBs that I want
to build and the target I've created that uses <ejbjar> neatly creates each
EJB with only one target. Using some of the other suggested methods
(which, again, I appreciate the responses) would require me to have a target
for virutally every bean and even worst add more targets if more beans are
added to the project.
Now with all tht said, I'm in the process of creating an Enterprise Archive,
but I'm having a deployment problem -- again unrelated to Ant itself.
However, after reading some BEA white papers and the J2EE specifications for
Application Deployment, it allows the addition of the name:value pair:
Class-Path: list-of-jars-separated-by-spaces
Example:
Class-Path: lib/my_support_classes.jar
Now the Ant-related problem... It seems that <ejbjar> extends the <jar> task
meaning that it inherits the "manifest" attribute. If I use <jar> with my
manifest addition it works just fine. However, with <ejbjar> it generates a
"near empty" file (actually, it has a set of cr/lf).
Has anybody else come across this problem or have any ideas what I can do?
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Adding/extending a manifest using
Posted by Todd Chambery <tc...@hotmail.com>.
Howdy,
The GenericDeploymentTool in CVS
(http://cvs.apache.org/viewcvs/jakarta-ant/src/main/org/apache/tools/ant/tas
kdefs/optional/ejb/GenericDeploymentTool.java) has a workaround in which
<ejbjar> will pick up your manifest if it is named with
descriptor_root_dir/base_name-manifest.mf
.
I don't quite understand why GDT doesn't just look to see if a "manifest.mf"
exists in the current descriptor directory, and if it does, add it to the
jar. If one isn't there, put in the empty Ant default. I'm going to make
an attempt at submitting a patch (I think it's a very simple fix).
hope that helps,
Todd
----- Original Message -----
From: "Eddie Bernard" <eb...@digitalthink.com>
To: <an...@jakarta.apache.org>
Sent: Wednesday, January 09, 2002 7:54 PM
Subject: Adding/extending a manifest using <ejbjar>
> OK, I've haven't completely given up on using <ejbjar> for my WebLogic 6.1
> project.
>
> The reason I want to use it is that I have approximately 75 EJBs that I
want
> to build and the target I've created that uses <ejbjar> neatly creates
each
> EJB with only one target. Using some of the other suggested methods
> (which, again, I appreciate the responses) would require me to have a
target
> for virutally every bean and even worst add more targets if more beans are
> added to the project.
>
> Now with all tht said, I'm in the process of creating an Enterprise
Archive,
> but I'm having a deployment problem -- again unrelated to Ant itself.
> However, after reading some BEA white papers and the J2EE specifications
for
> Application Deployment, it allows the addition of the name:value pair:
>
> Class-Path: list-of-jars-separated-by-spaces
>
> Example:
>
> Class-Path: lib/my_support_classes.jar
>
> Now the Ant-related problem... It seems that <ejbjar> extends the <jar>
task
> meaning that it inherits the "manifest" attribute. If I use <jar> with my
> manifest addition it works just fine. However, with <ejbjar> it generates
a
> "near empty" file (actually, it has a set of cr/lf).
>
> Has anybody else come across this problem or have any ideas what I can do?
>
>
>
> --
> To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: Adding/extending a manifest using
Posted by Donnie Hale <do...@haleonline.net>.
I don't have 75 beans, but I have 6 and build them all with one target (not
<ejbjar> - actually 2, one for the vanilla ejb.jar and one to put that into
ejbc) and won't have to change that if/when we add more beans.
Don't know what to say about the manifest problem. Sorry...
Donnie
> -----Original Message-----
> From: Eddie Bernard [mailto:ebernard@digitalthink.com]
> Sent: Wednesday, January 09, 2002 7:54 PM
> To: 'ant-user@jakarta.apache.org'
> Subject: Adding/extending a manifest using <ejbjar>
>
>
> OK, I've haven't completely given up on using <ejbjar> for my WebLogic 6.1
> project.
>
> The reason I want to use it is that I have approximately 75 EJBs
> that I want
> to build and the target I've created that uses <ejbjar> neatly
> creates each
> EJB with only one target. Using some of the other suggested methods
> (which, again, I appreciate the responses) would require me to
> have a target
> for virutally every bean and even worst add more targets if more beans are
> added to the project.
>
> Now with all tht said, I'm in the process of creating an
> Enterprise Archive,
> but I'm having a deployment problem -- again unrelated to Ant itself.
> However, after reading some BEA white papers and the J2EE
> specifications for
> Application Deployment, it allows the addition of the name:value pair:
>
> Class-Path: list-of-jars-separated-by-spaces
>
> Example:
>
> Class-Path: lib/my_support_classes.jar
>
> Now the Ant-related problem... It seems that <ejbjar> extends the
> <jar> task
> meaning that it inherits the "manifest" attribute. If I use <jar> with my
> manifest addition it works just fine. However, with <ejbjar> it
> generates a
> "near empty" file (actually, it has a set of cr/lf).
>
> Has anybody else come across this problem or have any ideas what I can do?
>
>
>
> --
> To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: Adding/extending a manifest using
Posted by "J. Matthew Pryor" <ma...@versata.com>.
I just use ejbjar then use the jar task to update the manifest on its own
<ejbjar>
<whatever/>
</ejbjar>
<jar
jarfile="${dist.lib.dir}/${ant.project.name}-ejb-${param.ejb.spec.version}.j
ar" update="true" >
<manifest>
<attribute name="Class-Path" value="abc.jar def.jar
hij.jar"/>
</manifest>
</jar>
See the archives for a discussion of the manifest updating capability of the
jar task in Ant 1.4.1
jmp
> -----Original Message-----
> From: Eddie Bernard [mailto:ebernard@digitalthink.com]
> Sent: Thursday, January 10, 2002 11:54 AM
> To: 'ant-user@jakarta.apache.org'
> Subject: Adding/extending a manifest using <ejbjar>
>
>
> OK, I've haven't completely given up on using <ejbjar> for my WebLogic 6.1
> project.
>
> The reason I want to use it is that I have approximately 75 EJBs
> that I want
> to build and the target I've created that uses <ejbjar> neatly
> creates each
> EJB with only one target. Using some of the other suggested methods
> (which, again, I appreciate the responses) would require me to
> have a target
> for virutally every bean and even worst add more targets if more beans are
> added to the project.
>
> Now with all tht said, I'm in the process of creating an
> Enterprise Archive,
> but I'm having a deployment problem -- again unrelated to Ant itself.
> However, after reading some BEA white papers and the J2EE
> specifications for
> Application Deployment, it allows the addition of the name:value pair:
>
> Class-Path: list-of-jars-separated-by-spaces
>
> Example:
>
> Class-Path: lib/my_support_classes.jar
>
> Now the Ant-related problem... It seems that <ejbjar> extends the
> <jar> task
> meaning that it inherits the "manifest" attribute. If I use <jar> with my
> manifest addition it works just fine. However, with <ejbjar> it
> generates a
> "near empty" file (actually, it has a set of cr/lf).
>
> Has anybody else come across this problem or have any ideas what I can do?
>
>
>
> --
> To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>