Source

webwork / build.xml

Author Commit Message Labels Comments Date
rainerh
Publish properly to OpenSymphony maven repo
rainerh
ant dist target does not package ivyconf.xml
rainerh
WebWork 2.2.3 release: Updating ivy.xml, build.properties & pom.xml
Tags
webwork_2-2-3
rainerh
Running ant new in webapps fails
the_mindstorm
added creation of 2 additional jars in the distro (pure WW and static WW)
tmjee
Issue number: ww-1251
rainerh
Getting rid of those unknown javadoc tag warnings
plightbo
filtering a bad idea if you want to use the pom to build the project :P
plightbo
automatic ibiblio deployment (maybe?)
rainerh
Create blank webapp application with an ant target to create a getting started webapp
plightbo
include the xwork source too
plightbo
removed wwia and ajax apps
plightbo
WW-1054: make the build entirely self-sufficient
plightbo
WW-1024: allow building of webapps (war files) in addition to QuickStart
rgielen
cleaned up a bit (again)
rgielen
Readded webapp packaging in dist target
plightbo
set the TLD URI to /webwork instead of webwork
plightbo
minor cleanup
henryhu
Add deployable_wars target in main build.xml
rgielen
Issue number: WW-986
rainerh
o webapps/starter/build not deleted while running clean target
plightbo
generates xwork source javadocs
tmjee
move the osbuild.xml import to before <path id="cp"> is defined, so <path id="cp"> will override osbuild.xml's "cp"
plightbo
don't include xwork-tiger in the classpaths when running tests
rgielen
Issue number: WW-971
rgielen
Issue number: WW-971
rgielen
Issue number: WW-971
rgielen
Issue number: WW-971
rgielen
Issue number: WW-971
tmjee
added force="true" to xdoclet's webdoclet task to force taglib.tld generation
  1. Prev
  2. 1
  3. 2
  4. 3
  5. 4
  6. Next