There is a way if he's embedding the .swf file inside a war. you can use the dependency:copy-dependencies to copy the swf file into the war and strip the version while doing that
-Stephen On 3 August 2010 21:52, Anders Hammar <[email protected]> wrote: > There was a very imilar question on this list just a few days ago.You would > get a lot of details by searching an archive. > > As to your question: No, you cannot change the Maven standard. Don't fight > Maven! > (Someone will likely suggest overriding the finalName definition, but that > would NOT affect the name in the repo, local or remote.) > > /Anders > > On Tue, Aug 3, 2010 at 19:29, Chetan V Minajagi < > [email protected]> wrote: > > > Hi, > > > > We use maven for build and I have a problem with the way the name of a > > entity(jar/war/swf) is generated. > > We use a jsp in which to embed the swf file and this swf file name should > > be xyz.swf .Invariably, the name that gets generated by default is > > xyz-1.0.0.swf etc based on the version in the pom file. > > Can this be overridden somehow so that we can force a name rather than > rely > > on the default naming that maven makes it available with. > > > > Regards, > > Chetan > > > > > > This communication is for informational purposes only. It is not > > intended as an offer or solicitation for the purchase or sale of > > any financial instrument or as an official confirmation of any > > transaction. All market prices, data and other information are not > > warranted as to completeness or accuracy and are subject to change > > without notice. Any comments or statements made herein do not > > necessarily reflect those of JPMorgan Chase & Co., its subsidiaries > > and affiliates. > > > > This transmission may contain information that is privileged, > > confidential, legally privileged, and/or exempt from disclosure > > under applicable law. If you are not the intended recipient, you > > are hereby notified that any disclosure, copying, distribution, or > > use of the information contained herein (including any reliance > > thereon) is STRICTLY PROHIBITED. Although this transmission and any > > attachments are believed to be free of any virus or other defect > > that might affect any computer system into which it is received and > > opened, it is the responsibility of the recipient to ensure that it > > is virus free and no responsibility is accepted by JPMorgan Chase & > > Co., its subsidiaries and affiliates, as applicable, for any loss > > or damage arising in any way from its use. If you received this > > transmission in error, please immediately contact the sender and > > destroy the material in its entirety, whether in electronic or hard > > copy format. Thank you. > > > > Please refer to http://www.jpmorgan.com/pages/disclosures for > > disclosures relating to European legal entities. >
