| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
For ease of development, GWT "trunk" and "tools" are assumed to be
checked out in a directory parallel to the project directory. Otherwise,
the variable gwt.root can be used to give the location of trunk.
Add Ivy dependencies for servlet API and libraries needed to compile
tests (Jetty, Apache Commons) - these were previously used from GWT
JARs.
|
|
|
|
|
|
|
|
| |
Build vaadin.jar that contains the contents of gwt-user.jar, gwt-dev.jar
and gwt-codeserver.jar in addition to Vaadin itself.
The property gwt.root must be defined and point to a GWT trunk branch
check-out. The tools branch should be checked out in a directory next to
it.
|
|
|
| |
be consistent
|
| |
|
|
|
|
| |
Targets related to Ivy configuration are now in separate common.xml file
which is imported to main build files.
|
| |
|
|
|
|
|
| |
Included first version of Ant based replacement of old vaadin-server.py
demo server launch script.
|
|
|
|
|
|
|
|
|
|
| |
Patched SmartSprites jar is now fetched using Ivy tooling.
Custom dependency resolver is used to retrieve module description
from local filesystem (in project hierarchy) and the master artifact
from Vaadin (6.x) SVN repository.
This is a temporary solution until required patches get contributed and
committed back to SmartSprite upstream and artifacts are available in
Maven central.
|
|
|
|
| |
Transitively resolved thru gwt-user didn't fetch both classes and
source correctly.
|
|
|