AppFuseEclipse |
|
Your trail: |
Difference between
version 29
and
version 28:
At line 15 changed 1 line. |
Open Eclipse (either with an existing or a new workspace) and to go File → Import..., select ''Existing Project into Workspace'' and click ''Next >''. Enter the pathname to the directory of your project or click the Browse... button and select the directory. Click the Finish button. Eclipse will load and build the project. At this point you'll probably have 2 Problems complaining that it can't build your project due to an ''Unbound classpath variable''. You'll correct this in the next step. |
Open Eclipse (either with an existing or a new workspace) and to go File → Import..., select ''Existing Project into Workspace'' and click ''Next >''. Enter the pathname to the directory of your project or click the Browse... button and select the directory. Click the Finish button. Eclipse will load and build the project. At this point you'll probably have 2 Problems complaining that it can't build your project due to an ''Unbound classpath variable''. You'll correct this in the next step. |
At line 41 changed 6 lines. |
It's also possible to run your JUnit tests in Eclipse. I should note that if you're running an ActionTest, you'll need to execute "ant deploy-test-war" and then start Tomcat before running them. To configure Eclipse to run AppFuse's JUnit Tests, all you need to do is define a J2EE_HOME variable. To do this, go to Window → Preferences → Java → Classpath Variables. Add a new variable called J2EE_HOME and point it to the location where you have the [J2EE SDK|http://java.sun.com/j2ee/download.html#sdk] installed. AppFuse already has its classpath configured (in the .classpath file) to include J2EE_HOME/lib/j2ee.jar. |
|
Open a test you'd like to run (i.e. UserDaoTest) and go to Run → Debug As → JUnit Test. If this doesn't work, make sure you have AppFuse 1.0.1+ |
|
!!Tips for Debugging and UI Editing [#7] |
For debugging, I use the Tomcat Plugin in Eclipse and set breakpoints. For little changes, I use "ant deploy-web" which only takes a couple of seconds. For truly minor tweaks, it's sometimes easier to edit the file in Tomcat's webapps folder. For major design changes, I usually run the app, view source on a page and save it to a "sandbox" folder in the same directory as my project. Then I do a find/replace and change all "/appfuse/" references to "../web/". This allows me to change CSS and JS files and just refresh the file in the sandbox. |
It's also possible to run your JUnit tests in Eclipse. I should note that if you're running an ActionTest, you'll need to execute |
Back to AppFuseEclipse,
or to the Page History.
|