RE: Maven not taking the latest snapshot

2009-11-19 Thread Yury Kudryashov 
Thank you for your response, Brian. Unfortunately upgrading to 2.2.1 did not
help - today the problem was reproduced again.

After looking at the local repository on the build server we have noticed
that there is a snapshot version without the timestamp part in the name.
This version is much older than any of the latest snapshots and it seems
Maven takes exactly this old version.

Here's a dump of the local repository for one of the artifacts:

-rw-r--r-- 1 teamcity teamcity 1178041 2009-11-18 18:26
tobj-TRUNK-20091118.152629-342.jar 
-rw-r--r-- 1 teamcity teamcity 404 2009-11-18 18:26
tobj-TRUNK-20091118.152629-342.pom 
-rw-r--r-- 1 teamcity teamcity 1178195 2009-11-19 15:58
tobj-TRUNK-20091119.125835-343.jar 
-rw-r--r-- 1 teamcity teamcity 404 2009-11-19 15:58
tobj-TRUNK-20091119.125835-343.pom 
-rw-r--r-- 1 teamcity teamcity 1178195 2009-11-19 16:49
tobj-TRUNK-20091119.134950-344.jar 
-rw-r--r-- 1 teamcity teamcity 404 2009-11-19 16:50
tobj-TRUNK-20091119.134950-344.pom 
-rw-r--r-- 1 teamcity teamcity 1171191 2009-11-17 22:15
tobj-TRUNK-SNAPSHOT.jar 
-rw-r--r-- 1 teamcity teamcity 404 2009-11-17 22:15
tobj-TRUNK-SNAPSHOT.pom


As you may see there is a snapshot as of 11-19
(tobj-TRUNK-20091119.134950-344.jar) but the tobj-TRUNK-SNAPSHOT.jar is much
older. Should this "default" snapshot be updated automatically? It looks
like it should, but it does not. Can this be a configuration problem?

--
Yury Kudryashov


-Original Message-
From: Brian Fox [mailto:bri...@infinity.nu] 
Sent: Tuesday, November 17, 2009 8:36 PM
To: Maven Users List
Subject: Re: Maven not taking the latest snapshot

First, I would not use 2.1.0, use 2.0.10 or 2.2.1 instead. I'm fairly
certain that -U works properly in those versions. (2.1.0 shouldn't be
used at all, there were lots of issues there and we went right to
2.2.x)

On Tue, Nov 17, 2009 at 6:24 AM, Yury Kudryashov
 wrote:
> Hello,
>
> We have a set of products some of them depending on the others. We use
Maven
> to control dependencies and a continuous integration server to check
whether
> the changes are compatible.
>
> Continuous integration server first builds and deploys (to local
Nexus-based
> repository) snapshot versions of the parent component and then builds the
> dependent components (which take and use the parent SNAPSHOTS).
>
> The problem is that sometimes the continuous integration server caches a
> SNAPSHOT artifact in the local repository and then refuses to take newer
one
> from the remote repository. This leads to failing builds. This happens
> periodically, but not all the time. Deletion of the local repository on
the
> build server helps, but it is very inconvenient.
>
> Builds are run with the -U switch, but it seems to have no effect.
>
> We're using Maven 2.1.0 on Ubuntu.
>
> Please advise what can be the cause of the problem.
>
> Thank you.
>
>
> --
> Yury Kudryashov
>
>
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Maven not taking the latest snapshot

2009-11-17 Thread Yury Kudryashov 
Hello,

We have a set of products some of them depending on the others. We use Maven
to control dependencies and a continuous integration server to check whether
the changes are compatible. 

Continuous integration server first builds and deploys (to local Nexus-based
repository) snapshot versions of the parent component and then builds the
dependent components (which take and use the parent SNAPSHOTS). 

The problem is that sometimes the continuous integration server caches a
SNAPSHOT artifact in the local repository and then refuses to take newer one
from the remote repository. This leads to failing builds. This happens
periodically, but not all the time. Deletion of the local repository on the
build server helps, but it is very inconvenient.

Builds are run with the -U switch, but it seems to have no effect. 

We're using Maven 2.1.0 on Ubuntu.

Please advise what can be the cause of the problem.

Thank you.


--
Yury Kudryashov




-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Problem with maven-ant-tasks and https repository

2009-04-16 Thread Yury Kudryashov 

Hello,

I have an internal Maven repository that can only be accessed via HTTPS 
with authorization. I have setup everything in settings.xml and have the 
correct .jks file to access the repository.


My goal is to download dependencies from that repository.

Command "mvn -Djavax.net.ssl.trustStore=my.jks package" runs ok - 
dependency is retrieved. But if I try to use maven-ant-tasks and 
retrieve dependencies from ant - I got the "missing artifact" errors.


Here's part of my ant script that does the copying:











 



I run ant as:
ant -Djavax.net.ssl.trustStore=my.jks

And here's what I'm getting:

[artifact:dependencies] An error has occurred while processing the Maven 
artifact tasks.

[artifact:dependencies]  Diagnosis:
[artifact:dependencies]
[artifact:dependencies] Unable to resolve artifact: Missing:

I ran procmon and it seems that maven-ant-tasks doesn't attempt to use 
the .jks to access the repository over HTTPS.


Could you please help with this issue?

--
Yury Kudryashov

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org