I work in the corporate world every day, friend. As for incorporating a patch like this, if it is a fairly trivial patch (many are just a couple fixed class files), I would personally just unpack the affected jars, copy the patched files in, and repack them with adjusted version numbers. I'm not saying this is ideal, but its not a 6mo delay either...
Wayne On 5/3/07, Jose Alberto Fernandez <[EMAIL PROTECTED]> wrote:
When I read things like this, I think some of the Maven people have never been working in the real corporate world. You cannot expect a project to stop for 6 month waiting for the next full release of Weblogic or any other product, just because there is no way on Maven to take a product patch into account. Try telling your manager that his flagship project must be delay half a year because your building tool does not like the way Weblogic distributes an emergency patch. I mean how fast would you think it would take to be asked to clean your desk and leave the building? J.A. Wayne Fay wrote: > > As a Weblogic customer, I'd complain until they resolve this issue. > > I agree entirely with Graham -- the fact that your dependency JARs > must be ordered in a particular way to get a successful build should > not be acceptable to you. > > Wayne > > -- View this message in context: http://www.nabble.com/-m2--Dependency-Ordering-Headache-tf3668646s177.html#a10305209 Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
