AW: Snapshot feature broken in maven 2?
Hi!
I have seen you have filed a similar bug in jira
(http://jira.codehaus.org/browse/MNG-2289). I have added my description to that
bug and have voted to it.
Roger
-Ursprüngliche Nachricht-
Von: Jörg Schaible [mailto:[EMAIL PROTECTED]
Gesendet: Montag, 29. Mai 2006 18:28
An: Maven Developers List
Betreff: RE: Snapshot feature broken in maven 2?
[EMAIL PROTECTED] wrote on Monday, May 29, 2006 5:59 PM:
Hi!
We use maven 2 to build a large project consisting of
several modules.
Dependencies between modules are handled by the maven dependency
mechanism. During development, we want to use the SNAPSHOT feature
because we don't want to have an inflation of version numbers.
The problem: For me it looks like snapshots are never
updated in the
local repository.
There was already a thread some days ago (17.5.), where a
user had the same problems. It seems there is a problem and
you should raise an issue in JIRA.
- Jörg
To track this down, I have done the following test:
1. Deploy interface to our central repository 2. Compile client
(which depends on interface)
pom, jar and metadata are downloaded into local repository.
3. Increased version number and timestamp in the file
1.0-SNAPSHOT/maven-metadata.xml, recomputed checksums.
4. Run mvn -U clean compile on module client.
This results in the following log:
[INFO] Scanning for projects...
[INFO]
--
--
[INFO] Building Client for the great calculator
[INFO]task-segment: [clean, compile]
[INFO]
--
--
[INFO] artifact org.apache.maven.plugins:maven-clean-plugin:
checking for updates from central
[INFO] artifact org.apache.maven.plugins:maven-source-plugin:
checking for updates from central
[INFO] artifact
org.apache.maven.plugins:maven-surefire-plugin: checking
for updates
from central [INFO] [clean:clean] [INFO] Deleting directory
c:\example\client\target [INFO] Deleting directory
c:\example\client\target\classes [INFO] Deleting directory
c:\example\client\target\test-classes
[INFO] artifact org.apache.maven.plugins:maven-resources-plugin:
checking for updates from central [INFO] artifact
org.apache.maven.plugins:maven-compiler-plugin: checking
for updates
from central [INFO] [source-download:download-sources {execution:
default}]
- [INFO] snapshot
de.sdm.calculator:interface:1.0-SNAPSHOT: checking for updates from
central --
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources. [INFO]
snapshot de.sdm.calculator:calculator-all:1.0-SNAPSHOT:
checking for
updates from central [INFO] [compiler:compile] Compiling 1
source file
to c:\example\client\target\classes [INFO]
--
--
[INFO] BUILD SUCCESSFUL
As you can see in the marked line, the check for updates is done.
Looking into ~/.m2/repository I can see even the new
maven-metadata-central.xml (new timestamp, new content),
but the jar
is NOT updated from the server.
Is this intendented behaviour?
I can solve the problem by setting
uniqueVersiontrue/uniqueVersion master pom of the project, but
this clobberes the local repositories of all users and the central
repository with lots of old versions.
Your comments?
Regards
Roger
-
To unsubscribe, e-mail: [EMAIL PROTECTED] For
additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED] For
additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Snapshot feature broken in maven 2?
Hi!
We use maven 2 to build a large project consisting of several modules.
Dependencies between modules are handled by the maven dependency mechanism.
During development, we want to use the SNAPSHOT feature because we don't want
to have an inflation of version numbers.
The problem: For me it looks like snapshots are never updated in the local
repository.
To track this down, I have done the following test:
1. Deploy interface to our central repository
2. Compile client (which depends on interface)
pom, jar and metadata are downloaded into local repository.
3. Increased version number and timestamp in the file
1.0-SNAPSHOT/maven-metadata.xml, recomputed checksums.
4. Run mvn -U clean compile on module client.
This results in the following log:
[INFO] Scanning for projects...
[INFO]
[INFO] Building Client for the great calculator
[INFO]task-segment: [clean, compile]
[INFO]
[INFO] artifact org.apache.maven.plugins:maven-clean-plugin: checking for
updates from central
[INFO] artifact org.apache.maven.plugins:maven-source-plugin: checking for
updates from central
[INFO] artifact org.apache.maven.plugins:maven-surefire-plugin: checking for
updates from central
[INFO] [clean:clean]
[INFO] Deleting directory c:\example\client\target
[INFO] Deleting directory c:\example\client\target\classes
[INFO] Deleting directory c:\example\client\target\test-classes
[INFO] artifact org.apache.maven.plugins:maven-resources-plugin: checking for
updates from central
[INFO] artifact org.apache.maven.plugins:maven-compiler-plugin: checking for
updates from central
[INFO] [source-download:download-sources {execution: default}]
- [INFO] snapshot de.sdm.calculator:interface:1.0-SNAPSHOT: checking for
updates from central --
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] snapshot de.sdm.calculator:calculator-all:1.0-SNAPSHOT: checking for
updates from central
[INFO] [compiler:compile]
Compiling 1 source file to c:\example\client\target\classes
[INFO]
[INFO] BUILD SUCCESSFUL
As you can see in the marked line, the check for updates is done. Looking into
~/.m2/repository I can see even the new maven-metadata-central.xml (new
timestamp, new content), but the jar is NOT updated from the server.
Is this intendented behaviour?
I can solve the problem by setting uniqueVersiontrue/uniqueVersion master
pom of the project, but this clobberes the local repositories of all users and
the central repository with lots of old versions.
Your comments?
Regards
Roger
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: Snapshot feature broken in maven 2?
[EMAIL PROTECTED] wrote on Monday, May 29, 2006 5:59 PM:
Hi!
We use maven 2 to build a large project consisting of several
modules. Dependencies between modules are handled by the
maven dependency mechanism. During development, we want to
use the SNAPSHOT feature because we don't want to have an inflation
of version numbers.
The problem: For me it looks like snapshots are never updated in the
local repository.
There was already a thread some days ago (17.5.), where a user had the same
problems. It seems there is a problem and you should raise an issue in JIRA.
- Jörg
To track this down, I have done the following test:
1. Deploy interface to our central repository
2. Compile client (which depends on interface)
pom, jar and metadata are downloaded into local repository.
3. Increased version number and timestamp in the file
1.0-SNAPSHOT/maven-metadata.xml, recomputed checksums.
4. Run mvn -U clean compile on module client.
This results in the following log:
[INFO] Scanning for projects...
[INFO]
--
--
[INFO] Building Client for the great calculator
[INFO]task-segment: [clean, compile]
[INFO]
--
--
[INFO] artifact org.apache.maven.plugins:maven-clean-plugin:
checking for updates from central
[INFO] artifact org.apache.maven.plugins:maven-source-plugin:
checking for updates from central
[INFO] artifact
org.apache.maven.plugins:maven-surefire-plugin: checking for updates
from central [INFO] [clean:clean]
[INFO] Deleting directory c:\example\client\target
[INFO] Deleting directory c:\example\client\target\classes
[INFO] Deleting directory c:\example\client\target\test-classes
[INFO] artifact org.apache.maven.plugins:maven-resources-plugin:
checking for updates from central [INFO] artifact
org.apache.maven.plugins:maven-compiler-plugin: checking for updates
from central [INFO] [source-download:download-sources {execution:
default}]
- [INFO] snapshot
de.sdm.calculator:interface:1.0-SNAPSHOT: checking for
updates from central --
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources. [INFO]
snapshot de.sdm.calculator:calculator-all:1.0-SNAPSHOT: checking for
updates from central [INFO] [compiler:compile]
Compiling 1 source file to c:\example\client\target\classes [INFO]
--
--
[INFO] BUILD SUCCESSFUL
As you can see in the marked line, the check for updates is
done. Looking into ~/.m2/repository I can see even the new
maven-metadata-central.xml (new timestamp, new content), but
the jar is NOT updated from the server.
Is this intendented behaviour?
I can solve the problem by setting
uniqueVersiontrue/uniqueVersion master pom of the
project, but this clobberes the local repositories of all
users and the central repository with lots of old versions.
Your comments?
Regards
Roger
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
