---------- Forwarded message ----------<br><span class="gmail_quote">From: <b class="gmail_sendername">Jose Gonzalez Gomez</b> <<a href="mailto:jgonzalez.openinput@...">jgonzalez.openinput@...</a>><br>Date: 27-ene-2006 12:54
<br>Subject: Re: [gentoo-java] webapp-config & Java<br>To: Andrew Cowie <<a href="mailto:andrew@...">andrew@...</a>><br><br></span>2006/1/27, Andrew Cowie <<a href="mailto:andrew@..." target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
andrew@...</a>>:<span class="q"><div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Thu, 2006-26-01 at 16:56 -0500, Joshua Nichols wrote:<br><br>> Following the spirit of not using bundled jars for building, this leads<br>> me to think that it would be better to explode the wars, and replace the
<br>> jars contained within with symlinks to the jars on the system.<br><br>Note that some app-servers can't/won't deal with an exploded war/ear.<br></blockquote></div><br></span>I think this issue has more to do with solving the issues with java builds based in ant or maven than finding bundled jars... currently almost every Java package out there is built using either ant or maven (please, some Java Gentoo developer correct me if I'm wrong). In the case of maven, jar dependencies are not bundled with source files, they are specified as dependencies in the project descriptors. In the case of web applications, those dependencies are downloaded from binary repositories, and bundled in the WEB-INF/lib directory of the war file at build time. The obvious solution (don't know if easy to implement, I remember some discussion here regarding this) is to intercept in some way the maven dependency resolution mechanism and instead of downloading binary jars, take jars from the java packages already installed by Gentoo.
<br><br>In case you still want to go the explode/replace way, as Andrew tells, you won't be able to use symlinks, as some app-servers can't deal with exploded archives. You should replace those jars with jars present on the system, and then repackage and deploy the archive. I see this more unnatural than the previous solution, although maybe easier to do.
<br><br>Best regads<br><span class="sg">Jose<br><br>Arghh... hadn't this list activated the reply-to-list option some time ago??<br>