Permalink
Switch branches/tags
Nothing to show
Commits on Aug 24, 2011
  1. Respect 'name' when generating pom <repositories>

    Previously, declaring a repositories closure in build.gradle as follows
    
        repositories {
            mavenRepo urls: 'http://maven.springframework.org/snapshot'
            mavenCentral()
            mavenRepo urls: 'http://maven.springframework.org/release'
            mavenRepo urls: 'http://maven.springframework.org/milestone'
        }
    
    would produce a <repositories> section in pom.xml (during `gradle
    generatePom`) as follows
    
      <repositories>
          <repository>
              <id>http://maven.springframework.org/snapshot</id>
              <url>http://maven.springframework.org/snapshot</url>
          </repository>
          <repository>
              <id>http://maven.springframework.org/release</id>
              <url>http://maven.springframework.org/release</url>
          </repository>
          <repository>
              <id>http://maven.springframework.org/milestone</id>
              <url>http://maven.springframework.org/milestone</url>
          </repository>
      </repositories>
    
    Per INT-2078, Maven 3 now raises warning-level log messages about the
    <id> values, such as:
    
        [WARNING] 'repositories.repository.id' must not contain any of these
        characters \/:"<>|?* but found / @ line 74, column 11
    
    Users may now create their repositories entries using the 'name'
    property, which will be translated to the <id> element during pom
    generation. For example,
    
        repositories {
            mavenRepo name: 's2-snapshot', urls: 'http://maven.springframework.org/snapshot'
            mavenCentral()
            mavenRepo name: 's2-release', urls: 'http://maven.springframework.org/release'
            mavenRepo name: 's2-milestone', urls: 'http://maven.springframework.org/milestone'
        }
    
    will now produce a <repositories> section as follows
    
      <repositories>
          <repository>
              <id>s2-snapshot</id>
              <url>http://maven.springframework.org/snapshot</url>
          </repository>
          <repository>
              <id>s2-release</id>
              <url>http://maven.springframework.org/release</url>
          </repository>
          <repository>
              <id>s2-milestone</id>
              <url>http://maven.springframework.org/milestone</url>
          </repository>
      </repositories>
    
    Issue: INT-2078, GRADLE-48
    cbeams committed Aug 24, 2011
Commits on Jun 15, 2011
  1. Upgrade to Gradle 1.0 M3

    cbeams committed Jun 15, 2011
Commits on Mar 13, 2011
  1. Add <repositories> section to generated poms

    Issue: GRADLE-48
    cbeams committed Mar 13, 2011
Commits on Jan 24, 2011
  1. Upgrade to Gradle 0.9.2 GA

    cbeams committed Jan 24, 2011
Commits on Jan 18, 2011
  1. Update Gradle wrapper to 0.9.1 GA

    cbeams committed Jan 18, 2011
Commits on Dec 22, 2010
  1. Update Gradle wrapper to 0.9 GA

    cbeams committed Dec 22, 2010
  2. Trigger pom generation on version change

    generatePom task now considers gradle.properties as an input
    for incremental build purposes.
    
    Prior to this change, one could change the project version
    in gradle.properties (as during a release), yet generatePom
    would remain UP-TO-DATE, because only changes to the classpath
    were considered as inputs to the incremental build.
    
    Now a change to gradle.properties will cause generatePom to
    fire, meaning all poms (root and child) will be updated with
    the new version.  In this way, generated poms will always
    remain in sync with the project version.
    cbeams committed Dec 22, 2010
Commits on Nov 22, 2010
Commits on Nov 19, 2010
  1. Add README (GRADLE-4)

    cbeams committed Nov 19, 2010
  2. Use null-safe operator to accommodate versionless deps

    `snapshotDependencyCheck` interrogates dependent modules to see if
    their versions are SNAPSHOTs.  Prior to this change, the build would
    fail if a dependency did not declare a version.  Now it will tolerate
    this.
    
    It is an uncommon use case, but spring-android has it because they
    compile against an exploded set of classfiles, which are inherently
    without version metadata.
    cbeams committed Nov 19, 2010
  3. GA releases deploy to both Maven Central and S2 repos (GRADLE-34)

    During `uploadArchives`, if the release type of the current version is
    GA (.RELEASE), bring up a second Gradle mavenDeployer and configure it
    to 'upload' to the filesystem based on the value of the
    mavenSyncRepoDir property.
    
    Prior to this change, *only* the filesystem upload happened for GA
    releases, meaning that they would not also be uploaded to
    http://maven.springframework.org/release, as should be the case.
    cbeams committed Nov 19, 2010
Commits on Nov 18, 2010
  1. Add EBR repository for aws.ant dependency

    A critcal fix, as 'uploadArchives' will not work without this
    on the buildscript classpath. It has only worked thus far
    because users including CI have had it cached locally
    cbeams committed Nov 18, 2010
Commits on Nov 17, 2010
  1. Return docbook logging to original settings

     *will* show details about parsing errors.
    regular output has again been suppressed as it's too verbose by default.
    cbeams committed Nov 17, 2010
Commits on Nov 16, 2010
  1. Expose docbook parsing errors to stderr

    Switch statement eliminated; was obsolete anyway.
    cbeams committed Nov 16, 2010
Commits on Nov 13, 2010
Commits on Nov 12, 2010
Commits on Nov 11, 2010
  1. Upgrade to latest Gradle snapshot

    Daemon updates:
    
        build_daemon branch has been merged into master and daemon
        unctionality is now opt-in instead of being on by default. Use the
        '--daemon' switch to enable; consider adding this to your alias
        configuration:
    
            alias gradle='$PWD./gradlew --daemon'
    
        Daemon functionality may also be enabled via system properties:
    
            ./gradlew -Dorg.gradle.daemon=true build
                - or -
            GRADLE_OPTS="-Dorg.gradle.daemon=true" ./gradlew build
    
    Eclipse metadata generation updates:
    
        `gradle eclipse` now generates JDT preferences under .settings,
        taking into account sourceCompatibilty and targetCompatibility
        properties.
    cbeams committed Nov 11, 2010
Commits on Nov 10, 2010
Commits on Nov 9, 2010
  1. Add publishSchema task

    cbeams committed Nov 9, 2010
  2. Pull in SI .gradle files

    Temporary measure as each gets factored out into a proper plugin
    cbeams committed Nov 9, 2010
  3. Ignore Vim swap files

    cbeams committed Nov 9, 2010
  4. Ignore .gradle directory

    cbeams committed Nov 9, 2010
  5. Ignore build directory

    cbeams committed Nov 9, 2010