How to build WebLaF binaries

Mikle edited this page Sep 14, 2016 · 7 revisions

Step 1: Download source code

First of all you will need to get WebLaF sources - you can do that using various GitHub features or by downloading sources ZIP archive from the latest release: https://github.com/mgarin/weblaf/releases

Step 2: Install ANT

You will find build.xml file inside project's build folder - this is an ANT build script that can build any of distributions that are available on site (and even some additional ones).

To run this build script you will either need to install ANT or use some modern IDE that includes ANT - here are Intellij IDEA and NetBeans official instructions to run ANT scripts.

Step 3: Use ANT targets

Separate artifact targets

  • build.core.jar - build weblaf-core-x.xx.jar
  • build.ui.jar - build weblaf-ui-x.xx.jar
  • build.weblaf.jar - build weblaf-x.xx.jar
  • build.weblaf.complete.jar - build weblaf-complete-x.xx.jar
  • build.weblaf.demo.jar - build weblaf-demo-x.xx.jar
  • build.npe.jar - build ninepatch-editor-x.xx.jar
  • build.sources.zip - build weblaf-src-x.xx.zip
  • build.sources.jar - build weblaf-src-x.xx.jar
  • build.javadoc.jar - build weblaf-javadoc-x.xx.jar

Complex targets

  • build.all.artifacts - build all WebLaF binaries, default target
  • build.common.artifacts - build common WebLaF binaries
  • build.release.artifacts - build release WebLaF binaries
  • build.base.artifacts - build separate WebLaF binaries
  • build.complete.artifacts - build single WebLaF binaries
  • build.featured.artifacts - build featured WebLaF binaries
  • build.misc.artifacts - build miscellaneous WebLaF binaries

Other targets are used to perform various operations required to build artifacts. I doubt you will need them at all.


Configuring build

You can also find build.properties file inside the build folder - it contains various properties which you might want to change to redirect the output, rename jars or something else. Make sure you know what you are doing, before changing anything there.

Anyway, you always can get a new version of the sources from the GIT if you break something ;)