build.gradle

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
remove website project

  1. … 62 more files in changeset.
Inlined the roadmap code now that it's sourced from the forum.

  1. … 2 more files in changeset.
Include the .htaccess file in the site.

Removed some old experimental stuff that is not used.

  1. … 2 more files in changeset.
add full install task that installs the site and all dependent repo.

Integrated new dynamic training data into site.

  1. … 2 more files in changeset.
- Changed Releases task type to include type of current release (release vs snapshot) in generated releases.xml - Changed website build to generate links based on the type of the current Gradle release, rather than the type of website build being performed. This means you can upload to gradle.org/latest for a real Gradle release, and get a much closer approximation of what will be uploaded to gradle.org.

  1. … 3 more files in changeset.
Some website changes: - Include link to migration guide and known issues for current release. - Include release date of each release. - Some style tweaks.

  1. … 3 more files in changeset.
fix html task inputs.

fix task dependencies for site upload.

Publish a version of the site with all file extension to local files removed, to hide that we are using PHP.

added some tasks for checking out the roadmap into the “installed” version of the site.

Renamed the status board to roadmap and added a link.

  1. … 3 more files in changeset.
- Added status flag to releases.xml, so we can mark certain releases as broken. - Updated the website build so that it understands about broken releases.

  1. … 4 more files in changeset.
Renamed the 'current release' -> 'current stable' so that it sticks better to the current situation with M4 and M3 :)

Added some very simple debug statements so that resolving a problem will be quicker next time.

Documented the tacit dependency. I'm not sure at the moment why website is not included in the settings.gradle. Maybe there is a reason for it?

Another battle with website links tests won! It should be now possible to run website tests regularly, against snapshot versions :D

Further fixes that enable running links tests against snapshot versions of our website

Fixed the script so that it is possible to run website tests against snapshot versions. This is yet another step towards automated deployment of snapshots/docs/test website.

- Publish docs for current release under /current on website, in addition to /releases/<version>. - Changed website to link to docs under /current.

  1. … 3 more files in changeset.
Build generates a releases.xml that lists all Gradle releases: - Use this to determine the next release version - Use this in GradleVersion instead of version.properties - Use this in the website instead of hardcoded list

  1. … 9 more files in changeset.
Updates to docs and website publishing for new website hosting infrastructure.

  1. … 6 more files in changeset.
Updates for 1.0-milestone-2

Updated links for repo, jira and wiki on the website.

  1. … 9 more files in changeset.
Updates for 1.0-milestone-1

Fail early in the build when uploadDocs is to be executed and no password has been specified.

  1. … 1 more file in changeset.
Updated to Ant 1.8.2 and Logback 0.9.28

  1. … 6 more files in changeset.
Some build script tidy-ups

Some fixes