On Friday, October 17, 2003, at 05:24 PM, [EMAIL PROTECTED] wrote:
David Sean Taylor <[EMAIL PROTECTED]> wrote on 18/10/2003 10:00:20 AM:What's not to get. Its either a bug or a mistake on our part
On Friday, October 17, 2003, at 04:35 PM, [EMAIL PROTECTED] wrote:
- <war.bundle>true</war.bundle> + <war.bundle.jar>true</war.bundle.jar>
You do know that <war.bundle.jar> is deprecated in favour of <war.bundle>, right?
Yes, I patched that a few days ago. Unfortunately Maven is not quite ready for deprecation of <war.bundle.jar>, and still relies on <war.bundle> for bundling jars into the war target, even though it is supposedly deprecated. Thus Scott had to change it back
I don't get it?
How is Maven not quite ready for deprecation of war.bundle.jar? As a committer on Maven, if there's somewhere that it's still floating about and war.bundle isn't provided as well, I'd like to know!
Well try it out. Thats exactly what Im going do right now.
I was quite surprised too when Scott told me that I broke the build with a seemingly innocuous deprecation fix
-- David Sean Taylor Bluesunrise Software [EMAIL PROTECTED] +01 707 773-4646 +01 707 529 9194
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
