The fact that install / deploy process maintains the filename with a
version in it is simple.
The repository is to be thought of as a database.
The local repository is to be thought of as a remote repository cache.
The repository database *needs* versioning.
The plugins that bundle the artifacts within other files (such a
assembly, war, ear, etc...) honor the <finalName> setting when working
on the artifacts outside of the Repository database.
- Joakim
Stephane Nicoll wrote:
> Hi,
>
> On 3/28/07, Franz Allan Valencia See <[EMAIL PROTECTED]> wrote:
>> Good day to you, Dheeraj,
>>
>> Try
>>
>> <project>
>> ...
>> <build>
>> <finalName>${artifactId}</finalName>
>> ...
>> </build>
>> ...
>> </project>
>>
>> By default, the value of finalName is "${artifactId}-${version}" (
>> without
>> the quotes ) which every pom inherits from the super pom ( see [1] ).
>
> This is not honored by the deploy/install plugins so I am not sure
> it's fixing anything.
>
>>
>> ..btw, you might want to try asking in the maven users list next time
>> to get
>> a faster response :)
>
> +1
>
> Stéphane
>
>
>>
>> Cheers,
>> Franz
>>
>> [1]
>> http://maven.apache.org/guides/introduction/introduction-to-the-pom.html
>>
>> On 3/27/07, Pant, Dheeraj <[EMAIL PROTECTED]> wrote:
>> >
>> > Hi,
>> >
>> > Using Maven generates all the artifacts (jars/wars/ears)
>> > with a unique filename <artifactid>-<version>.<type>. How do we remove
>> > the version number from the filenames? I need a generic way to do
>> this,
>> > because we have many sub-modules and would like to have a common
>> > solution that can be reused for every module.
>> >
>> >
>> >
>> > I tried the following things:
>> >
>> > 1. For ear, Maven allows to rename the modules.
>> >
>> > 2. Using an ant task, rename each jar/war/ear after it gets packaged.
>> >
>> >
>> >
>> > However, still classpath within the MANIFEST files (generated using
>> > Maven) refers to unique filenames including their version numbers. We
>> > don't want to hardcode our manifest files. I tried specifying project
>> > specific modules as system dependency - did not work.
>> >
>> >
>> >
>> > Is there a way out?
>> >
>> >
>> >
>> > Thanks,
>> >
>> > Dheeraj.
>> >
>> >
>> >
>> >
>> >
>> > -----------------------------------------
>> > This message and any attachments are intended only for the use of
>> > the addressee and may contain information that is privileged and
>> > confidential. If the reader of the message is not the intended
>> > recipient or an authorized representative of the intended
>> > recipient, you are hereby notified that any dissemination of this
>> > communication is strictly prohibited. If you have received this
>> > communication in error, notify the sender immediately by return
>> > email and delete the message and any attachments from your system.
>>
>
> ---------------------------------------------------------------------
> 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]
