IMO what you are trying to do is no more no less then cheat your build
managers :)
If they dislike the idea of SNAPSHOT artifacts - its better not to use them
or explain to
them what for you need to use them.
You may also consider using <currentVersion>2.1-SNAPSHOT</currentVersion>
<dependency>
<version>2.1-SNAPSHOT</version>
<dependency>
this is what will be soon a default and recommended way of doing (this
allows to have snapshot per version (branch))
In m2 we have already one single install goal which is "smart" enough to
check project's type and version .
It means that soon you will be able to do:
maven install
and this will do what (depending of the context) what jar:install,
jar:install-snapshot, war:install, ejb:install, ejb:install-snapshot etc
goals used to do.
Michal
> -----Original Message-----
> From: Marcel Vehof [mailto:[EMAIL PROTECTED]
> Sent: Friday, July 23, 2004 10:45 AM
> To: '[EMAIL PROTECTED]'
> Subject: problem using snapshots in JAR override
>
>
>
> Hello,
>
> In our organization we want to use snapshot versions of
> some of our libraries, during developing.
> Normally, this would be done by stating the version number
> for the library as SNAPSHOT in project.xml
> But this practice is not allowed by our build managers,
> they only want references to officially released versions
> in project.xml
>
> So, I tried the JAR override feature and added the following
> to build.properties (since this file is not in version control,
> the content is no problem for the build managers) :
>
> maven.jar.override=on
> maven.jar.mylibrary=SNAPSHOT
>
> This does not work as I expected, what happens is that the
> snapshot dependency is downloaded, but to the home directory
> of the project, with filename "Snapshot".
> Also when building an EAR, the library ends up with filename
> "Snapshot". Besides that this is not the correct name, it will
> definitely not work if there are more than one snapshot
> dependency in the project.
>
> Does any one know how to solve this ?
>
>
> Marcel Vehof
>
> ---
> This message is confidential and may be privileged. Any review,
> retransmission, dissemination or other use of, or taking any
> action with
> reference to this information by persons other than the
> intended recipient
> is prohibited. If you received this message in error, please
> notify the
> sender by reply e-mail and delete this message from all
> computers. Please
> note that e-mails are susceptible to change. The sender will
> not accept
> liability for the improper or incomplete transmission of the
> information
> contained in this message.
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
