[jira] Commented: (MNGECLIPSE-46) Repository search dialog not handling - properly
[ http://jira.codehaus.org/browse/MNGECLIPSE-46?page=comments#action_60334 ] Tuomas Kiviaho commented on MNGECLIPSE-46: -- Dot seems to have similar effect when for instance searching for javax.portlet Repository search dialog not handling - properly -- Key: MNGECLIPSE-46 URL: http://jira.codehaus.org/browse/MNGECLIPSE-46 Project: Maven 2.x Extension for Eclipse Type: Improvement Components: Repository Management Versions: 0.0.4 Reporter: Dmitri Maximovich Assignee: Eugene Kuleshov Priority: Minor Fix For: 1.0.0 If user types commons-lang search result would be empty, even so commons-lang is listed in repository index. Most likely dash is treated as token separator. -- 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-83) Hiding of runtime scope
[ http://jira.codehaus.org/browse/MNGECLIPSE-83?page=comments#action_59534 ] Tuomas Kiviaho commented on MNGECLIPSE-83: -- If there would be a bulletproof way to determine wether or not Eclipse project is intended to be run only in container... What I can come up with is the project descriptor ear/war packaging (ear/war) and/or existence of WTP project nature. I'm not pleased with the latter, since it woud be too much to require TPTP usage for test scope dependencies to be considered. POM dependency then again will fail for other standard packaging types like .rar and definetly for vendor spesific types like JBoss .ejb3 and .aop. Hiding of runtime scope --- Key: MNGECLIPSE-83 URL: http://jira.codehaus.org/browse/MNGECLIPSE-83 Project: Maven 2.x Extension for Eclipse Type: Sub-task Reporter: Tuomas Kiviaho Assignee: Eugene Kuleshov The Maven2 dependencies library get's bloated since runtime scope is included as well. After all the plugin is providing build path support so compile and provided plus most likely test since Eclipse can't tell the difference (and system) should be enough. -- 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] Created: (MNGECLIPSE-83) Hiding of runtime scope
Hiding of runtime scope --- Key: MNGECLIPSE-83 URL: http://jira.codehaus.org/browse/MNGECLIPSE-83 Project: Maven 2.x Extension for Eclipse Type: Sub-task Reporter: Tuomas Kiviaho Assigned to: Eugene Kuleshov The Maven2 dependencies library get's bloated since runtime scope is included as well. After all the plugin is providing build path support so compile and provided plus most likely test since Eclipse can't tell the difference (and system) should be enough. -- 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_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] Updated: (MNGECLIPSE-81) Maven2 dependencies library providing souce information when running/debugging projects
[ http://jira.codehaus.org/browse/MNGECLIPSE-81?page=all ] Tuomas Kiviaho updated MNGECLIPSE-81: - Attachment: Launch configuration.jpg 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] Closed: (MNGECLIPSE-81) Maven2 dependencies library providing souce information when running/debugging projects
[ http://jira.codehaus.org/browse/MNGECLIPSE-81?page=all ] Tuomas Kiviaho closed MNGECLIPSE-81: Resolution: Won't Fix The problem Eclipse internal error only exist when using WTP. Maven2 plugin doesn't generate a similar situation. There is an error with stacktrace already open at bugs.eclipse.org (bug 128349). What comes to choosing java project instead of playing around with library itself. This approach is what I tried first, but it seems that Eclipse treats only source folder from the project and ignores java libraries that have source folders tied to them. I'm closing the issue right away and moving to bother Eclipse team. Anyway thank you for clarifying a couple of things for me. 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] Created: (MNGECLIPSE-78) Attaching javadocs to dependent libraries is misleadingly made possible.
Attaching javadocs to dependent libraries is misleadingly made possible. Key: MNGECLIPSE-78 URL: http://jira.codehaus.org/browse/MNGECLIPSE-78 Project: Maven 2.x Extension for Eclipse Type: Bug Components: Dependency Resolver Versions: 0.0.5 Reporter: Tuomas Kiviaho Assigned to: Eugene Kuleshov I noticed that even though I'm able to edit javadoc locations and successfully verify them, applying the changes has not yet any effect. Next time looking at the lib the change just made has vanished. It's sad that pom.xml doesn't support yet javadoc outside the project http://jira.codehaus.org/browse/MNG-2040, but at least repositories could be used in same manner as for java source lookups. -- 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] Created: (MNGECLIPSE-81) Maven2 dependencies library providing souce information when running/debugging projects
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 Assigned to: 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_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-17) Can't Attach Source to Maven Dependencies
[ http://jira.codehaus.org/browse/MNGECLIPSE-17?page=comments#action_56089 ] Tuomas Kiviaho commented on MNGECLIPSE-17: -- Also javadoc and native library locations are non modifiable. Access rule seems to be modifiable for Maven2 Dependencies top level, but individual packages are as well non modifiable Can't Attach Source to Maven Dependencies - Key: MNGECLIPSE-17 URL: http://jira.codehaus.org/browse/MNGECLIPSE-17 Project: Maven 2.x Plug-in for Eclipse Type: Improvement Versions: 0.0.3 Reporter: Lee Meador Assignee: Eugene Kuleshov Fix For: 1.0.0 There does not seem to be any way to attach source to any of the classpath entries that the maven2 plugin adds. When you are tracing around (or using ctrl-F3) and it pops up a class that for which it doesn't know the source there is usually a button you can click to add source. If the class is among the Maven Dependencies, there is no button. The instructions that it does give don't really seem to apply. You can't bring up the project properties build classpath and add source. -- 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]
