You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Th...@putnam.com on 2005/02/02 18:07:06 UTC
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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: is there a way to force maven to always download a dependency?
Posted by Steve Molloy <sm...@convera.com>.
The problem is when you do not have any control on the jars you rely
on...
I had the same problem, with projects depending on jars which were
changing but were not tagged with any version. What I ended up doing is
host them locally, renaming each one by adding "-SNAPSHOT"... Not very
clean, but it works...
Steve
On Wed, 2005-02-02 at 12:54 -0500, Eric Giguere wrote:
> Hi
> No, cannot.
> But I would suggest to version all your jars and maybe remove the
> versions at deployment if it is an issue.
>
> We are using this technique and the jar compatibility nightmare (jars in
> cvs, versions clashing, etc) ended and never came back!
>
> HTH.
> Eric.
>
>
>
> Thomas_Perry@putnam.com wrote:
>
> >
> >
> >
> >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: users-unsubscribe@maven.apache.org
> >For additional commands, e-mail: users-help@maven.apache.org
> >
> >
> >
> >
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
Re: is there a way to force maven to always download a dependency?
Posted by Eric Giguere <er...@videotron.ca>.
Hi Thomas.
Ah, got the wrong guy ;)
I'm not a "Maven way" zealot.. I create and modify plugins so that maven
fits my needs and not the other way around. Maven is an
integration/building tool, (and a great one) not a religion.. not for
me anyway. I have no problems at all twisting it and making it more
adapted to "real life" (pronounce:
typical-not-so-organized-company-produced-software-projects...) projects.
Take a look at my plugin then: named uber-dist. It resides on
sourceforge. Maybe it can help you. This guy introduced properties for
dependency for automatic dependency publishing with renaming
capabilities (to eliminate the version for instance).
I am a team leader in a company that didn't have any clue about maven
before me. I did though versionned the jars when I migrated the project
from Ant to Maven. It was a little pain at the beginning but now, we
rely on the central repository and the team never messes up now since
all is driven though the project.xml. Our main project is not at all the
perfect Maven project template. The main project builds I don't know how
many artifacts, I have multiple sub-projects that uses the parent's
sources as well as the parent's target. But everything works just
perfectly now. Most of those projects were alive before Maven came in.
Here, take a look, an example on an "extended" dependency definition we
use with the plugin:
<dependency>
<groupId>commons-digester</groupId>
<artifactId>commons-digester</artifactId>
<version>1.5</version>
<url>http://jakarta.apache.org/commons/digester/</url>
<properties>
<CMS.deploy>true</CMS.deploy>
<jar.dependency.dist.dir>lib/3rdparty/catalina</jar.dependency.dist.dir>
<jar.dependency.dist.name>commons-digester.jar</jar.dependency.dist.name>
<!-- NOTE: Required by struts.jar -->
</properties>
</dependency>
With these, you can deploy, in the subdirectory you want and the jar
gets renamed. But, in terms of configuration management, you always know
what exact version you need by looking at project.xml... not at the
actual distribution since nearly all the jars gets renamed. Legacy stuff...
GLuck with your project then
Eric.
The CMS.deploy tells upber
Thomas_Perry@putnam.com wrote:
>
>
>
>
>ok, I understand that it goes against all that Maven stands for :-)
>
>But I wish there were some property that could be added on a per-dependency
>basis that would
>force Maven to download the dependency every build. Just for weird
>situations, like teams working
>on company projects don't want to get into versioning their jars.
>
>Thanks again.
>Tom
>
>
>
>
> Eric Giguere
> <eric.giguere@vid
> eotron.ca> To
> Maven Users List
> 02/02/2005 12:54 <us...@maven.apache.org>
> PM cc
>
> Subject
> Please respond to Re: is there a way to force maven
> "Maven Users to always download a dependency?
> List"
> <users@maven.apac
> he.org>
>
>
>
>
>
>
>
>Hi
>No, cannot.
>But I would suggest to version all your jars and maybe remove the
>versions at deployment if it is an issue.
>
>We are using this technique and the jar compatibility nightmare (jars in
>cvs, versions clashing, etc) ended and never came back!
>
>HTH.
>Eric.
>
>
>
>Thomas_Perry@putnam.com wrote:
>
>
>
>>
>>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: users-unsubscribe@maven.apache.org
>>For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>>
>>
>>
>>
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>For additional commands, e-mail: users-help@maven.apache.org
>
>
>
>
>
>
>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: users-unsubscribe@maven.apache.org
>For additional commands, e-mail: users-help@maven.apache.org
>
>
>
>
Re: is there a way to force maven to always download a dependency?
Posted by Th...@putnam.com.
ok, I understand that it goes against all that Maven stands for :-)
But I wish there were some property that could be added on a per-dependency
basis that would
force Maven to download the dependency every build. Just for weird
situations, like teams working
on company projects don't want to get into versioning their jars.
Thanks again.
Tom
Eric Giguere
<eric.giguere@vid
eotron.ca> To
Maven Users List
02/02/2005 12:54 <us...@maven.apache.org>
PM cc
Subject
Please respond to Re: is there a way to force maven
"Maven Users to always download a dependency?
List"
<users@maven.apac
he.org>
Hi
No, cannot.
But I would suggest to version all your jars and maybe remove the
versions at deployment if it is an issue.
We are using this technique and the jar compatibility nightmare (jars in
cvs, versions clashing, etc) ended and never came back!
HTH.
Eric.
Thomas_Perry@putnam.com wrote:
>
>
>
>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: users-unsubscribe@maven.apache.org
>For additional commands, e-mail: users-help@maven.apache.org
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: is there a way to force maven to always download a dependency?
Posted by Eric Giguere <er...@videotron.ca>.
Hi
No, cannot.
But I would suggest to version all your jars and maybe remove the
versions at deployment if it is an issue.
We are using this technique and the jar compatibility nightmare (jars in
cvs, versions clashing, etc) ended and never came back!
HTH.
Eric.
Thomas_Perry@putnam.com wrote:
>
>
>
>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: users-unsubscribe@maven.apache.org
>For additional commands, e-mail: users-help@maven.apache.org
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Maven turbine:setup failed!
Posted by Inandjo Taurel <in...@hotmail.com>.
hi,
I'm trying to generate my first turbine app with META, by entering the
following command :
maven -Dturbine.setup.properties=setup.properties turbine:setup
Here is the error I get:
BUILD FAILED
File...... C:\Documents and
Settings\Administrateur\.maven\cache\maven-turbine-p
lugin-1.2\plugin.jelly
Element... include
Line...... 857
Column.... 43
java.lang.NullPointerException
[INFO] App - -Total time: 3 seconds
[INFO] App - -Finished at: Tue Feb 01 04:57:51 GMT 2005
[INFO] App - -
I am running this command from the tomcat webapps directory
(C:\Program Files\Apache Group\Tomcat 4.1\webapps), where I have the
project.xml
file, the setup.properties file, as well as the build.properties file.
This is the content of my project.xml file:
<?xml version="1.0" encoding="UTF-8"?>
<project>
<pomVersion>3</pomVersion>
<id>myapp</id>
<name>My first test</name>
</project>
This is the content of my build.properties file:
maven.appserver.home = C:/Program Files/Apache Group/Tomcat 4.1
maven.appserver.name = tomcat
This is the content of my setup.properties file:
turbine.plugin.mode = inplace
turbine.app.name = myapp
turbine.app.flavor = turbine-2.3.1
turbine.app.om.layer = torque
turbine.app.setup.demo = false
torque.database = mysql
torque.database.driver = com.mysql.jdbc.Driver
torque.database.user = test
torque.database.password = test
torque.database.buildUrl = jdbc:mysql://localhost/myapp
torque.database.createUrl = jdbc:mysql://localhost/myapp
The command generate the folders alright but there are no files in them
despite the fact that
it is supposed to be copying some files from the turbine plugin.
Also, I put an <ant:echo message="${include}"> a couple of lines before the
crashing include, in
the plugin.jelly file under the turbine plugin folder: it echoed "**/*".
I'm using a win2k SP4 box with tomcat 4.1.31, and maven 1.0.2.
Is there anything I'm doing wrong or missing here??
Thanx.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: is there a way to force maven to always download a dependency?
Posted by Eric Pugh <ep...@upstate.com>.
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: Thomas_Perry@putnam.com [mailto:Thomas_Perry@putnam.com]
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 <da...@yahoo.com> 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: Thomas_Perry@putnam.com [mailto:Thomas_Perry@putnam.com]
> > 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: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
> > --------------------------------------------------------------------
> > -
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: is there a way to force maven to always download a dependency?
Posted by Th...@putnam.com.
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 <da...@yahoo.com> 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: Thomas_Perry@putnam.com [mailto:Thomas_Perry@putnam.com]
> > 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: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: is there a way to force maven to always download a dependency?
Posted by David Jencks <da...@yahoo.com>.
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: Thomas_Perry@putnam.com [mailto:Thomas_Perry@putnam.com]
> 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: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: is there a way to force maven to always download a dependency?
Posted by Th...@putnam.com.
You know what, I didn't test by changing the timestamp on a jar in our
(internal) remote repository.
I just ran a project build consecutively on my desktop and watched if the
SNAPSHOT dependency
caused the jar to be re-loaded every time; it didn't.
I'm going to re-test by touching the timestamp on a jar in our repository
and check it out.
Thanks for the tip.
Tom
"Eric Pugh" <ep...@upstate.com> wrote on 02/02/2005 01:46:25 PM:
> 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: Thomas_Perry@putnam.com [mailto:Thomas_Perry@putnam.com]
> 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: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: is there a way to force maven to always download a dependency?
Posted by Eric Pugh <ep...@upstate.com>.
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: Thomas_Perry@putnam.com [mailto:Thomas_Perry@putnam.com]
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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org