You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Yaakov Chaikin <ya...@gmail.com> on 2008/09/16 19:47:53 UTC
Jar not updating from remote repo
Hi,
I am using Maven 2.0.8.
I have a custom remote maven repo with some JARs imported there. I
recently updated one of the JARs there, but noticed that when I built
on the client, no update was pulled from the remote repo and my local
repo still has the old one. Only after I erased the actual JAR from
the local repo, did it pull the file from the remote repo.
I checked and all the files in the directory under (version) 1.0 of
that JAR file have new timestamps, so it's definitely new.
I then tried to force by doing this:
mvn -U clean install
That didn't bring in the new JAR.
I then tried to edit the update policy and explicitely says "always":
<repositories>
<repository>
<id>central</id>
<name>FES Unclass Maven Repository</name>
<url>https://xxx</url>
<snapshots>
<updatePolicy>always</updatePolicy>
<enabled>true</enabled>
</snapshots>
<releases>
<enabled>true</enabled>
<updatePolicy>always</updatePolicy>
</releases>
</repository>
</repositories>
<pluginRepositories>
<pluginRepository>
<id>central</id>
<name>FES Unclass Maven Repository</name>
<url>https://xxx</url>
</pluginRepository>
</pluginRepositories>
However, that didn't work either.
Am I doing something wrong here?
Thanks,
Yaakov.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Jar not updating from remote repo
Posted by Wayne Fay <wa...@gmail.com>.
On Tue, Sep 16, 2008 at 11:26 AM, Yaakov Chaikin
<ya...@gmail.com> wrote:
> Oh, I see. Makes sense... The official documentation bites again. It'd
> be much great if it was clearer than what it is now.
If you have a specific problem with the documentation, you should file
a JIRA issue so it can be addressed. If this is just a general
complaint, then that is much less useful.
Wayne
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Jar not updating from remote repo
Posted by Yaakov Chaikin <ya...@gmail.com>.
Oh, I see. Makes sense... The official documentation bites again. It'd
be much great if it was clearer than what it is now.
Thanks for the explanation.
Yaakov.
On Tue, Sep 16, 2008 at 2:21 PM, Stephen Connolly
<st...@gmail.com> wrote:
> The update ppolicy for a remote repo will control how often maven looks for
> updates versions being available also...
>
> but the thing is this is only is Maven thinks it could use a newer
> version...
>
> so if your dependency is like
>
> <version>1.0</version>
>
> then that's a "no fixed version, but I'd suggest to use 1.0" and as long as
> Maven has a 1.0 downloaded, there's no need to check.
>
> Similarly if you have
>
> <version>[1.0]</version>
>
> However, if you have
>
> <version>[1.0,2.0-!)</version>
>
> Then Maven _can_ use a newer one if available. If no other project is
> forcing or strongly suggesting a specific version within the range, then
> Maven will use the update policy to decide how often to check for other
> versions that match the range(s) that apply for the version.
>
> At least that's my understanding (and results of some quick experiments)
>
> -Stephen
>
> On Tue, Sep 16, 2008 at 7:00 PM, Yaakov Chaikin <ya...@gmail.com>wrote:
>
>> Hmm... Is that REALLY true? The documentation for the 'updatePolicy'
>> certainly seems to disagree since it exists for both <snapshots> and
>> <releases>:
>> "updatePolicy: This element specifies how often updates should attempt
>> to occur. Maven will compare the local POM's timestamp (stored in a
>> repository's maven-metadata file) to the remote. The choices are:
>> always, daily (default), interval:X (where X is an integer in minutes)
>> or never."
>>
>> The documentation for mvn --help also says this for '-U':
>> -U,--update-snapshots Forces a check for updated releases and
>> snapshots on remote repositories
>>
>> So, how do you explain these then? What do they do?
>>
>>
>> On Tue, Sep 16, 2008 at 1:53 PM, Wayne Fay <wa...@gmail.com> wrote:
>> > Maven NEVER updates jars that have a non-snapshot version associated with
>> them.
>> >
>> > If you are "updating" jars then they MUST be called a.b.c-SNAPSHOT for
>> > Maven to notice the changes.
>> >
>> > Wayne
>> >
>> > On Tue, Sep 16, 2008 at 10:47 AM, Yaakov Chaikin
>> > <ya...@gmail.com> wrote:
>> >> Hi,
>> >>
>> >> I am using Maven 2.0.8.
>> >>
>> >> I have a custom remote maven repo with some JARs imported there. I
>> >> recently updated one of the JARs there, but noticed that when I built
>> >> on the client, no update was pulled from the remote repo and my local
>> >> repo still has the old one. Only after I erased the actual JAR from
>> >> the local repo, did it pull the file from the remote repo.
>> >>
>> >> I checked and all the files in the directory under (version) 1.0 of
>> >> that JAR file have new timestamps, so it's definitely new.
>> >>
>> >> I then tried to force by doing this:
>> >> mvn -U clean install
>> >>
>> >> That didn't bring in the new JAR.
>> >>
>> >> I then tried to edit the update policy and explicitely says "always":
>> >> <repositories>
>> >> <repository>
>> >> <id>central</id>
>> >> <name>FES Unclass Maven Repository</name>
>> >> <url>https://xxx</url>
>> >> <snapshots>
>> >> <updatePolicy>always</updatePolicy>
>> >> <enabled>true</enabled>
>> >> </snapshots>
>> >> <releases>
>> >> <enabled>true</enabled>
>> >> <updatePolicy>always</updatePolicy>
>> >> </releases>
>> >> </repository>
>> >> </repositories>
>> >> <pluginRepositories>
>> >> <pluginRepository>
>> >> <id>central</id>
>> >> <name>FES Unclass Maven Repository</name>
>> >> <url>https://xxx</url>
>> >> </pluginRepository>
>> >> </pluginRepositories>
>> >>
>> >> However, that didn't work either.
>> >>
>> >> Am I doing something wrong here?
>> >>
>> >> Thanks,
>> >> Yaakov.
>> >>
>> >> ---------------------------------------------------------------------
>> >> 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
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Jar not updating from remote repo
Posted by Yaakov Chaikin <ya...@gmail.com>.
Thanks. I get it now. the documentation was just misleading on this...
In my situation, it's like 30 JARs from a non-mavenized older build,
so I have to import them into the repo manually... But I guess, I can
import them as versions "1.0-SNAPSHOT" and be done with it
Thanks,
Yaakov.
On Tue, Sep 16, 2008 at 2:24 PM, Stephen Connolly
<st...@gmail.com> wrote:
> The *key* thing to understand is that once Maven downloads foo-1.0.jar and
> has it in its local repository, it will *never* download it again.
>
> This is why you should always keep the version as -SNAPSHOT and use the
> release plugin (or roll your own scripts if you're crazy) to roll a release.
>
> The result of using the release plugin is that developers will never
> _normally_ build a non-SNAPSHOT version, and each build of a non-SNAPSHOT
> will get deployed to your maven repo... and they should only be being built
> once to ensure that there is only one release of the artifact for that
> version number.
>
> On Tue, Sep 16, 2008 at 7:21 PM, Stephen Connolly <
> stephen.alan.connolly@gmail.com> wrote:
>
>> The update ppolicy for a remote repo will control how often maven looks for
>> updates versions being available also...
>>
>> but the thing is this is only is Maven thinks it could use a newer
>> version...
>>
>> so if your dependency is like
>>
>> <version>1.0</version>
>>
>> then that's a "no fixed version, but I'd suggest to use 1.0" and as long as
>> Maven has a 1.0 downloaded, there's no need to check.
>>
>> Similarly if you have
>>
>> <version>[1.0]</version>
>>
>> However, if you have
>>
>> <version>[1.0,2.0-!)</version>
>>
>> Then Maven _can_ use a newer one if available. If no other project is
>> forcing or strongly suggesting a specific version within the range, then
>> Maven will use the update policy to decide how often to check for other
>> versions that match the range(s) that apply for the version.
>>
>> At least that's my understanding (and results of some quick experiments)
>>
>> -Stephen
>>
>>
>> On Tue, Sep 16, 2008 at 7:00 PM, Yaakov Chaikin <ya...@gmail.com>wrote:
>>
>>> Hmm... Is that REALLY true? The documentation for the 'updatePolicy'
>>> certainly seems to disagree since it exists for both <snapshots> and
>>> <releases>:
>>> "updatePolicy: This element specifies how often updates should attempt
>>> to occur. Maven will compare the local POM's timestamp (stored in a
>>> repository's maven-metadata file) to the remote. The choices are:
>>> always, daily (default), interval:X (where X is an integer in minutes)
>>> or never."
>>>
>>> The documentation for mvn --help also says this for '-U':
>>> -U,--update-snapshots Forces a check for updated releases and
>>> snapshots on remote repositories
>>>
>>> So, how do you explain these then? What do they do?
>>>
>>>
>>> On Tue, Sep 16, 2008 at 1:53 PM, Wayne Fay <wa...@gmail.com> wrote:
>>> > Maven NEVER updates jars that have a non-snapshot version associated
>>> with them.
>>> >
>>> > If you are "updating" jars then they MUST be called a.b.c-SNAPSHOT for
>>> > Maven to notice the changes.
>>> >
>>> > Wayne
>>> >
>>> > On Tue, Sep 16, 2008 at 10:47 AM, Yaakov Chaikin
>>> > <ya...@gmail.com> wrote:
>>> >> Hi,
>>> >>
>>> >> I am using Maven 2.0.8.
>>> >>
>>> >> I have a custom remote maven repo with some JARs imported there. I
>>> >> recently updated one of the JARs there, but noticed that when I built
>>> >> on the client, no update was pulled from the remote repo and my local
>>> >> repo still has the old one. Only after I erased the actual JAR from
>>> >> the local repo, did it pull the file from the remote repo.
>>> >>
>>> >> I checked and all the files in the directory under (version) 1.0 of
>>> >> that JAR file have new timestamps, so it's definitely new.
>>> >>
>>> >> I then tried to force by doing this:
>>> >> mvn -U clean install
>>> >>
>>> >> That didn't bring in the new JAR.
>>> >>
>>> >> I then tried to edit the update policy and explicitely says "always":
>>> >> <repositories>
>>> >> <repository>
>>> >> <id>central</id>
>>> >> <name>FES Unclass Maven Repository</name>
>>> >> <url>https://xxx</url>
>>> >> <snapshots>
>>> >> <updatePolicy>always</updatePolicy>
>>> >> <enabled>true</enabled>
>>> >> </snapshots>
>>> >> <releases>
>>> >> <enabled>true</enabled>
>>> >> <updatePolicy>always</updatePolicy>
>>> >> </releases>
>>> >> </repository>
>>> >> </repositories>
>>> >> <pluginRepositories>
>>> >> <pluginRepository>
>>> >> <id>central</id>
>>> >> <name>FES Unclass Maven Repository</name>
>>> >> <url>https://xxx</url>
>>> >> </pluginRepository>
>>> >> </pluginRepositories>
>>> >>
>>> >> However, that didn't work either.
>>> >>
>>> >> Am I doing something wrong here?
>>> >>
>>> >> Thanks,
>>> >> Yaakov.
>>> >>
>>> >> ---------------------------------------------------------------------
>>> >> 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
>>>
>>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Jar not updating from remote repo
Posted by Yaakov Chaikin <ya...@gmail.com>.
The plugin for which the pom is being downloaded is not a custom
plugin. It's something that Maven downloaded automatically. I did use
that command to import other JARs though. So, what would this help?
Are you saying that I should pull out that maven plugin jar out of the
repository and use this command to import it back again?
Yaakov.
P.S. (I believe generatePom=true is the default).
On Wed, Sep 17, 2008 at 2:16 AM, Stephen Connolly
<st...@gmail.com> wrote:
> Have a look at
>
> mvn deploy:deploy-file -DgeneratePom=true -Dfile=myjar.jar
> -Dversion=1.0-SNAPSHOT -DartifactId=foo -DgroupId=com.foobar
>
>
> On Wed, Sep 17, 2008 at 12:51 AM, Yaakov Chaikin
> <ya...@gmail.com>wrote:
>
>> Well, I ran the mvn clean install, etc. using the DSMP proxy server
>> and then moved what it cached into the repository. I didn't actually
>> manually deploy anything except those JARs from a parallel project.
>>
>> How do I deploy those poms?
>>
>> Thanks,
>> Yaakov.
>>
>> On Tue, Sep 16, 2008 at 6:59 PM, Stephen Connolly
>> <st...@gmail.com> wrote:
>> > It's looking for the poms...
>> >
>> > did you deploy poms?
>> >
>> > BTW when doing a deploy you can generate basic poms if you don't have a
>> pom
>> > to deploy
>> >
>> > On Tue, Sep 16, 2008 at 8:14 PM, Yaakov Chaikin <
>> yaakov.chaikin@gmail.com>wrote:
>> >
>> >> DO you know why, given my <repositories> setup, every time I ran, it
>> >> downloads the following:
>> >>
>> >> Downloading:
>> >>
>> https://xxxxx/maven/org/codehaus/plexus/plexus-component-api/1.0-alpha-15/plexus-component-api-1.0-alpha-15.pom
>> >> Downloading:
>> >>
>> https://xxxxx/maven/org/codehaus/plexus/plexus-component-api/1.0-alpha-15/plexus-component-api-1.0-alpha-15.pom
>> >> Downloading:
>> >>
>> https://xxxxx/maven/org/codehaus/plexus/plexus-container-default/1.0-alpha-15/plexus-container-default-1.0-alpha-15.pom
>> >> Downloading:
>> >>
>> https://xxxxx/maven/org/codehaus/plexus/plexus-container-default/1.0-alpha-15/plexus-container-default-1.0-alpha-15.pom
>> >>
>> >> How do I disable downloading this every time?
>> >>
>> >> Thanks,
>> >> Yaakov.
>> >>
>> >> On Tue, Sep 16, 2008 at 2:24 PM, Stephen Connolly
>> >> <st...@gmail.com> wrote:
>> >> > The *key* thing to understand is that once Maven downloads foo-1.0.jar
>> >> and
>> >> > has it in its local repository, it will *never* download it again.
>> >> >
>> >> > This is why you should always keep the version as -SNAPSHOT and use
>> the
>> >> > release plugin (or roll your own scripts if you're crazy) to roll a
>> >> release.
>> >> >
>> >> > The result of using the release plugin is that developers will never
>> >> > _normally_ build a non-SNAPSHOT version, and each build of a
>> non-SNAPSHOT
>> >> > will get deployed to your maven repo... and they should only be being
>> >> built
>> >> > once to ensure that there is only one release of the artifact for that
>> >> > version number.
>> >> >
>> >> > On Tue, Sep 16, 2008 at 7:21 PM, Stephen Connolly <
>> >> > stephen.alan.connolly@gmail.com> wrote:
>> >> >
>> >> >> The update ppolicy for a remote repo will control how often maven
>> looks
>> >> for
>> >> >> updates versions being available also...
>> >> >>
>> >> >> but the thing is this is only is Maven thinks it could use a newer
>> >> >> version...
>> >> >>
>> >> >> so if your dependency is like
>> >> >>
>> >> >> <version>1.0</version>
>> >> >>
>> >> >> then that's a "no fixed version, but I'd suggest to use 1.0" and as
>> long
>> >> as
>> >> >> Maven has a 1.0 downloaded, there's no need to check.
>> >> >>
>> >> >> Similarly if you have
>> >> >>
>> >> >> <version>[1.0]</version>
>> >> >>
>> >> >> However, if you have
>> >> >>
>> >> >> <version>[1.0,2.0-!)</version>
>> >> >>
>> >> >> Then Maven _can_ use a newer one if available. If no other project
>> is
>> >> >> forcing or strongly suggesting a specific version within the range,
>> then
>> >> >> Maven will use the update policy to decide how often to check for
>> other
>> >> >> versions that match the range(s) that apply for the version.
>> >> >>
>> >> >> At least that's my understanding (and results of some quick
>> experiments)
>> >> >>
>> >> >> -Stephen
>> >> >>
>> >> >>
>> >> >> On Tue, Sep 16, 2008 at 7:00 PM, Yaakov Chaikin <
>> >> yaakov.chaikin@gmail.com>wrote:
>> >> >>
>> >> >>> Hmm... Is that REALLY true? The documentation for the 'updatePolicy'
>> >> >>> certainly seems to disagree since it exists for both <snapshots> and
>> >> >>> <releases>:
>> >> >>> "updatePolicy: This element specifies how often updates should
>> attempt
>> >> >>> to occur. Maven will compare the local POM's timestamp (stored in a
>> >> >>> repository's maven-metadata file) to the remote. The choices are:
>> >> >>> always, daily (default), interval:X (where X is an integer in
>> minutes)
>> >> >>> or never."
>> >> >>>
>> >> >>> The documentation for mvn --help also says this for '-U':
>> >> >>> -U,--update-snapshots Forces a check for updated releases
>> and
>> >> >>> snapshots on remote repositories
>> >> >>>
>> >> >>> So, how do you explain these then? What do they do?
>> >> >>>
>> >> >>>
>> >> >>> On Tue, Sep 16, 2008 at 1:53 PM, Wayne Fay <wa...@gmail.com>
>> wrote:
>> >> >>> > Maven NEVER updates jars that have a non-snapshot version
>> associated
>> >> >>> with them.
>> >> >>> >
>> >> >>> > If you are "updating" jars then they MUST be called a.b.c-SNAPSHOT
>> >> for
>> >> >>> > Maven to notice the changes.
>> >> >>> >
>> >> >>> > Wayne
>> >> >>> >
>> >> >>> > On Tue, Sep 16, 2008 at 10:47 AM, Yaakov Chaikin
>> >> >>> > <ya...@gmail.com> wrote:
>> >> >>> >> Hi,
>> >> >>> >>
>> >> >>> >> I am using Maven 2.0.8.
>> >> >>> >>
>> >> >>> >> I have a custom remote maven repo with some JARs imported there.
>> I
>> >> >>> >> recently updated one of the JARs there, but noticed that when I
>> >> built
>> >> >>> >> on the client, no update was pulled from the remote repo and my
>> >> local
>> >> >>> >> repo still has the old one. Only after I erased the actual JAR
>> from
>> >> >>> >> the local repo, did it pull the file from the remote repo.
>> >> >>> >>
>> >> >>> >> I checked and all the files in the directory under (version) 1.0
>> of
>> >> >>> >> that JAR file have new timestamps, so it's definitely new.
>> >> >>> >>
>> >> >>> >> I then tried to force by doing this:
>> >> >>> >> mvn -U clean install
>> >> >>> >>
>> >> >>> >> That didn't bring in the new JAR.
>> >> >>> >>
>> >> >>> >> I then tried to edit the update policy and explicitely says
>> >> "always":
>> >> >>> >> <repositories>
>> >> >>> >> <repository>
>> >> >>> >> <id>central</id>
>> >> >>> >> <name>FES Unclass Maven Repository</name>
>> >> >>> >> <url>https://xxx</url>
>> >> >>> >> <snapshots>
>> >> >>> >>
>> <updatePolicy>always</updatePolicy>
>> >> >>> >> <enabled>true</enabled>
>> >> >>> >> </snapshots>
>> >> >>> >> <releases>
>> >> >>> >> <enabled>true</enabled>
>> >> >>> >>
>> <updatePolicy>always</updatePolicy>
>> >> >>> >> </releases>
>> >> >>> >> </repository>
>> >> >>> >> </repositories>
>> >> >>> >> <pluginRepositories>
>> >> >>> >> <pluginRepository>
>> >> >>> >> <id>central</id>
>> >> >>> >> <name>FES Unclass Maven Repository</name>
>> >> >>> >> <url>https://xxx</url>
>> >> >>> >> </pluginRepository>
>> >> >>> >> </pluginRepositories>
>> >> >>> >>
>> >> >>> >> However, that didn't work either.
>> >> >>> >>
>> >> >>> >> Am I doing something wrong here?
>> >> >>> >>
>> >> >>> >> Thanks,
>> >> >>> >> Yaakov.
>> >> >>> >>
>> >> >>> >>
>> >> ---------------------------------------------------------------------
>> >> >>> >> 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
>> >> >>>
>> >> >>>
>> >> >>
>> >> >
>> >>
>> >> ---------------------------------------------------------------------
>> >> 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: Jar not updating from remote repo
Posted by Stephen Connolly <st...@gmail.com>.
Have a look at
mvn deploy:deploy-file -DgeneratePom=true -Dfile=myjar.jar
-Dversion=1.0-SNAPSHOT -DartifactId=foo -DgroupId=com.foobar
On Wed, Sep 17, 2008 at 12:51 AM, Yaakov Chaikin
<ya...@gmail.com>wrote:
> Well, I ran the mvn clean install, etc. using the DSMP proxy server
> and then moved what it cached into the repository. I didn't actually
> manually deploy anything except those JARs from a parallel project.
>
> How do I deploy those poms?
>
> Thanks,
> Yaakov.
>
> On Tue, Sep 16, 2008 at 6:59 PM, Stephen Connolly
> <st...@gmail.com> wrote:
> > It's looking for the poms...
> >
> > did you deploy poms?
> >
> > BTW when doing a deploy you can generate basic poms if you don't have a
> pom
> > to deploy
> >
> > On Tue, Sep 16, 2008 at 8:14 PM, Yaakov Chaikin <
> yaakov.chaikin@gmail.com>wrote:
> >
> >> DO you know why, given my <repositories> setup, every time I ran, it
> >> downloads the following:
> >>
> >> Downloading:
> >>
> https://xxxxx/maven/org/codehaus/plexus/plexus-component-api/1.0-alpha-15/plexus-component-api-1.0-alpha-15.pom
> >> Downloading:
> >>
> https://xxxxx/maven/org/codehaus/plexus/plexus-component-api/1.0-alpha-15/plexus-component-api-1.0-alpha-15.pom
> >> Downloading:
> >>
> https://xxxxx/maven/org/codehaus/plexus/plexus-container-default/1.0-alpha-15/plexus-container-default-1.0-alpha-15.pom
> >> Downloading:
> >>
> https://xxxxx/maven/org/codehaus/plexus/plexus-container-default/1.0-alpha-15/plexus-container-default-1.0-alpha-15.pom
> >>
> >> How do I disable downloading this every time?
> >>
> >> Thanks,
> >> Yaakov.
> >>
> >> On Tue, Sep 16, 2008 at 2:24 PM, Stephen Connolly
> >> <st...@gmail.com> wrote:
> >> > The *key* thing to understand is that once Maven downloads foo-1.0.jar
> >> and
> >> > has it in its local repository, it will *never* download it again.
> >> >
> >> > This is why you should always keep the version as -SNAPSHOT and use
> the
> >> > release plugin (or roll your own scripts if you're crazy) to roll a
> >> release.
> >> >
> >> > The result of using the release plugin is that developers will never
> >> > _normally_ build a non-SNAPSHOT version, and each build of a
> non-SNAPSHOT
> >> > will get deployed to your maven repo... and they should only be being
> >> built
> >> > once to ensure that there is only one release of the artifact for that
> >> > version number.
> >> >
> >> > On Tue, Sep 16, 2008 at 7:21 PM, Stephen Connolly <
> >> > stephen.alan.connolly@gmail.com> wrote:
> >> >
> >> >> The update ppolicy for a remote repo will control how often maven
> looks
> >> for
> >> >> updates versions being available also...
> >> >>
> >> >> but the thing is this is only is Maven thinks it could use a newer
> >> >> version...
> >> >>
> >> >> so if your dependency is like
> >> >>
> >> >> <version>1.0</version>
> >> >>
> >> >> then that's a "no fixed version, but I'd suggest to use 1.0" and as
> long
> >> as
> >> >> Maven has a 1.0 downloaded, there's no need to check.
> >> >>
> >> >> Similarly if you have
> >> >>
> >> >> <version>[1.0]</version>
> >> >>
> >> >> However, if you have
> >> >>
> >> >> <version>[1.0,2.0-!)</version>
> >> >>
> >> >> Then Maven _can_ use a newer one if available. If no other project
> is
> >> >> forcing or strongly suggesting a specific version within the range,
> then
> >> >> Maven will use the update policy to decide how often to check for
> other
> >> >> versions that match the range(s) that apply for the version.
> >> >>
> >> >> At least that's my understanding (and results of some quick
> experiments)
> >> >>
> >> >> -Stephen
> >> >>
> >> >>
> >> >> On Tue, Sep 16, 2008 at 7:00 PM, Yaakov Chaikin <
> >> yaakov.chaikin@gmail.com>wrote:
> >> >>
> >> >>> Hmm... Is that REALLY true? The documentation for the 'updatePolicy'
> >> >>> certainly seems to disagree since it exists for both <snapshots> and
> >> >>> <releases>:
> >> >>> "updatePolicy: This element specifies how often updates should
> attempt
> >> >>> to occur. Maven will compare the local POM's timestamp (stored in a
> >> >>> repository's maven-metadata file) to the remote. The choices are:
> >> >>> always, daily (default), interval:X (where X is an integer in
> minutes)
> >> >>> or never."
> >> >>>
> >> >>> The documentation for mvn --help also says this for '-U':
> >> >>> -U,--update-snapshots Forces a check for updated releases
> and
> >> >>> snapshots on remote repositories
> >> >>>
> >> >>> So, how do you explain these then? What do they do?
> >> >>>
> >> >>>
> >> >>> On Tue, Sep 16, 2008 at 1:53 PM, Wayne Fay <wa...@gmail.com>
> wrote:
> >> >>> > Maven NEVER updates jars that have a non-snapshot version
> associated
> >> >>> with them.
> >> >>> >
> >> >>> > If you are "updating" jars then they MUST be called a.b.c-SNAPSHOT
> >> for
> >> >>> > Maven to notice the changes.
> >> >>> >
> >> >>> > Wayne
> >> >>> >
> >> >>> > On Tue, Sep 16, 2008 at 10:47 AM, Yaakov Chaikin
> >> >>> > <ya...@gmail.com> wrote:
> >> >>> >> Hi,
> >> >>> >>
> >> >>> >> I am using Maven 2.0.8.
> >> >>> >>
> >> >>> >> I have a custom remote maven repo with some JARs imported there.
> I
> >> >>> >> recently updated one of the JARs there, but noticed that when I
> >> built
> >> >>> >> on the client, no update was pulled from the remote repo and my
> >> local
> >> >>> >> repo still has the old one. Only after I erased the actual JAR
> from
> >> >>> >> the local repo, did it pull the file from the remote repo.
> >> >>> >>
> >> >>> >> I checked and all the files in the directory under (version) 1.0
> of
> >> >>> >> that JAR file have new timestamps, so it's definitely new.
> >> >>> >>
> >> >>> >> I then tried to force by doing this:
> >> >>> >> mvn -U clean install
> >> >>> >>
> >> >>> >> That didn't bring in the new JAR.
> >> >>> >>
> >> >>> >> I then tried to edit the update policy and explicitely says
> >> "always":
> >> >>> >> <repositories>
> >> >>> >> <repository>
> >> >>> >> <id>central</id>
> >> >>> >> <name>FES Unclass Maven Repository</name>
> >> >>> >> <url>https://xxx</url>
> >> >>> >> <snapshots>
> >> >>> >>
> <updatePolicy>always</updatePolicy>
> >> >>> >> <enabled>true</enabled>
> >> >>> >> </snapshots>
> >> >>> >> <releases>
> >> >>> >> <enabled>true</enabled>
> >> >>> >>
> <updatePolicy>always</updatePolicy>
> >> >>> >> </releases>
> >> >>> >> </repository>
> >> >>> >> </repositories>
> >> >>> >> <pluginRepositories>
> >> >>> >> <pluginRepository>
> >> >>> >> <id>central</id>
> >> >>> >> <name>FES Unclass Maven Repository</name>
> >> >>> >> <url>https://xxx</url>
> >> >>> >> </pluginRepository>
> >> >>> >> </pluginRepositories>
> >> >>> >>
> >> >>> >> However, that didn't work either.
> >> >>> >>
> >> >>> >> Am I doing something wrong here?
> >> >>> >>
> >> >>> >> Thanks,
> >> >>> >> Yaakov.
> >> >>> >>
> >> >>> >>
> >> ---------------------------------------------------------------------
> >> >>> >> 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
> >> >>>
> >> >>>
> >> >>
> >> >
> >>
> >> ---------------------------------------------------------------------
> >> 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: Jar not updating from remote repo
Posted by Yaakov Chaikin <ya...@gmail.com>.
Well, I ran the mvn clean install, etc. using the DSMP proxy server
and then moved what it cached into the repository. I didn't actually
manually deploy anything except those JARs from a parallel project.
How do I deploy those poms?
Thanks,
Yaakov.
On Tue, Sep 16, 2008 at 6:59 PM, Stephen Connolly
<st...@gmail.com> wrote:
> It's looking for the poms...
>
> did you deploy poms?
>
> BTW when doing a deploy you can generate basic poms if you don't have a pom
> to deploy
>
> On Tue, Sep 16, 2008 at 8:14 PM, Yaakov Chaikin <ya...@gmail.com>wrote:
>
>> DO you know why, given my <repositories> setup, every time I ran, it
>> downloads the following:
>>
>> Downloading:
>> https://xxxxx/maven/org/codehaus/plexus/plexus-component-api/1.0-alpha-15/plexus-component-api-1.0-alpha-15.pom
>> Downloading:
>> https://xxxxx/maven/org/codehaus/plexus/plexus-component-api/1.0-alpha-15/plexus-component-api-1.0-alpha-15.pom
>> Downloading:
>> https://xxxxx/maven/org/codehaus/plexus/plexus-container-default/1.0-alpha-15/plexus-container-default-1.0-alpha-15.pom
>> Downloading:
>> https://xxxxx/maven/org/codehaus/plexus/plexus-container-default/1.0-alpha-15/plexus-container-default-1.0-alpha-15.pom
>>
>> How do I disable downloading this every time?
>>
>> Thanks,
>> Yaakov.
>>
>> On Tue, Sep 16, 2008 at 2:24 PM, Stephen Connolly
>> <st...@gmail.com> wrote:
>> > The *key* thing to understand is that once Maven downloads foo-1.0.jar
>> and
>> > has it in its local repository, it will *never* download it again.
>> >
>> > This is why you should always keep the version as -SNAPSHOT and use the
>> > release plugin (or roll your own scripts if you're crazy) to roll a
>> release.
>> >
>> > The result of using the release plugin is that developers will never
>> > _normally_ build a non-SNAPSHOT version, and each build of a non-SNAPSHOT
>> > will get deployed to your maven repo... and they should only be being
>> built
>> > once to ensure that there is only one release of the artifact for that
>> > version number.
>> >
>> > On Tue, Sep 16, 2008 at 7:21 PM, Stephen Connolly <
>> > stephen.alan.connolly@gmail.com> wrote:
>> >
>> >> The update ppolicy for a remote repo will control how often maven looks
>> for
>> >> updates versions being available also...
>> >>
>> >> but the thing is this is only is Maven thinks it could use a newer
>> >> version...
>> >>
>> >> so if your dependency is like
>> >>
>> >> <version>1.0</version>
>> >>
>> >> then that's a "no fixed version, but I'd suggest to use 1.0" and as long
>> as
>> >> Maven has a 1.0 downloaded, there's no need to check.
>> >>
>> >> Similarly if you have
>> >>
>> >> <version>[1.0]</version>
>> >>
>> >> However, if you have
>> >>
>> >> <version>[1.0,2.0-!)</version>
>> >>
>> >> Then Maven _can_ use a newer one if available. If no other project is
>> >> forcing or strongly suggesting a specific version within the range, then
>> >> Maven will use the update policy to decide how often to check for other
>> >> versions that match the range(s) that apply for the version.
>> >>
>> >> At least that's my understanding (and results of some quick experiments)
>> >>
>> >> -Stephen
>> >>
>> >>
>> >> On Tue, Sep 16, 2008 at 7:00 PM, Yaakov Chaikin <
>> yaakov.chaikin@gmail.com>wrote:
>> >>
>> >>> Hmm... Is that REALLY true? The documentation for the 'updatePolicy'
>> >>> certainly seems to disagree since it exists for both <snapshots> and
>> >>> <releases>:
>> >>> "updatePolicy: This element specifies how often updates should attempt
>> >>> to occur. Maven will compare the local POM's timestamp (stored in a
>> >>> repository's maven-metadata file) to the remote. The choices are:
>> >>> always, daily (default), interval:X (where X is an integer in minutes)
>> >>> or never."
>> >>>
>> >>> The documentation for mvn --help also says this for '-U':
>> >>> -U,--update-snapshots Forces a check for updated releases and
>> >>> snapshots on remote repositories
>> >>>
>> >>> So, how do you explain these then? What do they do?
>> >>>
>> >>>
>> >>> On Tue, Sep 16, 2008 at 1:53 PM, Wayne Fay <wa...@gmail.com> wrote:
>> >>> > Maven NEVER updates jars that have a non-snapshot version associated
>> >>> with them.
>> >>> >
>> >>> > If you are "updating" jars then they MUST be called a.b.c-SNAPSHOT
>> for
>> >>> > Maven to notice the changes.
>> >>> >
>> >>> > Wayne
>> >>> >
>> >>> > On Tue, Sep 16, 2008 at 10:47 AM, Yaakov Chaikin
>> >>> > <ya...@gmail.com> wrote:
>> >>> >> Hi,
>> >>> >>
>> >>> >> I am using Maven 2.0.8.
>> >>> >>
>> >>> >> I have a custom remote maven repo with some JARs imported there. I
>> >>> >> recently updated one of the JARs there, but noticed that when I
>> built
>> >>> >> on the client, no update was pulled from the remote repo and my
>> local
>> >>> >> repo still has the old one. Only after I erased the actual JAR from
>> >>> >> the local repo, did it pull the file from the remote repo.
>> >>> >>
>> >>> >> I checked and all the files in the directory under (version) 1.0 of
>> >>> >> that JAR file have new timestamps, so it's definitely new.
>> >>> >>
>> >>> >> I then tried to force by doing this:
>> >>> >> mvn -U clean install
>> >>> >>
>> >>> >> That didn't bring in the new JAR.
>> >>> >>
>> >>> >> I then tried to edit the update policy and explicitely says
>> "always":
>> >>> >> <repositories>
>> >>> >> <repository>
>> >>> >> <id>central</id>
>> >>> >> <name>FES Unclass Maven Repository</name>
>> >>> >> <url>https://xxx</url>
>> >>> >> <snapshots>
>> >>> >> <updatePolicy>always</updatePolicy>
>> >>> >> <enabled>true</enabled>
>> >>> >> </snapshots>
>> >>> >> <releases>
>> >>> >> <enabled>true</enabled>
>> >>> >> <updatePolicy>always</updatePolicy>
>> >>> >> </releases>
>> >>> >> </repository>
>> >>> >> </repositories>
>> >>> >> <pluginRepositories>
>> >>> >> <pluginRepository>
>> >>> >> <id>central</id>
>> >>> >> <name>FES Unclass Maven Repository</name>
>> >>> >> <url>https://xxx</url>
>> >>> >> </pluginRepository>
>> >>> >> </pluginRepositories>
>> >>> >>
>> >>> >> However, that didn't work either.
>> >>> >>
>> >>> >> Am I doing something wrong here?
>> >>> >>
>> >>> >> Thanks,
>> >>> >> Yaakov.
>> >>> >>
>> >>> >>
>> ---------------------------------------------------------------------
>> >>> >> 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
>> >>>
>> >>>
>> >>
>> >
>>
>> ---------------------------------------------------------------------
>> 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: Jar not updating from remote repo
Posted by Stephen Connolly <st...@gmail.com>.
It's looking for the poms...
did you deploy poms?
BTW when doing a deploy you can generate basic poms if you don't have a pom
to deploy
On Tue, Sep 16, 2008 at 8:14 PM, Yaakov Chaikin <ya...@gmail.com>wrote:
> DO you know why, given my <repositories> setup, every time I ran, it
> downloads the following:
>
> Downloading:
> https://xxxxx/maven/org/codehaus/plexus/plexus-component-api/1.0-alpha-15/plexus-component-api-1.0-alpha-15.pom
> Downloading:
> https://xxxxx/maven/org/codehaus/plexus/plexus-component-api/1.0-alpha-15/plexus-component-api-1.0-alpha-15.pom
> Downloading:
> https://xxxxx/maven/org/codehaus/plexus/plexus-container-default/1.0-alpha-15/plexus-container-default-1.0-alpha-15.pom
> Downloading:
> https://xxxxx/maven/org/codehaus/plexus/plexus-container-default/1.0-alpha-15/plexus-container-default-1.0-alpha-15.pom
>
> How do I disable downloading this every time?
>
> Thanks,
> Yaakov.
>
> On Tue, Sep 16, 2008 at 2:24 PM, Stephen Connolly
> <st...@gmail.com> wrote:
> > The *key* thing to understand is that once Maven downloads foo-1.0.jar
> and
> > has it in its local repository, it will *never* download it again.
> >
> > This is why you should always keep the version as -SNAPSHOT and use the
> > release plugin (or roll your own scripts if you're crazy) to roll a
> release.
> >
> > The result of using the release plugin is that developers will never
> > _normally_ build a non-SNAPSHOT version, and each build of a non-SNAPSHOT
> > will get deployed to your maven repo... and they should only be being
> built
> > once to ensure that there is only one release of the artifact for that
> > version number.
> >
> > On Tue, Sep 16, 2008 at 7:21 PM, Stephen Connolly <
> > stephen.alan.connolly@gmail.com> wrote:
> >
> >> The update ppolicy for a remote repo will control how often maven looks
> for
> >> updates versions being available also...
> >>
> >> but the thing is this is only is Maven thinks it could use a newer
> >> version...
> >>
> >> so if your dependency is like
> >>
> >> <version>1.0</version>
> >>
> >> then that's a "no fixed version, but I'd suggest to use 1.0" and as long
> as
> >> Maven has a 1.0 downloaded, there's no need to check.
> >>
> >> Similarly if you have
> >>
> >> <version>[1.0]</version>
> >>
> >> However, if you have
> >>
> >> <version>[1.0,2.0-!)</version>
> >>
> >> Then Maven _can_ use a newer one if available. If no other project is
> >> forcing or strongly suggesting a specific version within the range, then
> >> Maven will use the update policy to decide how often to check for other
> >> versions that match the range(s) that apply for the version.
> >>
> >> At least that's my understanding (and results of some quick experiments)
> >>
> >> -Stephen
> >>
> >>
> >> On Tue, Sep 16, 2008 at 7:00 PM, Yaakov Chaikin <
> yaakov.chaikin@gmail.com>wrote:
> >>
> >>> Hmm... Is that REALLY true? The documentation for the 'updatePolicy'
> >>> certainly seems to disagree since it exists for both <snapshots> and
> >>> <releases>:
> >>> "updatePolicy: This element specifies how often updates should attempt
> >>> to occur. Maven will compare the local POM's timestamp (stored in a
> >>> repository's maven-metadata file) to the remote. The choices are:
> >>> always, daily (default), interval:X (where X is an integer in minutes)
> >>> or never."
> >>>
> >>> The documentation for mvn --help also says this for '-U':
> >>> -U,--update-snapshots Forces a check for updated releases and
> >>> snapshots on remote repositories
> >>>
> >>> So, how do you explain these then? What do they do?
> >>>
> >>>
> >>> On Tue, Sep 16, 2008 at 1:53 PM, Wayne Fay <wa...@gmail.com> wrote:
> >>> > Maven NEVER updates jars that have a non-snapshot version associated
> >>> with them.
> >>> >
> >>> > If you are "updating" jars then they MUST be called a.b.c-SNAPSHOT
> for
> >>> > Maven to notice the changes.
> >>> >
> >>> > Wayne
> >>> >
> >>> > On Tue, Sep 16, 2008 at 10:47 AM, Yaakov Chaikin
> >>> > <ya...@gmail.com> wrote:
> >>> >> Hi,
> >>> >>
> >>> >> I am using Maven 2.0.8.
> >>> >>
> >>> >> I have a custom remote maven repo with some JARs imported there. I
> >>> >> recently updated one of the JARs there, but noticed that when I
> built
> >>> >> on the client, no update was pulled from the remote repo and my
> local
> >>> >> repo still has the old one. Only after I erased the actual JAR from
> >>> >> the local repo, did it pull the file from the remote repo.
> >>> >>
> >>> >> I checked and all the files in the directory under (version) 1.0 of
> >>> >> that JAR file have new timestamps, so it's definitely new.
> >>> >>
> >>> >> I then tried to force by doing this:
> >>> >> mvn -U clean install
> >>> >>
> >>> >> That didn't bring in the new JAR.
> >>> >>
> >>> >> I then tried to edit the update policy and explicitely says
> "always":
> >>> >> <repositories>
> >>> >> <repository>
> >>> >> <id>central</id>
> >>> >> <name>FES Unclass Maven Repository</name>
> >>> >> <url>https://xxx</url>
> >>> >> <snapshots>
> >>> >> <updatePolicy>always</updatePolicy>
> >>> >> <enabled>true</enabled>
> >>> >> </snapshots>
> >>> >> <releases>
> >>> >> <enabled>true</enabled>
> >>> >> <updatePolicy>always</updatePolicy>
> >>> >> </releases>
> >>> >> </repository>
> >>> >> </repositories>
> >>> >> <pluginRepositories>
> >>> >> <pluginRepository>
> >>> >> <id>central</id>
> >>> >> <name>FES Unclass Maven Repository</name>
> >>> >> <url>https://xxx</url>
> >>> >> </pluginRepository>
> >>> >> </pluginRepositories>
> >>> >>
> >>> >> However, that didn't work either.
> >>> >>
> >>> >> Am I doing something wrong here?
> >>> >>
> >>> >> Thanks,
> >>> >> Yaakov.
> >>> >>
> >>> >>
> ---------------------------------------------------------------------
> >>> >> 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
> >>>
> >>>
> >>
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: Jar not updating from remote repo
Posted by Lee Meador <le...@leemeador.com>.
The one way to force Maven to reload something into the local repo is to
delete the copy in the repo. There isn't much downside to deleting too much
from the local repo EXCEPT you don't want to delete anything that you
imported manually to your local repo.
So, on my Windows machine I go to c:\My Documents\<my login>\.m2\repo and
follow down some part of the path to the files that I want to get updated.
Delete those files or even those whole folders.
The next build will reload. (Its not elegant but it works.)
-- Lee
On Tue, Sep 16, 2008 at 2:14 PM, Yaakov Chaikin <ya...@gmail.com>wrote:
> DO you know why, given my <repositories> setup, every time I ran, it
> downloads the following:
>
> Downloading:
> https://xxxxx/maven/org/codehaus/plexus/plexus-component-api/1.0-alpha-15/plexus-component-api-1.0-alpha-15.pom
> Downloading:
> https://xxxxx/maven/org/codehaus/plexus/plexus-component-api/1.0-alpha-15/plexus-component-api-1.0-alpha-15.pom
> Downloading:
> https://xxxxx/maven/org/codehaus/plexus/plexus-container-default/1.0-alpha-15/plexus-container-default-1.0-alpha-15.pom
> Downloading:
> https://xxxxx/maven/org/codehaus/plexus/plexus-container-default/1.0-alpha-15/plexus-container-default-1.0-alpha-15.pom
>
> How do I disable downloading this every time?
>
> Thanks,
> Yaakov.
>
> On Tue, Sep 16, 2008 at 2:24 PM, Stephen Connolly
> <st...@gmail.com> wrote:
> > The *key* thing to understand is that once Maven downloads foo-1.0.jar
> and
> > has it in its local repository, it will *never* download it again.
> >
> > This is why you should always keep the version as -SNAPSHOT and use the
> > release plugin (or roll your own scripts if you're crazy) to roll a
> release.
> >
> > The result of using the release plugin is that developers will never
> > _normally_ build a non-SNAPSHOT version, and each build of a non-SNAPSHOT
> > will get deployed to your maven repo... and they should only be being
> built
> > once to ensure that there is only one release of the artifact for that
> > version number.
> >
> > On Tue, Sep 16, 2008 at 7:21 PM, Stephen Connolly <
> > stephen.alan.connolly@gmail.com> wrote:
> >
> >> The update ppolicy for a remote repo will control how often maven looks
> for
> >> updates versions being available also...
> >>
> >> but the thing is this is only is Maven thinks it could use a newer
> >> version...
> >>
> >> so if your dependency is like
> >>
> >> <version>1.0</version>
> >>
> >> then that's a "no fixed version, but I'd suggest to use 1.0" and as long
> as
> >> Maven has a 1.0 downloaded, there's no need to check.
> >>
> >> Similarly if you have
> >>
> >> <version>[1.0]</version>
> >>
> >> However, if you have
> >>
> >> <version>[1.0,2.0-!)</version>
> >>
> >> Then Maven _can_ use a newer one if available. If no other project is
> >> forcing or strongly suggesting a specific version within the range, then
> >> Maven will use the update policy to decide how often to check for other
> >> versions that match the range(s) that apply for the version.
> >>
> >> At least that's my understanding (and results of some quick experiments)
> >>
> >> -Stephen
> >>
> >>
> >> On Tue, Sep 16, 2008 at 7:00 PM, Yaakov Chaikin <
> yaakov.chaikin@gmail.com>wrote:
> >>
> >>> Hmm... Is that REALLY true? The documentation for the 'updatePolicy'
> >>> certainly seems to disagree since it exists for both <snapshots> and
> >>> <releases>:
> >>> "updatePolicy: This element specifies how often updates should attempt
> >>> to occur. Maven will compare the local POM's timestamp (stored in a
> >>> repository's maven-metadata file) to the remote. The choices are:
> >>> always, daily (default), interval:X (where X is an integer in minutes)
> >>> or never."
> >>>
> >>> The documentation for mvn --help also says this for '-U':
> >>> -U,--update-snapshots Forces a check for updated releases and
> >>> snapshots on remote repositories
> >>>
> >>> So, how do you explain these then? What do they do?
> >>>
> >>>
> >>> On Tue, Sep 16, 2008 at 1:53 PM, Wayne Fay <wa...@gmail.com> wrote:
> >>> > Maven NEVER updates jars that have a non-snapshot version associated
> >>> with them.
> >>> >
> >>> > If you are "updating" jars then they MUST be called a.b.c-SNAPSHOT
> for
> >>> > Maven to notice the changes.
> >>> >
> >>> > Wayne
> >>> >
> >>> > On Tue, Sep 16, 2008 at 10:47 AM, Yaakov Chaikin
> >>> > <ya...@gmail.com> wrote:
> >>> >> Hi,
> >>> >>
> >>> >> I am using Maven 2.0.8.
> >>> >>
> >>> >> I have a custom remote maven repo with some JARs imported there. I
> >>> >> recently updated one of the JARs there, but noticed that when I
> built
> >>> >> on the client, no update was pulled from the remote repo and my
> local
> >>> >> repo still has the old one. Only after I erased the actual JAR from
> >>> >> the local repo, did it pull the file from the remote repo.
> >>> >>
> >>> >> I checked and all the files in the directory under (version) 1.0 of
> >>> >> that JAR file have new timestamps, so it's definitely new.
> >>> >>
> >>> >> I then tried to force by doing this:
> >>> >> mvn -U clean install
> >>> >>
> >>> >> That didn't bring in the new JAR.
> >>> >>
> >>> >> I then tried to edit the update policy and explicitely says
> "always":
> >>> >> <repositories>
> >>> >> <repository>
> >>> >> <id>central</id>
> >>> >> <name>FES Unclass Maven Repository</name>
> >>> >> <url>https://xxx</url>
> >>> >> <snapshots>
> >>> >> <updatePolicy>always</updatePolicy>
> >>> >> <enabled>true</enabled>
> >>> >> </snapshots>
> >>> >> <releases>
> >>> >> <enabled>true</enabled>
> >>> >> <updatePolicy>always</updatePolicy>
> >>> >> </releases>
> >>> >> </repository>
> >>> >> </repositories>
> >>> >> <pluginRepositories>
> >>> >> <pluginRepository>
> >>> >> <id>central</id>
> >>> >> <name>FES Unclass Maven Repository</name>
> >>> >> <url>https://xxx</url>
> >>> >> </pluginRepository>
> >>> >> </pluginRepositories>
> >>> >>
> >>> >> However, that didn't work either.
> >>> >>
> >>> >> Am I doing something wrong here?
> >>> >>
> >>> >> Thanks,
> >>> >> Yaakov.
> >>> >>
> >>> >>
> ---------------------------------------------------------------------
> >>> >> 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
> >>>
> >>>
> >>
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
--
-- Lee Meador
Sent from gmail. My real email address is lee AT leemeador.com
Re: Jar not updating from remote repo
Posted by Yaakov Chaikin <ya...@gmail.com>.
DO you know why, given my <repositories> setup, every time I ran, it
downloads the following:
Downloading: https://xxxxx/maven/org/codehaus/plexus/plexus-component-api/1.0-alpha-15/plexus-component-api-1.0-alpha-15.pom
Downloading: https://xxxxx/maven/org/codehaus/plexus/plexus-component-api/1.0-alpha-15/plexus-component-api-1.0-alpha-15.pom
Downloading: https://xxxxx/maven/org/codehaus/plexus/plexus-container-default/1.0-alpha-15/plexus-container-default-1.0-alpha-15.pom
Downloading: https://xxxxx/maven/org/codehaus/plexus/plexus-container-default/1.0-alpha-15/plexus-container-default-1.0-alpha-15.pom
How do I disable downloading this every time?
Thanks,
Yaakov.
On Tue, Sep 16, 2008 at 2:24 PM, Stephen Connolly
<st...@gmail.com> wrote:
> The *key* thing to understand is that once Maven downloads foo-1.0.jar and
> has it in its local repository, it will *never* download it again.
>
> This is why you should always keep the version as -SNAPSHOT and use the
> release plugin (or roll your own scripts if you're crazy) to roll a release.
>
> The result of using the release plugin is that developers will never
> _normally_ build a non-SNAPSHOT version, and each build of a non-SNAPSHOT
> will get deployed to your maven repo... and they should only be being built
> once to ensure that there is only one release of the artifact for that
> version number.
>
> On Tue, Sep 16, 2008 at 7:21 PM, Stephen Connolly <
> stephen.alan.connolly@gmail.com> wrote:
>
>> The update ppolicy for a remote repo will control how often maven looks for
>> updates versions being available also...
>>
>> but the thing is this is only is Maven thinks it could use a newer
>> version...
>>
>> so if your dependency is like
>>
>> <version>1.0</version>
>>
>> then that's a "no fixed version, but I'd suggest to use 1.0" and as long as
>> Maven has a 1.0 downloaded, there's no need to check.
>>
>> Similarly if you have
>>
>> <version>[1.0]</version>
>>
>> However, if you have
>>
>> <version>[1.0,2.0-!)</version>
>>
>> Then Maven _can_ use a newer one if available. If no other project is
>> forcing or strongly suggesting a specific version within the range, then
>> Maven will use the update policy to decide how often to check for other
>> versions that match the range(s) that apply for the version.
>>
>> At least that's my understanding (and results of some quick experiments)
>>
>> -Stephen
>>
>>
>> On Tue, Sep 16, 2008 at 7:00 PM, Yaakov Chaikin <ya...@gmail.com>wrote:
>>
>>> Hmm... Is that REALLY true? The documentation for the 'updatePolicy'
>>> certainly seems to disagree since it exists for both <snapshots> and
>>> <releases>:
>>> "updatePolicy: This element specifies how often updates should attempt
>>> to occur. Maven will compare the local POM's timestamp (stored in a
>>> repository's maven-metadata file) to the remote. The choices are:
>>> always, daily (default), interval:X (where X is an integer in minutes)
>>> or never."
>>>
>>> The documentation for mvn --help also says this for '-U':
>>> -U,--update-snapshots Forces a check for updated releases and
>>> snapshots on remote repositories
>>>
>>> So, how do you explain these then? What do they do?
>>>
>>>
>>> On Tue, Sep 16, 2008 at 1:53 PM, Wayne Fay <wa...@gmail.com> wrote:
>>> > Maven NEVER updates jars that have a non-snapshot version associated
>>> with them.
>>> >
>>> > If you are "updating" jars then they MUST be called a.b.c-SNAPSHOT for
>>> > Maven to notice the changes.
>>> >
>>> > Wayne
>>> >
>>> > On Tue, Sep 16, 2008 at 10:47 AM, Yaakov Chaikin
>>> > <ya...@gmail.com> wrote:
>>> >> Hi,
>>> >>
>>> >> I am using Maven 2.0.8.
>>> >>
>>> >> I have a custom remote maven repo with some JARs imported there. I
>>> >> recently updated one of the JARs there, but noticed that when I built
>>> >> on the client, no update was pulled from the remote repo and my local
>>> >> repo still has the old one. Only after I erased the actual JAR from
>>> >> the local repo, did it pull the file from the remote repo.
>>> >>
>>> >> I checked and all the files in the directory under (version) 1.0 of
>>> >> that JAR file have new timestamps, so it's definitely new.
>>> >>
>>> >> I then tried to force by doing this:
>>> >> mvn -U clean install
>>> >>
>>> >> That didn't bring in the new JAR.
>>> >>
>>> >> I then tried to edit the update policy and explicitely says "always":
>>> >> <repositories>
>>> >> <repository>
>>> >> <id>central</id>
>>> >> <name>FES Unclass Maven Repository</name>
>>> >> <url>https://xxx</url>
>>> >> <snapshots>
>>> >> <updatePolicy>always</updatePolicy>
>>> >> <enabled>true</enabled>
>>> >> </snapshots>
>>> >> <releases>
>>> >> <enabled>true</enabled>
>>> >> <updatePolicy>always</updatePolicy>
>>> >> </releases>
>>> >> </repository>
>>> >> </repositories>
>>> >> <pluginRepositories>
>>> >> <pluginRepository>
>>> >> <id>central</id>
>>> >> <name>FES Unclass Maven Repository</name>
>>> >> <url>https://xxx</url>
>>> >> </pluginRepository>
>>> >> </pluginRepositories>
>>> >>
>>> >> However, that didn't work either.
>>> >>
>>> >> Am I doing something wrong here?
>>> >>
>>> >> Thanks,
>>> >> Yaakov.
>>> >>
>>> >> ---------------------------------------------------------------------
>>> >> 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
>>>
>>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Jar not updating from remote repo
Posted by Stephen Connolly <st...@gmail.com>.
The *key* thing to understand is that once Maven downloads foo-1.0.jar and
has it in its local repository, it will *never* download it again.
This is why you should always keep the version as -SNAPSHOT and use the
release plugin (or roll your own scripts if you're crazy) to roll a release.
The result of using the release plugin is that developers will never
_normally_ build a non-SNAPSHOT version, and each build of a non-SNAPSHOT
will get deployed to your maven repo... and they should only be being built
once to ensure that there is only one release of the artifact for that
version number.
On Tue, Sep 16, 2008 at 7:21 PM, Stephen Connolly <
stephen.alan.connolly@gmail.com> wrote:
> The update ppolicy for a remote repo will control how often maven looks for
> updates versions being available also...
>
> but the thing is this is only is Maven thinks it could use a newer
> version...
>
> so if your dependency is like
>
> <version>1.0</version>
>
> then that's a "no fixed version, but I'd suggest to use 1.0" and as long as
> Maven has a 1.0 downloaded, there's no need to check.
>
> Similarly if you have
>
> <version>[1.0]</version>
>
> However, if you have
>
> <version>[1.0,2.0-!)</version>
>
> Then Maven _can_ use a newer one if available. If no other project is
> forcing or strongly suggesting a specific version within the range, then
> Maven will use the update policy to decide how often to check for other
> versions that match the range(s) that apply for the version.
>
> At least that's my understanding (and results of some quick experiments)
>
> -Stephen
>
>
> On Tue, Sep 16, 2008 at 7:00 PM, Yaakov Chaikin <ya...@gmail.com>wrote:
>
>> Hmm... Is that REALLY true? The documentation for the 'updatePolicy'
>> certainly seems to disagree since it exists for both <snapshots> and
>> <releases>:
>> "updatePolicy: This element specifies how often updates should attempt
>> to occur. Maven will compare the local POM's timestamp (stored in a
>> repository's maven-metadata file) to the remote. The choices are:
>> always, daily (default), interval:X (where X is an integer in minutes)
>> or never."
>>
>> The documentation for mvn --help also says this for '-U':
>> -U,--update-snapshots Forces a check for updated releases and
>> snapshots on remote repositories
>>
>> So, how do you explain these then? What do they do?
>>
>>
>> On Tue, Sep 16, 2008 at 1:53 PM, Wayne Fay <wa...@gmail.com> wrote:
>> > Maven NEVER updates jars that have a non-snapshot version associated
>> with them.
>> >
>> > If you are "updating" jars then they MUST be called a.b.c-SNAPSHOT for
>> > Maven to notice the changes.
>> >
>> > Wayne
>> >
>> > On Tue, Sep 16, 2008 at 10:47 AM, Yaakov Chaikin
>> > <ya...@gmail.com> wrote:
>> >> Hi,
>> >>
>> >> I am using Maven 2.0.8.
>> >>
>> >> I have a custom remote maven repo with some JARs imported there. I
>> >> recently updated one of the JARs there, but noticed that when I built
>> >> on the client, no update was pulled from the remote repo and my local
>> >> repo still has the old one. Only after I erased the actual JAR from
>> >> the local repo, did it pull the file from the remote repo.
>> >>
>> >> I checked and all the files in the directory under (version) 1.0 of
>> >> that JAR file have new timestamps, so it's definitely new.
>> >>
>> >> I then tried to force by doing this:
>> >> mvn -U clean install
>> >>
>> >> That didn't bring in the new JAR.
>> >>
>> >> I then tried to edit the update policy and explicitely says "always":
>> >> <repositories>
>> >> <repository>
>> >> <id>central</id>
>> >> <name>FES Unclass Maven Repository</name>
>> >> <url>https://xxx</url>
>> >> <snapshots>
>> >> <updatePolicy>always</updatePolicy>
>> >> <enabled>true</enabled>
>> >> </snapshots>
>> >> <releases>
>> >> <enabled>true</enabled>
>> >> <updatePolicy>always</updatePolicy>
>> >> </releases>
>> >> </repository>
>> >> </repositories>
>> >> <pluginRepositories>
>> >> <pluginRepository>
>> >> <id>central</id>
>> >> <name>FES Unclass Maven Repository</name>
>> >> <url>https://xxx</url>
>> >> </pluginRepository>
>> >> </pluginRepositories>
>> >>
>> >> However, that didn't work either.
>> >>
>> >> Am I doing something wrong here?
>> >>
>> >> Thanks,
>> >> Yaakov.
>> >>
>> >> ---------------------------------------------------------------------
>> >> 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: Jar not updating from remote repo
Posted by Stephen Connolly <st...@gmail.com>.
The update ppolicy for a remote repo will control how often maven looks for
updates versions being available also...
but the thing is this is only is Maven thinks it could use a newer
version...
so if your dependency is like
<version>1.0</version>
then that's a "no fixed version, but I'd suggest to use 1.0" and as long as
Maven has a 1.0 downloaded, there's no need to check.
Similarly if you have
<version>[1.0]</version>
However, if you have
<version>[1.0,2.0-!)</version>
Then Maven _can_ use a newer one if available. If no other project is
forcing or strongly suggesting a specific version within the range, then
Maven will use the update policy to decide how often to check for other
versions that match the range(s) that apply for the version.
At least that's my understanding (and results of some quick experiments)
-Stephen
On Tue, Sep 16, 2008 at 7:00 PM, Yaakov Chaikin <ya...@gmail.com>wrote:
> Hmm... Is that REALLY true? The documentation for the 'updatePolicy'
> certainly seems to disagree since it exists for both <snapshots> and
> <releases>:
> "updatePolicy: This element specifies how often updates should attempt
> to occur. Maven will compare the local POM's timestamp (stored in a
> repository's maven-metadata file) to the remote. The choices are:
> always, daily (default), interval:X (where X is an integer in minutes)
> or never."
>
> The documentation for mvn --help also says this for '-U':
> -U,--update-snapshots Forces a check for updated releases and
> snapshots on remote repositories
>
> So, how do you explain these then? What do they do?
>
>
> On Tue, Sep 16, 2008 at 1:53 PM, Wayne Fay <wa...@gmail.com> wrote:
> > Maven NEVER updates jars that have a non-snapshot version associated with
> them.
> >
> > If you are "updating" jars then they MUST be called a.b.c-SNAPSHOT for
> > Maven to notice the changes.
> >
> > Wayne
> >
> > On Tue, Sep 16, 2008 at 10:47 AM, Yaakov Chaikin
> > <ya...@gmail.com> wrote:
> >> Hi,
> >>
> >> I am using Maven 2.0.8.
> >>
> >> I have a custom remote maven repo with some JARs imported there. I
> >> recently updated one of the JARs there, but noticed that when I built
> >> on the client, no update was pulled from the remote repo and my local
> >> repo still has the old one. Only after I erased the actual JAR from
> >> the local repo, did it pull the file from the remote repo.
> >>
> >> I checked and all the files in the directory under (version) 1.0 of
> >> that JAR file have new timestamps, so it's definitely new.
> >>
> >> I then tried to force by doing this:
> >> mvn -U clean install
> >>
> >> That didn't bring in the new JAR.
> >>
> >> I then tried to edit the update policy and explicitely says "always":
> >> <repositories>
> >> <repository>
> >> <id>central</id>
> >> <name>FES Unclass Maven Repository</name>
> >> <url>https://xxx</url>
> >> <snapshots>
> >> <updatePolicy>always</updatePolicy>
> >> <enabled>true</enabled>
> >> </snapshots>
> >> <releases>
> >> <enabled>true</enabled>
> >> <updatePolicy>always</updatePolicy>
> >> </releases>
> >> </repository>
> >> </repositories>
> >> <pluginRepositories>
> >> <pluginRepository>
> >> <id>central</id>
> >> <name>FES Unclass Maven Repository</name>
> >> <url>https://xxx</url>
> >> </pluginRepository>
> >> </pluginRepositories>
> >>
> >> However, that didn't work either.
> >>
> >> Am I doing something wrong here?
> >>
> >> Thanks,
> >> Yaakov.
> >>
> >> ---------------------------------------------------------------------
> >> 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: Jar not updating from remote repo
Posted by Yaakov Chaikin <ya...@gmail.com>.
Hmm... Is that REALLY true? The documentation for the 'updatePolicy'
certainly seems to disagree since it exists for both <snapshots> and
<releases>:
"updatePolicy: This element specifies how often updates should attempt
to occur. Maven will compare the local POM's timestamp (stored in a
repository's maven-metadata file) to the remote. The choices are:
always, daily (default), interval:X (where X is an integer in minutes)
or never."
The documentation for mvn --help also says this for '-U':
-U,--update-snapshots Forces a check for updated releases and
snapshots on remote repositories
So, how do you explain these then? What do they do?
On Tue, Sep 16, 2008 at 1:53 PM, Wayne Fay <wa...@gmail.com> wrote:
> Maven NEVER updates jars that have a non-snapshot version associated with them.
>
> If you are "updating" jars then they MUST be called a.b.c-SNAPSHOT for
> Maven to notice the changes.
>
> Wayne
>
> On Tue, Sep 16, 2008 at 10:47 AM, Yaakov Chaikin
> <ya...@gmail.com> wrote:
>> Hi,
>>
>> I am using Maven 2.0.8.
>>
>> I have a custom remote maven repo with some JARs imported there. I
>> recently updated one of the JARs there, but noticed that when I built
>> on the client, no update was pulled from the remote repo and my local
>> repo still has the old one. Only after I erased the actual JAR from
>> the local repo, did it pull the file from the remote repo.
>>
>> I checked and all the files in the directory under (version) 1.0 of
>> that JAR file have new timestamps, so it's definitely new.
>>
>> I then tried to force by doing this:
>> mvn -U clean install
>>
>> That didn't bring in the new JAR.
>>
>> I then tried to edit the update policy and explicitely says "always":
>> <repositories>
>> <repository>
>> <id>central</id>
>> <name>FES Unclass Maven Repository</name>
>> <url>https://xxx</url>
>> <snapshots>
>> <updatePolicy>always</updatePolicy>
>> <enabled>true</enabled>
>> </snapshots>
>> <releases>
>> <enabled>true</enabled>
>> <updatePolicy>always</updatePolicy>
>> </releases>
>> </repository>
>> </repositories>
>> <pluginRepositories>
>> <pluginRepository>
>> <id>central</id>
>> <name>FES Unclass Maven Repository</name>
>> <url>https://xxx</url>
>> </pluginRepository>
>> </pluginRepositories>
>>
>> However, that didn't work either.
>>
>> Am I doing something wrong here?
>>
>> Thanks,
>> Yaakov.
>>
>> ---------------------------------------------------------------------
>> 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: Jar not updating from remote repo
Posted by Wayne Fay <wa...@gmail.com>.
Maven NEVER updates jars that have a non-snapshot version associated with them.
If you are "updating" jars then they MUST be called a.b.c-SNAPSHOT for
Maven to notice the changes.
Wayne
On Tue, Sep 16, 2008 at 10:47 AM, Yaakov Chaikin
<ya...@gmail.com> wrote:
> Hi,
>
> I am using Maven 2.0.8.
>
> I have a custom remote maven repo with some JARs imported there. I
> recently updated one of the JARs there, but noticed that when I built
> on the client, no update was pulled from the remote repo and my local
> repo still has the old one. Only after I erased the actual JAR from
> the local repo, did it pull the file from the remote repo.
>
> I checked and all the files in the directory under (version) 1.0 of
> that JAR file have new timestamps, so it's definitely new.
>
> I then tried to force by doing this:
> mvn -U clean install
>
> That didn't bring in the new JAR.
>
> I then tried to edit the update policy and explicitely says "always":
> <repositories>
> <repository>
> <id>central</id>
> <name>FES Unclass Maven Repository</name>
> <url>https://xxx</url>
> <snapshots>
> <updatePolicy>always</updatePolicy>
> <enabled>true</enabled>
> </snapshots>
> <releases>
> <enabled>true</enabled>
> <updatePolicy>always</updatePolicy>
> </releases>
> </repository>
> </repositories>
> <pluginRepositories>
> <pluginRepository>
> <id>central</id>
> <name>FES Unclass Maven Repository</name>
> <url>https://xxx</url>
> </pluginRepository>
> </pluginRepositories>
>
> However, that didn't work either.
>
> Am I doing something wrong here?
>
> Thanks,
> Yaakov.
>
> ---------------------------------------------------------------------
> 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