Raible's Wiki

Raible Designs
Wiki Home
News
Recent Changes

AppFuse

Homepage
  - Korean
  - Chinese
  - Italian
  - Japanese

QuickStart Guide
  - Chinese
  - French
  - German
  - Italian
  - Korean
  - Portuguese
  - Spanish
  - Japanese

User Guide
  - Korean
  - Chinese

Tutorials
  - Chinese
  - German
  - Italian
  - Korean
  - Portuguese
  - Spanish

FAQ
  - Korean

Latest Downloads

Other Applications

Struts Resume
Security Example
Struts Menu

Set your name in
UserPreferences


Referenced by
...nobody




JSPWiki v2.2.33

[RSS]


Hide Menu

FormattingSourceCode


Difference between version 39 and version 31:

At line 1 changed 1 line.
This page will show you how to setup AppFuse 1.8 and [Jalopy|http://jalopy.sourceforge.net] that you can format/beautify your code.
This page will show you how to setup AppFuse 1.8 and [Jalopy|http://jalopy.sourceforge.net] that you can format/beautify your code. This is useful if you're in a development team or if you like making your code ''more'' readable ;-).
At line 3 changed 1 line.
This tutorial is divided in two. First we have to setup an ant task that calls jalopy to format your code, once there we'll have to modify appfuse's source code (I hope it's not for long, since all we do is modify the javadoc comments in the code).
This tutorial is divided in two. First we have to setup an ant task that calls jalopy to format your code, once there we'll have to modify appfuse's source code (I hope it's not for long, since all we do is modify the javadoc comments in the code). Every file url starts at your projects root foolder, I used appfuse's source code for this tutorial, but have done it with several __ant new__ projects (just change the __org/appfuse__ package to whatever your using, but I'll recomend changing your root appfuse, that way, every new project will have jalopy setup). There are two attachments at the bottom of the page you'll need.
At line 45 changed 1 line.
If you're looking at what we're doing you'll notice a convention xml named __um.xml__... this is the convention I use, and you can [change it|http://jalopy.sourceforge.net/printer.html] if you like, but I won't get into that, there are [tools|http://jalopy.sourceforge.net/download.html] to do that (an Eclipse plugin, a standalone gui, etc.). By the way, the __um.xml__ is attached at the bottom of this page as well as the __jalopy-1.0b11.zip__ (you'll have to use this one, if you want jalopy task you've just create it to format your javadoc comments, because it's patched to know what to do with the servlet-mapping tag found in some servlets).
If you're looking at what we're doing you'll notice a convention xml named __um.xml__... this is the convention I use, and you can [change it|http://jalopy.sourceforge.net/printer.html] if you like, but I won't get into that, there are [tools|http://jalopy.sourceforge.net/download.html] to do that (an Eclipse plugin, a standalone gui, etc.). By the way, the __um.xml__ is attached at the bottom of this page as well as the __jalopy-1.0b11.zip__ (you'll have to use this one, if you want the jalopy task you've just create it to format your javadoc comments, because it's patched to know what to do with the servlet-mapping tag found in some servlets).
At line 81 changed 1 line.
And as Matt so eloquently puts it
And as [Matt|MattRaible] so eloquently puts it:

Back to FormattingSourceCode, or to the Page History.