chrisdoyle / gradle-fury Goto Github PK

Ugh running into issues on develop now and wanted to define a few requirements as i understand them

gradlew clean build

• no gpg signatures
• apk's signed as normal

gradlew build

• no gpg signatures
• apk's signed as normal

gradlew install

• no gpg signatures
• apk's signed as normal
• publish to maven local
• pom's are generated

on a SNAPSHOT built, with publish URL defined
gradlew publish

• gpg signatures generated if possible
• sha1 and md5 hashes generated
• apk's signed as normal
• publish to maven local
• pom's are generated
• files are uploaded to the repo

on a SNAPSHOT built, withOUT publish URL defined
gradlew publish

• gpg signatures generated if possible
• sha1 and md5 hashes generated
• apk's signed as normal
• publish to maven local
• pom's are generated

on a RELEASE built, with publish URL defined
gradlew publish

• gpg signatures generated if possible on all artifacts
• sha1 and md5 hashes generated
• apk's signed as normal
• publish to maven local
• pom's are generated
• files are uploaded

is this correct?

I have a use case with a multimodule project that has mixed licenses depending on the module. What are my options?

We're missing the URL field....

<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
....
<url>https://github.com/osmdroid/osmdroid</url>
....
</project>

In order to avoid confusion, we should add docs and a message of the day to remind people to apply fury first, then override their settings as needed

definitely does not publish with 1.5.0 or 2.0.0, they must have changed something

//memory leak testing
debugCompile 'com.squareup.leakcanary:leakcanary-android:1.4-beta2'
releaseCompile 'com.squareup.leakcanary:leakcanary-android-no-op:1.4-beta2'
testCompile 'com.squareup.leakcanary:leakcanary-android-no-op:1.4-beta2'

this might be useful

http://stackoverflow.com/questions/28832144/how-to-turn-on-console-output-in-android-unit-tests

Support a "name" pom element for all child modules
Need to mediate gradle's wild card syntax for versioning to maven's syntax

especially the android artifacts with variants from both gradle and maven

From the Gradle documentation:
Chapter 42. Initialization Scripts

Specifically, I'd like to illustrate:

• defining a global Maven repository configuration
• ensuring that only a specified repository is used when running the build
• mimicking the standard deployment behavior which Maven provides via server and repository configuration in settings.xml and the project POM (oh, how I miss thee...)

depends on the merge of #42 and #53 (due to the similarity of the verify script)

#43

ugh

JAR projects with a build.gradle properties as the following

dependencies {
    compile "org.apache.commons:commons-lang3:${project.property('commons-lang3.version')}"
    runtime 'com.esotericsoftware:kryo:4.0.0'
    testCompile "junit:junit:${project.property('junit.version')}"
}

Produces

<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <modelVersion>4.0.0</modelVersion>
  <groupId>com.chrisdoyle</groupId>
  <artifactId>hello-world-lib</artifactId>
  <version>1.0.7-SNAPSHOT</version>
  <dependencies>
    <dependency>
      <groupId>com.esotericsoftware</groupId>
      <artifactId>kryo</artifactId>
      <version>4.0.0</version>
      <scope>runtime</scope>
    </dependency>
    <dependency>
      <groupId>org.apache.commons</groupId>
      <artifactId>commons-lang3</artifactId>
      <version>3.4</version>
      <scope>runtime</scope>
    </dependency>
  </dependencies>
  <packaging>jar</packaging>
</project>

Note that we're missing name and description, both dependencies are listed as runtime and it's missing all the test dependencies.

Currently pom's for war projects are marked as JARs and only a jar is published. Obviously wrong.

Maven had this great feature to skip publication either always or when a certain condition is met. would be useful here to prevent publishing artifacts that aren't needed

It'd be nice to have a simple "Applying GradleFury to module" or some other kind of visual indicator during the build to know it's doing something.

trying to import into a folk for osmdroid.

getting

java.lang.IllegalStateException: buildToolsVersion is not specified.

```
```

must be useful to have the source repositories listed for any dependencies

Right now it rings in the configure phase of gradle's life cycle which means signing happens before compiler or anything else. We need to find another way to do this that enables a single step publishing

need to make sure this still works

Just an idea for a neat feature. If you develop offline and use maven to sync you local repo/nexus to the public Internet you probably make a dummy pom then manually copy your gradle project dependences into a pom. It would be awesome if we can exploit gradle fury's pom work to generate a dummy pom containing all child projects' deps.

kind of strange, i end up with

module/com/chrisdoyle/.... etc

it would be useful to store the generated pom's in the build folder for people construction distribution packages with pom's + output artifacts

compileSdkVersion 'Google Inc.:Google APIs:23'

add the equivalent of filtered sources that contains a build time generated timestamp. useful for verifying that the uploaded signature was actually from the same source. this may require disconnecting the 'publish' task from 'build'

build the sample project, then verify that the artifacts are published to a repo

This should be implemented similar to how support is built-in to accommodate multiple developers.

currently uploaded as -pom.asc instead of .pom.asc

is it possible to supply signing certificates and nexus u/p via the command line?

Oh, Gradle...

The POM generation task shall accurately capture both <scope /> and <classifier /> values in the <dependency /> declarations. I found a rather disheartening post related to the subject:

https://discuss.gradle.org/t/maven-publish-plugin-generated-pom-making-dependency-scope-runtime/7494

This ticket is an attempt to "Use the 'pom.withXml' hook to fix the dependency scopes as needed" method as a "solution", as proposed in Mr. Niederwieser's response. Sigh.

http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-gpg-plugin/src/main/java/org/apache/maven/plugin/gpg/GpgSigner.java

Hey!

I cloned the repo and ran gradle build publishToMavenLocal in order to see how it works and whether it fits my needs or not. It installed the artefacts into local repo well though I discovered that hello-world-aar's pom.xml file did not have dependencies specified. Is it so intentionally? Is it something that is okay for an AAR?

Wondering because there are dependencies for hello-world-lib module which a JAR file... I expected the AAR to have it too?

Cheers, Pavlo

I'm trying to switch osmdroid over to this library and in the gradle.properties file, minSdkVersion is 8, however several modules require a higher minSdkVersion and have declared that in the build.gradle file. The module looks like ( just the relevant parts)

android {
    compileSdkVersion 'Google Inc.:Google APIs:23'
    buildToolsVersion "23.0.2"

    defaultConfig {
        applicationId "org.osmdroid.google.sample"
        minSdkVersion 9
        testInstrumentationRunner "android.support.test.runner.AndroidJUnitRunner"

    }
    buildTypes {
        release {
            minifyEnabled false
            proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
        }
    }
    lintOptions {
        abortOnError false
    }
}

gradle.properties looks like this

android.buildToolsVersion=23.0.2
android.compileSdkVersion=23
android.minSdkVersion=8
android.targetSdkVersion=23

build output

:GoogleWrapperSample:processDebugManifest
/Users/xxxx/osmdroid/GoogleWrapperSample/src/main/AndroidManifest.xml:4:5-73 Error:
    uses-sdk:minSdkVersion 8 cannot be smaller than version 9 declared in library [com.google.android.gms:play-services:8.4.0] /Users/xxxx/osmdroid/GoogleWrapperSample/build/intermediates/exploded-aar/com.google.android.gms/play-services/8.4.0/AndroidManifest.xml
    Suggestion: use tools:overrideLibrary="com.google.android.gms.all" to force usage

See http://g.co/androidstudio/manifest-merger for more information about the manifest merger.

:GoogleWrapperSample:processDebugManifest FAILED

I'm willing to bet the root cause is the lack of an extra if (!defined) type of check for minSdkVersion.

Just ensure that all the artifacts are publishing correctly