[jira] Issue Comment Edited: (MSITE-222) -D command line options not recognised

[ http://jira.codehaus.org/browse/MSITE-222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=209128#action_209128 ] Joost den Boer edited comment on MSITE-222 at 2/4/10 6:00 AM: -- I run into

[jira] Commented: (MSITE-222) -D command line options not recognised

[ http://jira.codehaus.org/browse/MSITE-222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=209128#action_209128 ] Joost den Boer commented on MSITE-222: -- I run into the same problem when trying to use a Bamboo b

[jira] Commented: (MNG-2199) Version ranges not supported for parent artifacts

[ http://jira.codehaus.org/browse/MNG-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=208812#action_208812 ] Joost den Boer commented on MNG-2199: - Don't agree with Todor. Using relative path is not a solutio

[jira] Commented: (MECLIPSE-584) No eclipse classpath entries generated for aspectj dependencies

[ http://jira.codehaus.org/browse/MECLIPSE-584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=185468#action_185468 ] Joost den Boer commented on MECLIPSE-584: - This is caused by these lines in EclipseClasspat

[jira] Updated: (MEAR-107) Cannot generate Eclipse file with eclipse:eclipse when dependent projects are not installed in repository

[ http://jira.codehaus.org/browse/MEAR-107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joost den Boer updated MEAR-107: Attachment: MEAR-107-maven-ear-plugin-2.3.2.patch Patch for this issue > Cannot generate Eclipse file with

[jira] Created: (MEAR-107) Cannot generate Eclipse file with eclipse:eclipse when dependent projects are not installed in repository

Cannot generate Eclipse file with eclipse:eclipse when dependent projects are not installed in repository - Key: MEAR-107 URL: http://jira.codehaus.org/browse/

[jira] Commented: (MECLIPSE-252) Error trying to create an EAR project that contains one web module. It doesn't point to the local project, but only tries to find it in the local and remote repositori

[ http://jira.codehaus.org/browse/MECLIPSE-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=182921#action_182921 ] Joost den Boer commented on MECLIPSE-252: - Any progress on this issue? We're in the process

[jira] Commented: (MECLIPSE-577) Project Dependencies list too intrusive while navigating projects.

[ http://jira.codehaus.org/browse/MECLIPSE-577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=181986#action_181986 ] Joost den Boer commented on MECLIPSE-577: - Isn't this exactly what m2eclipse does? Install

[jira] Commented: (MNG-2551) pom metadata file gets truncated during install into local repository

[ http://jira.codehaus.org/browse/MNG-2551?page=comments#action_75046 ] Joost den Boer commented on MNG-2551: - Not sure what you mean. I had this problem with my project when it was on version 0.3. After the buildserver ran, the pom was trun

[jira] Commented: (MNG-2551) pom metadata file gets truncated during install into local repository

[ http://jira.codehaus.org/browse/MNG-2551?page=comments#action_74865 ] Joost den Boer commented on MNG-2551: - I went from version 0.3 to 0.4-SNAPSHOT yesterday and now this problem does not occur anymore for this project. > pom metadata fil

[jira] Commented: (MNG-2551) pom metadata file gets truncated during install into local repository

[ http://jira.codehaus.org/browse/MNG-2551?page=comments#action_74725 ] Joost den Boer commented on MNG-2551: - I have the exact same problem on a continuum buildserver on linux using Maven 2.0.4 and JDK 1.5_06. The problem occurs only on some

[jira] Commented: (MNG-2550) ClassNotFoundException and NoClassDefFoundError when running plugin

[ http://jira.codehaus.org/browse/MNG-2550?page=comments#action_74458 ] Joost den Boer commented on MNG-2550: - ok, I overcame my doubts and tried it. And you're right, it works. However, this only solves half of the problem. There still is the

[jira] Commented: (MNG-2550) ClassNotFoundException and NoClassDefFoundError when running plugin

[ http://jira.codehaus.org/browse/MNG-2550?page=comments#action_74226 ] Joost den Boer commented on MNG-2550: - I don't agree the log4j config causes the problem. - If I run the same application as the plugin does from the command line or in

[jira] Created: (MNG-2550) ClassNotFoundException and NoClassDefFoundError when running plugin

ClassNotFoundException and NoClassDefFoundError when running plugin --- Key: MNG-2550 URL: http://jira.codehaus.org/browse/MNG-2550 Project: Maven 2 Issue Type: Bug Co

[jira] Created: (MNG-2549) Plugin dependencies are not put in generated plugin.xml

Plugin dependencies are not put in generated plugin.xml --- Key: MNG-2549 URL: http://jira.codehaus.org/browse/MNG-2549 Project: Maven 2 Issue Type: Bug Components: Plugin Creatio