[jira] Commented: (SUREFIRE-784) Surefire plugin cannot be debugged remotely by eclipse

[ https://jira.codehaus.org/browse/SUREFIRE-784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=283245#comment-283245 ] lisak commented on SUREFIRE-784: It explains that you cannot useManifestOnlyJar if you need to ap

[jira] Commented: (MPLUGIN-189) add java 5 annotations support to mark Mojo sources

[ https://jira.codehaus.org/browse/MPLUGIN-189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=282907#comment-282907 ] lisak commented on MPLUGIN-189: --- Great Herve, I'll try it out. I hope Maven moves forwards and decid

[jira] Commented: (MPLUGIN-164) Extending a Mojo Class and used in a new Mojo Project, parameter fields in the parent mojo are not set, this disables reuse of existing mojo project.

[ https://jira.codehaus.org/browse/MPLUGIN-164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=282906#comment-282906 ] lisak commented on MPLUGIN-164: --- +1 annotations [MPLUGIN-189|http://jira.codehaus.org/browse/MPLUGI

[jira] Commented: (SUREFIRE-784) Surefire plugin cannot be debugged remotely by eclipse

[ https://jira.codehaus.org/browse/SUREFIRE-784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=282899#comment-282899 ] lisak commented on SUREFIRE-784: I wrote a [blog post|http://l154k.blogspot.com/2011/11/booting-

[jira] Commented: (SUREFIRE-784) Surefire plugin cannot be debugged remotely by eclipse

[ https://jira.codehaus.org/browse/SUREFIRE-784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=282885#comment-282885 ] lisak commented on SUREFIRE-784: Interesting, the test(s) runs only when : {noformat} false false

[jira] Commented: (SUREFIRE-784) Surefire plugin cannot be debugged remotely by eclipse

[ https://jira.codehaus.org/browse/SUREFIRE-784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=282884#comment-282884 ] lisak commented on SUREFIRE-784: My apologies, I used a different version of surefire plugin as d

[jira] Created: (SUREFIRE-784) Surefire plugin cannot be debugged remotely by eclipse

Surefire plugin cannot be debugged remotely by eclipse -- Key: SUREFIRE-784 URL: https://jira.codehaus.org/browse/SUREFIRE-784 Project: Maven Surefire Issue Type: Story Components

[jira] Commented: (SUREFIRE-118) Cannot override read-only parameter: classpathElements

[ https://jira.codehaus.org/browse/SUREFIRE-118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=282880#comment-282880 ] lisak commented on SUREFIRE-118: Guys I would need to add 200 jars on classpath to boot up Lifera

[jira] Commented: (SUREFIRE-667) Setting up maven resources when testing in addition to testResources

[ http://jira.codehaus.org/browse/SUREFIRE-667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=252632#action_252632 ] lisak commented on SUREFIRE-667: Here is a blog post about the archetype, the last paragraph explai

[jira] Commented: (SUREFIRE-667) Setting up maven resources when testing in addition to testResources

[ http://jira.codehaus.org/browse/SUREFIRE-667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=250499#action_250499 ] lisak commented on SUREFIRE-667: The resources (spring configs mainly) in Liferay plugins are being

[jira] Commented: (SUREFIRE-667) Setting up maven resources when testing in addition to testResources

[ http://jira.codehaus.org/browse/SUREFIRE-667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=250416#action_250416 ] lisak commented on SUREFIRE-667: Thank you Kristian, it is totally container irrelevant issue. It

[jira] Commented: (SUREFIRE-667) Setting up maven resources when testing in addition to testResources

[ http://jira.codehaus.org/browse/SUREFIRE-667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=250391#action_250391 ] lisak commented on SUREFIRE-667: the main problem is : naming conflict on the classpath : project

[jira] Commented: (SUREFIRE-667) Setting up maven resources when testing in addition to testResources

[ http://jira.codehaus.org/browse/SUREFIRE-667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=250359#action_250359 ] lisak commented on SUREFIRE-667: Yeah, I also needed surefire-plugin to do this many times. It ofte