[jira] Commented: (MNGECLIPSE-81) Maven2 dependencies library providing souce information when running/debugging projects
[ http://jira.codehaus.org/browse/MNGECLIPSE-81?page=comments#action_59004 ] Tuomas Kiviaho commented on MNGECLIPSE-81: -- 1. Have Eclipse WebTools project installed 2. Create new (preferrably generic) server and attach some (web) project to it. 3. Open launch configuration from server cheat sheet that can be opened by doubleclicking the server 4. Select source tab and press add source 5. Select 'java library' and from opened dialog you can pick up 'Maven2 managed dependencies'. Here you have the possibility to select WTP 'web app libraries' as well. Doublecliking it will sometimes lead to internal eclipse error. With this configuration I anticipate that source's can be found as they do when I explicitly add each *-source.jar, but when a debug breakpoint is met path to source is still requested. The 'Configure..' button can be achieved by rightclicking the 'Maven2 managed dependencies', but it'll open just a blank dialog. Maven2 dependencies library providing souce information when running/debugging projects --- Key: MNGECLIPSE-81 URL: http://jira.codehaus.org/browse/MNGECLIPSE-81 Project: Maven 2.x Extension for Eclipse Type: Wish Reporter: Tuomas Kiviaho Assignee: Eugene Kuleshov Attachments: Launch configuration.jpg Thanks for the source attachment option. When running projects it would be great if the plugin could as well provide the same functionality. For instance WTP server lauch configuration allows me to select the dependency library, but I'm still not able to see any sources. I bet the reason is the same as with WTP Web App library that causes a nasty Eclipse jam side effect when trying to use it by double clicking. The difference between these two libraries is that WTP has a dialog behind Configure... button which I think is nullpointering because there is no reference to any project. This would be a propably be a place to implement an alternative project reference. Of course reference to some pom.xml even outside workspace (a JBoss server minimal pom.xml perhaps) would be most flexible. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNGECLIPSE-81) Maven2 dependencies library providing souce information when running/debugging projects
[ http://jira.codehaus.org/browse/MNGECLIPSE-81?page=comments#action_59032 ] Eugene Kuleshov commented on MNGECLIPSE-81: --- Maven2 Managed Dependencies library container does not work this way and I am not sure if we can disable choosing out container from there. It only work for current project that have pom.xml. So, if you'll go to the source management and add a project that has maven library container you should see all the sources. Please verify and confirm that. As of internal Eclipse error. Can you please check .log file or Error Log view when that happens and verify that there is org.maven.ide.eclipse in the stack trace . then fill a separate report for that issue either in ours or Eclipse bug tracking system. Maven2 dependencies library providing souce information when running/debugging projects --- Key: MNGECLIPSE-81 URL: http://jira.codehaus.org/browse/MNGECLIPSE-81 Project: Maven 2.x Extension for Eclipse Type: Wish Reporter: Tuomas Kiviaho Assignee: Eugene Kuleshov Attachments: Launch configuration.jpg Thanks for the source attachment option. When running projects it would be great if the plugin could as well provide the same functionality. For instance WTP server lauch configuration allows me to select the dependency library, but I'm still not able to see any sources. I bet the reason is the same as with WTP Web App library that causes a nasty Eclipse jam side effect when trying to use it by double clicking. The difference between these two libraries is that WTP has a dialog behind Configure... button which I think is nullpointering because there is no reference to any project. This would be a propably be a place to implement an alternative project reference. Of course reference to some pom.xml even outside workspace (a JBoss server minimal pom.xml perhaps) would be most flexible. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNGECLIPSE-81) Maven2 dependencies library providing souce information when running/debugging projects
[ http://jira.codehaus.org/browse/MNGECLIPSE-81?page=comments#action_58893 ] Tuomas Kiviaho commented on MNGECLIPSE-81: -- Reference to similar Eclipse WTP issue HTTPS://BUGS.ECLIPSE.ORG/BUGS/SHOW_BUG.CGI?ID=128349 Maven2 dependencies library providing souce information when running/debugging projects --- Key: MNGECLIPSE-81 URL: http://jira.codehaus.org/browse/MNGECLIPSE-81 Project: Maven 2.x Extension for Eclipse Type: Wish Reporter: Tuomas Kiviaho Assignee: Eugene Kuleshov Thanks for the source attachment option. When running projects it would be great if the plugin could as well provide the same functionality. For instance WTP server lauch configuration allows me to select the dependency library, but I'm still not able to see any sources. I bet the reason is the same as with WTP Web App library that causes a nasty Eclipse jam side effect when trying to use it by double clicking. The difference between these two libraries is that WTP has a dialog behind Configure... button which I think is nullpointering because there is no reference to any project. This would be a propably be a place to implement an alternative project reference. Of course reference to some pom.xml even outside workspace (a JBoss server minimal pom.xml perhaps) would be most flexible. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNGECLIPSE-81) Maven2 dependencies library providing souce information when running/debugging projects
[ http://jira.codehaus.org/browse/MNGECLIPSE-81?page=comments#action_58898 ] Eugene Kuleshov commented on MNGECLIPSE-81: --- It would be nice to have exact steps to reproduce this issue. Maven2 dependencies library providing souce information when running/debugging projects --- Key: MNGECLIPSE-81 URL: http://jira.codehaus.org/browse/MNGECLIPSE-81 Project: Maven 2.x Extension for Eclipse Type: Wish Reporter: Tuomas Kiviaho Assignee: Eugene Kuleshov Thanks for the source attachment option. When running projects it would be great if the plugin could as well provide the same functionality. For instance WTP server lauch configuration allows me to select the dependency library, but I'm still not able to see any sources. I bet the reason is the same as with WTP Web App library that causes a nasty Eclipse jam side effect when trying to use it by double clicking. The difference between these two libraries is that WTP has a dialog behind Configure... button which I think is nullpointering because there is no reference to any project. This would be a propably be a place to implement an alternative project reference. Of course reference to some pom.xml even outside workspace (a JBoss server minimal pom.xml perhaps) would be most flexible. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
