[jira] Commented: (MECLIPSE-597) Workspace dependencies not resolved for SNAPSHOT dependencies (artifact has a different version from that in dependency management)
[ https://jira.codehaus.org/browse/MECLIPSE-597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=274588#comment-274588 ] Robrecht Anrijs commented on MECLIPSE-597: -- The environment is indeed irrelevant. The provided patch works when installing on version 2.8 of the plugin. Workspace dependencies not resolved for SNAPSHOT dependencies (artifact has a different version from that in dependency management) --- Key: MECLIPSE-597 URL: https://jira.codehaus.org/browse/MECLIPSE-597 Project: Maven 2.x Eclipse Plugin Issue Type: Bug Components: Core : Dependencies resolution and build path (.classpath) Affects Versions: 2.7 Environment: Nexus 1.3.6, Eclipse 3.4, Windows XP Reporter: Michal Galet Priority: Critical Attachments: maven-eclipse-plugin-2.7.patch When generating eclipse project with mvn eclipse:eclipse -Declipse.workspace=d:/eclipse-ws the SNAPSHOT dependencies are not resolved from workspace correctly. See console output below. This is probably caused by the way how Nexus handles the SNAPSHOTs. The artifact is resolved by ArtifactResolver and the version is changed from 1.1.0-SNAPSHOT to 1.1.0-20090819.145009-4. The comparison should be performed against {{artifact.getBaseVersion()}} instead of {{artifact.getVersion()}}. A simple fix is attached as a patch. Console output: [INFO] Artifact com.test:sample:jar:4.0.0.B02-SNAPSHOT already available a s a workspace project, but with different version. Expected: 4.0.0.B02-20090819.145009-4, found : 4.0.0.B02-SNAPSHOT -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MECLIPSE-597) Workspace dependencies not resolved for SNAPSHOT dependencies (artifact has a different version from that in dependency management)
[ http://jira.codehaus.org/browse/MECLIPSE-597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=262648#action_262648 ] Yves Langisch commented on MECLIPSE-597: We are regularly stumbling over this issue which leads to time costly manually work. Is there any reason why the provided patch is not applied yet? I could provide a new patch against the trunk if necessary. Thanks Yves Workspace dependencies not resolved for SNAPSHOT dependencies (artifact has a different version from that in dependency management) --- Key: MECLIPSE-597 URL: http://jira.codehaus.org/browse/MECLIPSE-597 Project: Maven 2.x Eclipse Plugin Issue Type: Bug Components: Core : Dependencies resolution and build path (.classpath) Affects Versions: 2.7 Environment: Nexus 1.3.6, Eclipse 3.4, Windows XP Reporter: Michal Galet Priority: Critical Attachments: maven-eclipse-plugin-2.7.patch When generating eclipse project with mvn eclipse:eclipse -Declipse.workspace=d:/eclipse-ws the SNAPSHOT dependencies are not resolved from workspace correctly. See console output below. This is probably caused by the way how Nexus handles the SNAPSHOTs. The artifact is resolved by ArtifactResolver and the version is changed from 1.1.0-SNAPSHOT to 1.1.0-20090819.145009-4. The comparison should be performed against {{artifact.getBaseVersion()}} instead of {{artifact.getVersion()}}. A simple fix is attached as a patch. Console output: [INFO] Artifact com.test:sample:jar:4.0.0.B02-SNAPSHOT already available a s a workspace project, but with different version. Expected: 4.0.0.B02-20090819.145009-4, found : 4.0.0.B02-SNAPSHOT -- 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
[jira] Commented: (MECLIPSE-597) Workspace dependencies not resolved for SNAPSHOT dependencies (artifact has a different version from that in dependency management)
[ http://jira.codehaus.org/browse/MECLIPSE-597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=262657#action_262657 ] Thomas Maurer commented on MECLIPSE-597: The environment is irrelevant, because it occurs also with a Archiva 1.2.1 repository. The problem arise only during a workspace dependency resolution on a single project (child pom, respectively) and not during a reactor dependency resolution on a parent pom. As Michal already described, the reason is that the ArtifactResolver changes the artifact version in its resolve() method (line 594 in class org.apache.maven.plugin.ide.AbstractIdeSupportMojo). Using artifact.getBaseVersion() in the subsequent code would solve the problem. Workspace dependencies not resolved for SNAPSHOT dependencies (artifact has a different version from that in dependency management) --- Key: MECLIPSE-597 URL: http://jira.codehaus.org/browse/MECLIPSE-597 Project: Maven 2.x Eclipse Plugin Issue Type: Bug Components: Core : Dependencies resolution and build path (.classpath) Affects Versions: 2.7 Environment: Nexus 1.3.6, Eclipse 3.4, Windows XP Reporter: Michal Galet Priority: Critical Attachments: maven-eclipse-plugin-2.7.patch When generating eclipse project with mvn eclipse:eclipse -Declipse.workspace=d:/eclipse-ws the SNAPSHOT dependencies are not resolved from workspace correctly. See console output below. This is probably caused by the way how Nexus handles the SNAPSHOTs. The artifact is resolved by ArtifactResolver and the version is changed from 1.1.0-SNAPSHOT to 1.1.0-20090819.145009-4. The comparison should be performed against {{artifact.getBaseVersion()}} instead of {{artifact.getVersion()}}. A simple fix is attached as a patch. Console output: [INFO] Artifact com.test:sample:jar:4.0.0.B02-SNAPSHOT already available a s a workspace project, but with different version. Expected: 4.0.0.B02-20090819.145009-4, found : 4.0.0.B02-SNAPSHOT -- 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
[jira] Commented: (MECLIPSE-597) Workspace dependencies not resolved for SNAPSHOT dependencies (artifact has a different version from that in dependency management)
[ http://jira.codehaus.org/browse/MECLIPSE-597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=194102#action_194102 ] Kathy Hale commented on MECLIPSE-597: - I'm not sure if I'm having the same problem or not, but I'll comment in case. Project A and Project B are both being migrated to Maven. I migrated A, except for the dependency of Project B. Then migrated Project B, installed a snapshot from B, and then added the coordinates as a dependency to Project A. While both projects are open, Project A will not resolve the dependency (the files are red in Navigator). But if I close Project B, you can see the snapshot jar show up in the Maven library. As soon as I open the Project B again, the snapshot is removed and is not being replaced with the open project (which is what usually happened before). In my other projects, I've seen this feature work sometimes, but not always. Usually when I had problems, it was just out of sync for some reason, but this is the first time where I've seen it completely fail. It's odd because calling Update Maven dependencies is not having problems, I can do a mvn compile while its in the broken state, but I cannot resolve that red without closing the child project. Workspace dependencies not resolved for SNAPSHOT dependencies (artifact has a different version from that in dependency management) --- Key: MECLIPSE-597 URL: http://jira.codehaus.org/browse/MECLIPSE-597 Project: Maven 2.x Eclipse Plugin Issue Type: Bug Components: Core : Dependencies resolution and build path (.classpath) Affects Versions: 2.7 Environment: Nexus 1.3.6, Eclipse 3.4, Windows XP Reporter: Michal Galet Priority: Critical Attachments: maven-eclipse-plugin-2.7.patch When generating eclipse project with mvn eclipse:eclipse -Declipse.workspace=d:/eclipse-ws the SNAPSHOT dependencies are not resolved from workspace correctly. See console output below. This is probably caused by the way how Nexus handles the SNAPSHOTs. The artifact is resolved by ArtifactResolver and the version is changed from 1.1.0-SNAPSHOT to 1.1.0-20090819.145009-4. The comparison should be performed against {{artifact.getBaseVersion()}} instead of {{artifact.getVersion()}}. A simple fix is attached as a patch. Console output: [INFO] Artifact com.test:sample:jar:4.0.0.B02-SNAPSHOT already available a s a workspace project, but with different version. Expected: 4.0.0.B02-20090819.145009-4, found : 4.0.0.B02-SNAPSHOT -- 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