Yep - the sources came down. The problem is in automatically attaching them to the debugger.
I have an Eclipse DEBUG configuration invoking "mvn jetty:run" and it breaks just fine into my own source code - but when I go to step into the Wicket source, it can't find it the source code. The sources are downloaded and located in the same directories as the jars in my maven repository. I can explicitly attach them via the screen I mentioned in the first post by adding them individually as External Archives ... but sounds like I'm missing something. I was thinking that the maven/jetty/m2eclipse combo would know where to look. Explicitly adding every source jar to my project is a bit painful ... and so it sounds like I'm doing something incorrectly. Is this just supposed to 'work'. -Luther On Mon, Mar 23, 2009 at 12:31 PM, francisco treacy < [email protected]> wrote: > i'm not sure i'm using m2eclipse (but i think so). to download sources > just right click on your eclipse project, go to maven > download > sources. if we're using the same plugin, this should work. > > francisco > > > On Mon, Mar 23, 2009 at 6:23 PM, Luther Baker <[email protected]> > wrote: > > I am having a slight bit of trouble getting Eclipse to step into the > Wicket > > source code while using the m2eclipse plugin. > > > > The m2eclpse has successfully downloaded the Wicket 1.3.5 distribution. > My > > application fires up and works just fine in Eclipse. I have also enabled > the > > m2eclipse plugin to download sources - I can see the source jars in the > m2 > > repository now as well. > > > > I am trying to implement a security/authentiation/authorization scheme > and > > while debugging, anytime I step out of my workspace source code, I get a > > window in Eclipse that says "Source not found" and a button that says > "Edit > > Source Lookup Path"... > > > > If I click that button, I can choose to explicitly add: > > > > *Archive*: a jar or zip in the workspace containing source files > > *External Archive*: a jar or zip in the local file system containing > source > > files > > *File System Directory*: a directory in the local file system > > *Java Classpath Variable*: workspace folder, local directory, or archive > > referenced by a variable path > > *Java Library*: a collection of binary archives with attached source > > *Java Project*: source folders in a Java project > > *Project*: a project in the workspace > > *Working Set*: > > *Workspace*: all projects in the workspace > > *Workspace Folder*: a folder in the workspace > > > > And I can click External Archive and explicitly add every single source > jar > > file --- but I was wondering - shouldn't this automatically happen? > > > > Does anyone have a suggestion? or confirmation that these source jars > must > > be manually added to step into Wicket code while using the m2eclipse > plugin > > in Eclipse? I think this is probably an m2eclipse question ... but hoping > > someone here has dealt with this already. > > > > Thanks much, > > > > -Luther > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
