Rod,
The way that our Ant build script has always been configured is below. I
believe that we're doing what you recommend, yet I did not resolve my
problem with JBoss 3.x until I referred to library JARs in manifest.txt
relative to the EJB JARs instead of the EAR root. I'm sharing this
information because I do not completely understand your post. Maybe you can
provide your own BEFORE and AFTER scenarios as I did in my earlier post. If
you can still find time to explore these issues, I would greatly appreciate
it.
<!-- ================================================================= -->
<!-- Package the application in a JAR file for distribution/deployment -->
<!-- ================================================================= -->
<target name="dist.jar">
<jar jarfile="${dist}/ejb/${main.jar.name}.jar"
manifest="${src.res}/META-INF/manifest.txt">
<metainf dir="${src.res}/META-INF">
<include name="ejb-jar.xml" />
</metainf>
<!-- all main classes, i.e., no test classes -->
<fileset dir="${build.main}" />
</jar>
</target>
Contents of manifest.txt (there is a new line at the end of the Class-Path
line):
Class-Path: ../libs/apogent-common.jar ../libs/eif-ejb.jar
> -----Original Message-----
> From: Rod Macpherson [mailto:[EMAIL PROTECTED]]
> Sent: Saturday, February 01, 2003 7:56 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [JBoss-user] EAR works in 2.4.10 but not in 3.0.6
>
>
> This whole issue only arises when you try to get a slimmed
> down EAR with no duplicates. There are so many ways to work
> around this that it comes as no surprise that you one ends up
> shrugging if off as no biggie but when several folks reported
> the problem I wanted to get to the bottom of it. Turned out
> it was my ant script. Yes, put everything in the right place
> with the correct syntax and all of that but assumed,
> incorrectly, that the class loader would pick up MANIFEST.MF.
> Jarred everything up with no complaint from ANT (it was
> supposed to complain about this) but there was a problem.
>
> HINT: <jar.. manifest="some-manifest.mf"> ... <metainf
> dir="whatever"> <include file="*"> </metainf> <jar>
>
> Make sure you DO NOT have MANIFEST.MF in META-INF or where
> it ultimately must be to actually work. Create manifest
> files (call 'em anything you
> like) and include that particular file in the jar manifest
> attribute. Feel free to flame away for having missed this.
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
