Re: Debug library code in eclipse

2017-04-12 Thread Thomas Broyer
On Tuesday, April 11, 2017 at 7:17:54 PM UTC+2, Juan Pablo Gardella wrote: > > Using eclipse you don't need do that. Simply include all the projects > (including pom artifact if you have one) and configure by using "workspace > resolution". Check > https://books.sonatype.com/m2eclipse-book/ref

Re: Debug library code in eclipse

2017-04-11 Thread Magnus
There is one big disadvantage when doing it like this: You cannot edit the library source code! Eclipse shows the library code as readonly, since it has taken it from lib-xxx-sources.jar. So when you debug into the library code and then want to make a change there, you have to open the "real" so

Re: Debug library code in eclipse

2017-04-11 Thread Magnus
Now Jens' solution works for me. I had to do Maven -> "Update Project" and "Refresh" several times until it worked #-) Thanks! Magnus -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it

Re: Debug library code in eclipse

2017-04-11 Thread Juan Pablo Gardella
Using eclipse you don't need do that. Simply include all the projects (including pom artifact if you have one) and configure by using "workspace resolution". Check https://books.sonatype.com/m2eclipse-book/reference/eclipse.html On Tue, 11 Apr 2017 at 14:06 Magnus wrote: > Hi Jens, > > I added t

Re: Debug library code in eclipse

2017-04-11 Thread Magnus
Hi Jens, I added the plugins to pom.xml and configured eclipse to download the sources. I did a mvn install for the lib and I can verify that the files *-sources.jar and *.-javadoc.jar are created. But when starting a debug session for the app in eclipse, I still get the message "Source not fou

Re: Debug library code in eclipse

2017-04-11 Thread Magnus
Thanks, I'll try it out. But besides these two solutions: What about simply adding the library eclipse project as a dependent project to the application eclipse project? Magnus -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from t

Re: Debug library code in eclipse

2017-04-10 Thread Jens
Alternatively you can probably also change your maven settings in Eclipse to always download sources / javadoc artifacts as well (also useful for stepping into 3rd party libs), see: http://stackoverflow.com/questions/310720/get-source-jar-files-attached-to-eclipse-for-maven-managed-dependencies

Re: Debug library code in eclipse

2017-04-10 Thread Rodolfo Raya
Expand "Referenced Libraries" and locate the jar in your project inside Eclipse. Right-click the jar and select "Properties". In the dialog that appears, select "Java Source Attachment" and complete the form using the "Workspace location" option. Hope this helps, Rodolfo On Mon, Apr 10, 2017 a

Debug library code in eclipse

2017-04-10 Thread Magnus
Hello, my application uses a java library (jar). When debugging the application, I would like to also step into the library code, but it's not available. Both, the application and the library are maven projects. The library is defined as a dependency in the application's pom.xml file. Both proj