This has been fixed in the trunk version of m2eclipse.
On 12-Oct-08, at 10:51 AM, Eugeny N Dzhurinsky wrote:
Hello!
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?
Thank you in advance!
--
Eugene N Dzhurinsky
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
What matters is not ideas, but the people who have them. Good people
can fix bad ideas, but good ideas can't save bad people.
-- Paul Graham
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
