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
Yep, but it's enough if you're deploying to some container and you don't
want the wars your deploying to have version number :)
On 3/28/07, Stephane Nicoll <[EMAIL PROTECTED]> wrote:
Hi,
On 3/28/07, Franz Allan Valencia See <[EMAIL PROTECTED]> wrote:
> Good day to you, Dheeraj,
>
> Try
>
>
>
Hi,
On 3/28/07, Franz Allan Valencia See <[EMAIL PROTECTED]> wrote:
Good day to you, Dheeraj,
Try
...
${artifactId}
...
...
By default, the value of finalName is "${artifactId}-${version}" ( without
the quotes ) which every pom inherits from the super pom ( see [1] ).
Th
Good day to you, Dheeraj,
Try
...
${artifactId}
...
...
By default, the value of finalName is "${artifactId}-${version}" ( without
the quotes ) which every pom inherits from the super pom ( see [1] ).
..btw, you might want to try asking in the maven users list next time to get
a
Just curious, but I'm interested in why you want to do this. It drives
me nuts when I get a product such as Jboss and I can't figure out what
version it is using just by looking at the file name. OTOH, I'd be just
as happy to run a command line program that could accurately tell me the
versio
Hi,
Using Maven generates all the artifacts (jars/wars/ears)
with a unique filename -.. 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
