[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-431) Non-project EJB dependencies need a version number in application.xml
[ https://jira.codehaus.org/browse/MECLIPSE-431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=272992#comment-272992 ] Robrecht Anrijs commented on MECLIPSE-431: -- patch MECLIPSE_431.4 and MECLIPSE_431.3 are working. I was wondering when these bugs are being fixed in the plugin. Is this plugin end of life? Non-project EJB dependencies need a version number in application.xml - Key: MECLIPSE-431 URL: https://jira.codehaus.org/browse/MECLIPSE-431 Project: Maven 2.x Eclipse Plugin Issue Type: Bug Components: RAD support, WTP support Affects Versions: 2.5.1 Reporter: Michael Johns Attachments: MECLIPSE-431.2.patch, MECLIPSE_431.3.patch, MECLIPSE_431.4.patch, MECLIPSE-431.patch This relates to issue MECLIPSE-430. When including EJBs that were built previously (ie, not part of the same multi-module project as the ear), the application.xml needs to include their version number. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira