What I do, is using a directory with the version number in:

                <dependency>
                        <groupId>someDllWeUse</groupId>
                        <artifactId>someDllWeUse.dll</artifactId>
                        <version>2.0.1</version>
                        <jar>2.0.1/someDllWeUse.dll</jar>
                        <type>dll</type>
                </dependency>

If you then create the following directories on your repository, it should
work:

someDllWeUse
|
+-- dlls
     |
     +---2.01
          |
          +--- someDllWeUse.dll

regards,

Wim

-----Original Message-----
From: Martin Heitz [mailto:[EMAIL PROTECTED]
Sent: maandag 7 maart 2005 8:42
To: Maven Users List
Subject: artifacts that shall not have version information in the name


Hi,

how do you deal with artifacts (ejb-jar, war, ear files) that shall not
have version information in the name?

I know that there is the possibility to override the artifact file name
with the <jar> tag, but how will the maven repository deal with the
different versions then?

The problem with version info in the name is that any runtime
redeployment in a J2EE server fails, because the servers do not
recognize the application to be the same...


Best regards from sunny frozen Black Forrest, Germany,
   Mattin

P.S. Probably this is a standard question, but I couldn't find any hint
on this in the Maven FAQ...

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

- - - - - - - DISCLAIMER- - - - - - - -
Unless indicated otherwise, the information contained in this message is
privileged and confidential, and is intended only for the use of the
addressee(s) named above and others who have been specifically authorized to
receive it. If you are not the intended recipient, you are hereby notified
that any dissemination, distribution or copying of this message and/or
attachments is strictly prohibited. The company accepts no liability for any
damage caused by any virus transmitted by this email. Furthermore, the
company does not warrant a proper and complete transmission of this
information, nor does it accept liablility for any delays. If you have
received this message in error, please contact the sender and delete the
message. Thank you.

Reply via email to