You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Tuomas Kiviaho (JIRA)" <ji...@codehaus.org> on 2006/02/21 08:10:31 UTC
[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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org