You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Pascal Larin (JIRA)" <ji...@codehaus.org> on 2005/08/10 22:51:57 UTC
[jira] Created: (MAVEN-1660) DependencyVerifier class doesn't resolve an snapshot artifact after attaining a first goal.
DependencyVerifier class doesn't resolve an snapshot artifact after attaining a first goal.
-------------------------------------------------------------------------------------------
Key: MAVEN-1660
URL: http://jira.codehaus.org/browse/MAVEN-1660
Project: Maven
Type: Bug
Components: core
Versions: 1.1-beta-1
Reporter: Pascal Larin
Priority: Minor
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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MAVEN-1660) DependencyVerifier class doesn't resolve an snapshot artifact after attaining a first goal.
Posted by "Pascal Larin (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MAVEN-1660?page=comments#action_44752 ]
Pascal Larin commented on MAVEN-1660:
-------------------------------------
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.
> DependencyVerifier class doesn't resolve an snapshot artifact after attaining a first goal.
> -------------------------------------------------------------------------------------------
>
> Key: MAVEN-1660
> URL: http://jira.codehaus.org/browse/MAVEN-1660
> Project: Maven
> Type: Bug
> Components: core
> Versions: 1.1-beta-1
> Reporter: Pascal Larin
> Priority: Minor
> Fix For: 1.1-beta-2
>
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Updated: (MAVEN-1660) DependencyVerifier class doesn't resolve an snapshot artifact after attaining a first goal.
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MAVEN-1660?page=all ]
Brett Porter updated MAVEN-1660:
--------------------------------
Fix Version: 1.1-beta-2
why is this a problem? deploy should install first, so the local copy is up to date.
> DependencyVerifier class doesn't resolve an snapshot artifact after attaining a first goal.
> -------------------------------------------------------------------------------------------
>
> Key: MAVEN-1660
> URL: http://jira.codehaus.org/browse/MAVEN-1660
> Project: Maven
> Type: Bug
> Components: core
> Versions: 1.1-beta-1
> Reporter: Pascal Larin
> Priority: Minor
> Fix For: 1.1-beta-2
>
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MAVEN-1660) DependencyVerifier class doesn't resolve an snapshot artifact after attaining a first goal.
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MAVEN-1660?page=comments#action_44775 ]
Brett Porter commented on MAVEN-1660:
-------------------------------------
my mistake, :deploy doesn't install.
You should be able to run :clean :install :deploy in sequence to get what you want.
> DependencyVerifier class doesn't resolve an snapshot artifact after attaining a first goal.
> -------------------------------------------------------------------------------------------
>
> Key: MAVEN-1660
> URL: http://jira.codehaus.org/browse/MAVEN-1660
> Project: Maven
> Type: Bug
> Components: core
> Versions: 1.1-beta-1
> Reporter: Pascal Larin
> Priority: Minor
> Fix For: 1.1-beta-2
>
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MAVEN-1660) DependencyVerifier class doesn't resolve an snapshot artifact after attaining a first goal.
Posted by "Pascal Larin (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MAVEN-1660?page=comments#action_44931 ]
Pascal Larin commented on MAVEN-1660:
-------------------------------------
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
> DependencyVerifier class doesn't resolve an snapshot artifact after attaining a first goal.
> -------------------------------------------------------------------------------------------
>
> Key: MAVEN-1660
> URL: http://jira.codehaus.org/browse/MAVEN-1660
> Project: Maven
> Type: Bug
> Components: core
> Versions: 1.1-beta-1
> Reporter: Pascal Larin
> Priority: Minor
> Fix For: 1.1-beta-2
>
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org