vaadin-framework

歷史記錄

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

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