Re: FW: Maven 3.1.1 plugin and debugging - problem solved

that's strange and should not be happening. If the appropriate 
dependency can be identified as an open project, all queries should 
prefer the actual sources over content of local repository.
Can you file it as a bug?

Thanks

Milos

stroudcuster <at> comcast.net wrote:
> I finally have this figured out.  Apparently, the previous version of the Maven plugin retrieved
referenced source code from the currently open projects, if available.  The new version of the plugin
expects to find a *-source.jar file in the repository under the version referenced in the dependency
element for the library.
>
> The release goal I was running didn't produce this jar.  Once I corrected that, I found that breakpoints set
in the source code of the library project weren't honored by the debug process.  With the new version, you
have to expand the library's node under the Libraries section of the referring project, open the
appropriate source member and create the desired breakpoints.
>
> Stroud Custer
> -------------- Forwarded Message: --------------
> From: stroudcuster <at> comcast.net
> To: nbusers <at> netbeans.org
> Subject: [nbusers] Maven 3.1.1 plugin and debugging
> Date: Thu, 8 May 2008 14:08:16 +0000
>   
>> I updated to the Maven 3.1.1 plugin a few days ago, and I'm having a problem 
>> with debugging,  The IDE is not able to find source for related projects whose 
>> jar files are listed in the referring projects dependencies.  This also affect 
>> the ability to reference source code via ctrl-B.
>>
>> I'm not sure if the start of this problem coincides with my update, but I can't 
>> find any other issue.  Everything worked fine a few days ago.
>>
>> Stroud Custer
>>     
>
>