Yes, you will need to change the name to have the word "SNAPSHOT" in it.
You *may* be able to just add a <jar>logging-client.jar</jar> tag, not
sure...

Eric

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, February 02, 2005 2:21 PM
To: Maven Users List
Subject: Re: is there a way to force maven to always download a
dependency?








Eric Pugh, thanks for your response. Question: do I need a property set
in project.properties or project.xml to make SNAPSHOT work? Here's my
dependency: <dependency>
      <groupId>loggingservice</groupId>
      <artifactId>logging-client</artifactId>
      <version>SNAPSHOT</version>
 </dependency>

This is what Maven tried to do:
Attempting to download logging-client-SNAPSHOT.jar.

Does the jar require SNAPSHOT in the name?  I haven't used the SNAPSHOT
feature till now.


David, a script as you suggest may be my only way out. Using a pregoal
to delete an unversioned jar file before every build is ugly, but may be
the only way. No argument here about the qualities of versioning, I'm
dealing with a worst case scenario.

Thanks again to all
Tom

David Jencks <[EMAIL PROTECTED]> wrote on 02/02/2005 01:53:55 PM:

> depending on a SNAPSHOT version has maven check the timestamp to see 
> if a newer version should be downloaded.
>
> If you figure out a way to make maven work from unversioned artifacts 
> you will make your project subject to many of the incompatible-version

> ills that maven's solution for are perhaps the main reason to use 
> maven.
>
> However, I would think the simplest way to force maven to download a 
> particular jar for every build, whether or not the remote repo copy's 
> timestamp has changed or is newer than the local copy (this is what 
> you are asking for, right?) is to write a little script to remove it 
> from the local repo.  You might have to run this separately from your 
> main build.  You could have a goal to do this on specially marked 
> dependencies.
>
> david jencks
>
> On Feb 2, 2005, at 10:46 AM, Eric Pugh wrote:
>
> > Are you sure about this?  I believe SNAPSHOT will do exactly what 
> > you want.  There may (I can't remember) be some logic about checking

> > timestamps or something...  But as far as I recall, you should be 
> > downloading everytime.
> >
> > ERic
> >
> > -----Original Message-----
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> > Sent: Wednesday, February 02, 2005 12:07 PM
> > To: Maven Users List
> > Subject: is there a way to force maven to always download a 
> > dependency?
> >
> >
> >
> >
> >
> >
> >
> > What if some jar files are not versioned (and maybe will never be 
> > versioned). Is there a way to force Maven to always go to the remote

> > repositories to resolve dependencies?
> >
> > I've tried SNAPSHOT, but that does not reload a dependency every 
> > time a build is executed.
> >
> > Thanks for your help.
> > Tom
> >
> >
> >
> >
> > This message is intended for the recipient only and is not meant to 
> > be forwarded or distributed in any other format. 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 security, or as an official confirmation of any 
> > transaction.  Putnam does not accept purchase or redemptions of
securities, instructions, or
> > authorizations that are sent via e-mail.   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 Putnam, 
> > LLC (DBA Putnam
> > Investments) and its subsidiaries and affiliates.  If you are not
the
> > intended recipient of this e-mail, please delete the e-mail.
> >
> > --------------------------------------------------------------------
> > -
> > 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]
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>



 
This message is intended for the recipient only and is not meant to be
forwarded or distributed in any other format. 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
security, or as an official confirmation of any transaction.  Putnam
does not accept purchase or redemptions of securities, instructions, or
authorizations that are sent via e-mail.   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 Putnam, LLC (DBA Putnam
Investments) and its subsidiaries and affiliates.  If you are not the
intended recipient of this e-mail, please delete the e-mail.

---------------------------------------------------------------------
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]

Reply via email to