vaadin-framework

History

Leif Åstrand 9015ff64aa Find compiled classes from default Eclipse location Also set a value default to the work.dir property		11 years ago
..
bin	Merged 6.8 branch	12 years ago
cssoptimizer	Removed svn:executable property to avoid problems with Git on Windows	12 years ago
ivy	Support running TestBench tests with the vaadin-uitest war (#9299)	11 years ago
javadoc	Upgrade build.xml for Java 1.6	12 years ago
maven	[merge from 6.7] #8311 Converted CRLF -> LF in css/html/xml files	12 years ago
package	Created separate build.xml files for each module (#9299)	11 years ago
GWT-VERSION.properties	Integrate GWT build with Vaadin - first step.	12 years ago
VERSION.properties	Updated version to 7.0.0	12 years ago
VaadinApache2LicenseForJavaFiles.txt	#7354 IT Mill -> Vaadin find and replace	12 years ago
build.properties	Upgrade build.xml for Java 1.6	12 years ago
build.xml	Renamed sass -> theme-compiler for consistency (#9299)	11 years ago
common.xml	Use JarJar from Ivy (#9299)	12 years ago
html-style.properties	#7381 Packaging changes for Vaadin 6.7: JAR and test WAR only, no demo WAR nor ZIP; some cleanup (files that were in ZIP, build.xml)	13 years ago
ide.xml	Find compiled classes from default Eclipse location	11 years ago
readme.txt	#7381 Include licensing related files and release notes in JARs, removed an obsolete readme.txt	13 years ago

How to build Vaadin Framework
=============================

Building the distribution packages is as easy as running ant without 
parameters in this directory. While as official packages will be built
with Java 1.5, you can force build with 1.6 by adding the option 
-Dignoreversion=1

Some of the most common targets to build:
- Distribution JAR-file will be built with target package-jar
- Test WAR will be built with target package-war

For more detailed info, see build.xml

readme.txt