[#MAVEN-1660] DependencyVerifier class doesn't resolve an snapshot artifact after attaining a first goal.

Maven 1

DependencyVerifier class doesn't resolve an snapshot artifact after attaining a first goal.

Created: 10/Aug/05 03:51 PM Updated: 11/Mar/07 02:50 PM

Component/s:

core

Affects Version/s:

1.1-beta-1

Fix Version/s:

None

Time Tracking:

Not Specified

Description

« Hide

Since revision 179556 of src/java/org/apache/maven/verifier/DependencyVerifier.java, the satisfyDependencies() method check if an artifact has already been resolved. It changes the behavior from version 1.0.

For example, if you call maven with goals multiproject:clean and multiproject:deploy with artifact versions set to snaphot, maven doesn't resolve the dependencies for the multiproject:deploy because it has been already done for the multiproject:clean.

I know that a multiproject:clean should not resolve the project dependencies but it can probably cause problems in other cases.

All

Comments

Work Log

Change History

Sort Order:

[ Permalink | « Hide ]

Brett Porter added a comment - 19/Aug/05 12:54 AM

why is this a problem? deploy should install first, so the local copy is up to date.

[ Permalink | « Hide ]

Pascal Larin added a comment - 19/Aug/05 10:16 AM

Bret,

I've done some tests. I've started a snapshot build with targets multiproject:clean multiproject:deploy. I let the clean do his job. I stop my build right after the end of the build of my first project, at build:end.

Before starting my build, in my local repo, I have:
303451 Aug 19 10:36 infra-core-dev-SNAPSHOT.jar

After stopping my build,
my target directory: 303451 Aug 19 11:03 infra-core-dev-SNAPSHOT.jar
remote repo: 303451 Aug 19 11:03 infra-core-dev-SNAPSHOT.jar
local repo: 303451 Aug 19 10:36 infra-core-dev-SNAPSHOT.jar

I'll check to see why my artifact is not installed in my local repo.

[ Permalink | « Hide ]

Brett Porter added a comment - 19/Aug/05 06:32 PM

my mistake, :deploy doesn't install.

You should be able to run :clean :install :deploy in sequence to get what you want.

[ Permalink | « Hide ]

Pascal Larin added a comment - 22/Aug/05 10:01 AM

Hum...

In our case, it won't work. We have around 50 subprojects, each project is set to snapshot. It happens sometime that a subproject needs changes from a component previously build in the same multiproject:deploy. I've made patch to always resolve a dependency if it is a snapshot version.

One thing is sure, Maven 1.1 behave differently than 1.0 with this revision (179556).

Pascal

[ Permalink | « Hide ]

Arnaud Heritier added a comment - 03/Aug/06 07:01 AM

I'll have a look at it for the RC1