Todd- Thanks again! I did manage to find the file in CVS and I've downloaded it. However, I'm still getting an empty manifest when I use it.
I inferred from looking at the code that the "manifest" attribute is not required as it will pick it up automagically from the location you've specified. Is this a correct assumption? IF I add the "manifest" attribute, I get an empty manifest. If I leave it out, I get the default manifest. Nonetheless, it looks like if this does work it will accomplish what I need. Any thoughts on how I can get this to work? Cheers! Eddie -----Original Message----- From: Todd Chambery [mailto:[EMAIL PROTECTED]] Sent: Friday, January 11, 2002 6:25 AM To: Ant Users List Subject: Re: Adding/extending a manifest using <ejbjar> Eddie, The most current version of the GDT in CVS looks in the descriptor root directory for the renamed manifest. So, descriptor_root/ basejarname-manifest.mf basjarname_bean/ META-INF/ ejb-jar.xml This depends kind of on what's specified in the 'naming' attribute of the <ejbjar> task, but you get the idea. Case is important (assuming you're not on a win box). I don't think this is very intuitive, so I submitted a patch (actually 2, but the first one sucked) that makes the GDT look in the current descriptor dir (in the above example, descriptor_root/basejarname_bean/META-INF/) for "manifest.mf". I don't know how the Ant people will respond, but I can mail it to you if you want. Todd ----- Original Message ----- From: "Eddie Bernard" <[EMAIL PROTECTED]> To: "'Ant Users List'" <[EMAIL PROTECTED]> Sent: Friday, January 11, 2002 3:05 AM Subject: RE: Adding/extending a manifest using <ejbjar> > Todd- > > So, if are you saying that the manifest file name must have the name of the > EJB as specified in the deployment descriptor? > > If so, then does the name of the manifest and directory structure look like: > > META-INF/ > ejb-jar.xml > MyBeanName-manifest.mf > > or does the manifest simply need to be "Manifest.mf". Better yet, is this > case-sensitive? > > > > Cheers! > Eddie > > -----Original Message----- > From: Todd Chambery [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, January 09, 2002 5:41 PM > To: Ant Users List > Subject: Re: Adding/extending a manifest using <ejbjar> > > > 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" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > 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: <mailto:[EMAIL PROTECTED]> > > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > > > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
