Re: maven, eclipse and wicket
I actually use that toolset all the time, run inside eclipse and have no trouble. If the java source is there it finds it. I can only assume there is a problem with his configuration some place. - Brill On 23-Mar-09, at 4:10 PM, Pointbreak wrote: I guess that if you use mvn jetty:run, maven will deploy your application (including the dependent jars). Thus it is not directly using the jars in the maven repo, but the deployed copies, therefore eclipse would be unable to find the sources. You could make a Start.java that just starts jetty (I think the wicket quick start projects include one). That's the easiest way to debug applications using jetty. On Mon, 23 Mar 2009 12:44 -0500, "Luther Baker" wrote: 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 < francisco.tre...@gmail.com> 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 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: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: maven, eclipse and wicket
I guess that does seem to make the most sense ... Thanks, -Luther On Mon, Mar 23, 2009 at 3:10 PM, Pointbreak > wrote: > I guess that if you use mvn jetty:run, maven will deploy your > application (including the dependent jars). Thus it is not directly > using the jars in the maven repo, but the deployed copies, therefore > eclipse would be unable to find the sources. > You could make a Start.java that just starts jetty (I think the wicket > quick start projects include one). That's the easiest way to debug > applications using jetty. > > On Mon, 23 Mar 2009 12:44 -0500, "Luther Baker" > wrote: > > 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 < > > francisco.tre...@gmail.com> 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 > > > 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: users-unsubscr...@wicket.apache.org > > > For additional commands, e-mail: users-h...@wicket.apache.org > > > > > > > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
Re: maven, eclipse and wicket
I guess that if you use mvn jetty:run, maven will deploy your application (including the dependent jars). Thus it is not directly using the jars in the maven repo, but the deployed copies, therefore eclipse would be unable to find the sources. You could make a Start.java that just starts jetty (I think the wicket quick start projects include one). That's the easiest way to debug applications using jetty. On Mon, 23 Mar 2009 12:44 -0500, "Luther Baker" wrote: > 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 < > francisco.tre...@gmail.com> 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 > > 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: users-unsubscr...@wicket.apache.org > > For additional commands, e-mail: users-h...@wicket.apache.org > > > > - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: maven, eclipse and wicket
make sure your m2e knows where your user repo is... it might not have it set. fyi - not all projects have source. - brill On 23-Mar-09, at 1:44 PM, Luther Baker wrote: 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 < francisco.tre...@gmail.com> 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 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: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: maven, eclipse and wicket
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 < francisco.tre...@gmail.com> 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 > 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: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
Re: maven, eclipse and wicket
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 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: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: maven, eclipse and wicket
Right-click project -> Maven -> Download sources You can see for which jar's m2eclipse has downloaded sources via the icon displayed in front of the jar under "Maven dependencies" in the project explorer. On Mon, 23 Mar 2009 12:23 -0500, "Luther Baker" 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: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
maven, eclipse and wicket
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
