Eugeny, I don't think this particular issue been fixed yet. The problem seem to related to sources configuration in cached by JDT in the launch config, and that sources are not being updated when project configuration is changed. We'll have to update existing launch configurations upon project change and there is already foundation for this in m2eclipse core.
Please submit bug report to the project issue tracker at http://jira.codehaus.org/browse/MNGECLIPSE It would also help if you could provide some test project that we could use to reproduce and debug this issue Thanks Eugene Eugeny N Dzhurinsky-2 wrote: > > I recently found some really weird issue when doing the debug of the > libraries > with attached sources in Eclipse. I used projects, which are being built > by > Maven2. The problem is if any new dependency was added after the debug > configuration is created, then the source for the dependency is downloaded > using the context menu - Eclipse does not see the source until the debug > configuration is removed and re-created. I am using remote application > debug > configuration if that matters. > > Looks like this is m2eclipse issue, since if the project is re-generated > after > the dependency was added using maven eclipse plugin - the new sources are > resolved immediately. > > Can somebody please advice? > -- View this message in context: http://www.nabble.com/m2eclipse-plugin%2C-debug-configuration-classpath-sources-issue--tp19944085p20240001.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
