[jira] Updated: (MDEPLOY-45) Classifier not supported by deploy:deploy

[ http://jira.codehaus.org/browse/MDEPLOY-45?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Schulz updated MDEPLOY-45: - Attachment: mdeploy-45-test.zip The attached mdeploy-45-test.zip contains a sample web project: The war

[jira] Commented: (CONTINUUM-836) Improve HTTP access to POMs for adding a multi-module project

[ http://jira.codehaus.org/browse/CONTINUUM-836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_114442 ] Daniel Schulz commented on CONTINUUM-836: - If your SCM is CVS with ViewCVS/ViewVC on top of it, simply use the Vi

[jira] Updated: (MNGECLIPSE-20) using ${version} for subproject dependencies doesn't work (maven uses 2.4.1 version instead)

[ http://jira.codehaus.org/browse/MNGECLIPSE-20?page=all ] Daniel Schulz updated MNGECLIPSE-20: Attachment: mngeclipse20-trigger.jpg problem trigger > using ${version} for subproject dependencies doesn't work (maven uses 2.4.1 > version instead) >

[jira] Created: (MNG-2651) POM interpolator treats ${pom.something} like ${something} and prefers system properties

POM interpolator treats ${pom.something} like ${something} and prefers system properties Key: MNG-2651 URL: http://jira.codehaus.org/browse/MNG-2651 Project: Mav

[jira] Updated: (MNGECLIPSE-20) using ${version} for subproject dependencies doesn't work (maven uses 2.4.1 version instead)

[ http://jira.codehaus.org/browse/MNGECLIPSE-20?page=all ] Daniel Schulz updated MNGECLIPSE-20: Attachment: org.maven.ide.eclipse-MNGECLIPSE-20-patch.txt Patch with changed RegexBasedModelInterpolator impl. > using ${version} for subproject dependen

[jira] Commented: (MNGECLIPSE-30) Maven plugin keeps looking for non-existent apacheds-*-2.4.1 dependency

[ http://jira.codehaus.org/browse/MNGECLIPSE-30?page=comments#action_79318 ] Daniel Schulz commented on MNGECLIPSE-30: - i found the reason for the "${pom.version} is 2.4.1" problem (for more details and a fix see MNGECLIPSE-20). there is

[jira] Commented: (MNGECLIPSE-20) using ${version} for subproject dependencies doesn't work (maven uses 2.4.1 version instead)

[ http://jira.codehaus.org/browse/MNGECLIPSE-20?page=comments#action_79317 ] Daniel Schulz commented on MNGECLIPSE-20: - again the quick explanation: i found the reason for the "${pom.version} is 2.4.1" problem. there is a system propert

[jira] Commented: (MNGECLIPSE-20) using ${version} for subproject dependencies doesn't work (maven uses 2.4.1 version instead)

[ http://jira.codehaus.org/browse/MNGECLIPSE-20?page=comments#action_79316 ] Daniel Schulz commented on MNGECLIPSE-20: - quick explanation: i found the reason for the "${pom.version} -> 2.4.1" problem. there is a system property of name

[jira] Created: (MECLIPSE-108) .wtpmodules with version 2.4 for javax.servlet:servlet-api:2.3

.wtpmodules with version 2.4 for javax.servlet:servlet-api:2.3 -- Key: MECLIPSE-108 URL: http://jira.codehaus.org/browse/MECLIPSE-108 Project: Maven 2.x Eclipse Plugin Type: Bug Versions: 2.2 Re