profile
viewpoint
Roberto Perez Alcolea rpalcolea @Netflix @nebula-plugins Los Gatos, CA http://blog.perezalcolea.info

desirable-objects/grails-sendgrid 10

Sendgrid plugin for Grails

rpalcolea/codemash-2018-presentation 2

Presentation for my talk "Real Time Traffic Visualization in a Microservices World" @ CodeMash 2018

rpalcolea/airbrake-grails 0

Airbrake Client for Grails

rpalcolea/artifactory-badge 0

Badge generator for Artifactory

rpalcolea/artifactory-client-java 0

Artifactory REST Client Java API bindings

rpalcolea/blog 0

rpalcolea's blog

rpalcolea/build-info 0

Artifactory's open integration layer for CI build servers

issue closednebula-plugins/gradle-ospackage-plugin

Minor: fix directory permissions in examples

The example provided in the wiki is misleading:

Directories

Specifies directory that should be created within package.

directory(String path, int permissions)

E.g.

directory('/some/dir')
directory('/some/dir', 644)

This won't be interpreted as octal. The example could be improved:

directory('/some/dir', 0644)

(See reported and closed bug: https://github.com/nebula-plugins/gradle-ospackage-plugin/issues/152)

closed time in 3 hours

gallardo

issue commentnebula-plugins/gradle-ospackage-plugin

Minor: fix directory permissions in examples

Hi! thanks for reporting this.

This should be fixed now in the example

gallardo

comment created time in 3 hours

GollumEvent
GollumEvent

created tagnebula-plugins/gradle-dependency-lock-plugin

tagv9.4.1

A plugin to allow people using dynamic dependency versions to lock them to specific versions.

created time in 4 days

release nebula-plugins/gradle-dependency-lock-plugin

v9.4.1

released time in 4 days

delete branch nebula-plugins/gradle-dependency-lock-plugin

delete branch : fix-platform-support

delete time in 4 days

push eventnebula-plugins/gradle-dependency-lock-plugin

Roberto Perez Alcolea

commit sha 940ef7d89e80ad3ca94cc2c49f72e5d87cea40cc

DependencyLockPlugin: lockConfiguration should change version via useVersion instead of useTarget

view details

Roberto Perez Alcolea

commit sha 8638c50b02007155859f14654fd4873a7aad0ca0

Merge pull request #198 from nebula-plugins/fix-platform-support DependencyLockPlugin: lockConfiguration should change version via useVersion instead of useTarget

view details

push time in 4 days

push eventnebula-plugins/gradle-nebula-integration

Roberto Perez Alcolea

commit sha a681f51d70b2001e756f82de39630f8fa67251b0

Merge branch 'master' of ssh://github.com/nebula-plugins/gradle-nebula-integration

view details

push time in 4 days

push eventnebula-plugins/gradle-nebula-integration

Roberto Perez Alcolea

commit sha 7fd3e1f121d808638870bd4c1ac493e7cde72e96

Merge branch 'master' of ssh://github.com/nebula-plugins/gradle-nebula-integration

view details

push time in 4 days

push eventnebula-plugins/gradle-nebula-integration

Roberto Perez Alcolea

commit sha ba96cea369a5497787df85465e2db528e1255605

Merge branch 'master' of ssh://github.com/nebula-plugins/gradle-nebula-integration

view details

push time in 4 days

push eventnebula-plugins/gradle-nebula-integration

Roberto Perez Alcolea

commit sha 0504b494c21de720ef60dcc87ca03f79c3aa1241

Create sample project that has issue with dependency locks + platform

view details

Roberto Perez Alcolea

commit sha 8992164fddf554834c6c7f8923cbe715d0f0d322

Merge branch 'master' of ssh://github.com/nebula-plugins/gradle-nebula-integration

view details

push time in 4 days

created tagnebula-plugins/gradle-info-plugin

tagv8.4.0

Plugin to gather information about the environment

created time in 9 days

release nebula-plugins/gradle-info-plugin

v8.4.0

released time in 9 days

delete branch nebula-plugins/gradle-info-plugin

delete branch : InfoJarManifestPlugin-ignore-info-properties-for-manifest-normalization

delete time in 9 days

push eventnebula-plugins/gradle-info-plugin

Roberto Perez Alcolea

commit sha a2e463a9473840ee9558d94ae0a66e45774c7ea3

InfoJarManifestPlugin: configure meta inf normalization to ignore gradle-info-plugin attributes

view details

Roberto Perez Alcolea

commit sha e85e1f144588ee543eefbd977c516b4decb3dfc0

Merge pull request #75 from nebula-plugins/InfoJarManifestPlugin-ignore-info-properties-for-manifest-normalization InfoJarManifestPlugin: configure meta inf normalization to ignore gradle-info-plugin attributes

view details

push time in 9 days

push eventnebula-plugins/gradle-info-plugin

Roberto Perez Alcolea

commit sha a2e463a9473840ee9558d94ae0a66e45774c7ea3

InfoJarManifestPlugin: configure meta inf normalization to ignore gradle-info-plugin attributes

view details

push time in 10 days

PR closed nebula-plugins/gradle-info-plugin

Reviewers
InfoJarManifestPlugin: introduce support for configuring MetaInfNormalization

The idea is to make the attributes configurable via InfoBrokerPlugin to avoid hardcoding values in the implementation. Thoughts?

+152 -9

1 comment

12 changed files

rpalcolea

pr closed time in 10 days

Pull request review commentnebula-plugins/gradle-info-plugin

InfoJarManifestPlugin: introduce support for configuring MetaInfNormalization

 class InfoJarManifestPlugin implements Plugin<Project>, InfoReporterPlugin {                     jarTask.manifest.attributes.putAll(attrs)                 }             }++            project.afterEvaluate {+                if(GradleKt.versionGreaterThan(project.gradle, "6.6-rc-1")) {+                    configureMetaInfNormalization(project)+                }+            }+         }     }++    @CompileDynamic+    private void configureMetaInfNormalization(Project project) {+        InfoBrokerPluginExtension extension = project.extensions.getByName('infoBroker') as InfoBrokerPluginExtension+        project.normalization.runtimeClasspath.metaInf(new Action<MetaInfNormalization>() {+            @Override+            void execute(MetaInfNormalization metaInfNormalization) {+                if(extension.ignoreManifestForNormalization.isPresent() && extension.ignoreManifestForNormalization.get()) {

I was thinking on a extension so people can decide what to do (like outside of the nebula context). But yeah you are right... this is info broker specific.

Should we have a list of what to ignore first then?

I'm thinking:

Build-Date: 2020-07-08_18:34:10 Built-OS Build-Number Build-Job `Build-Id

rpalcolea

comment created time in 10 days

PR opened nebula-plugins/gradle-info-plugin

Reviewers
InfoJarManifestPlugin: introduce support for configuring MetaInfNormalization

The idea is to make the attributes configurable via InfoBrokerPlugin to avoid hardcoding values in the implementation. Thoughts?

+152 -9

0 comment

12 changed files

pr created time in 10 days

push eventnebula-plugins/gradle-info-plugin

Roberto Perez Alcolea

commit sha 62ece924e56eb65a7fb7295789593ecaf30042f8

InfoJarManifestPlugin: introduce support for configuring MetaInfNormalization

view details

push time in 10 days

created tagnebula-plugins/nebula-release-plugin

tagv15.1.0

Release opinions based around gradle-git

created time in 12 days

release nebula-plugins/nebula-release-plugin

v15.1.0

released time in 12 days

push eventnebula-plugins/nebula-release-plugin

Roberto Perez Alcolea

commit sha 7bd20625b03c8927e3e728c20b6f3fa95a1bc2a0

immutable snapshots timestamp use YYYYMMddHHmm format

view details

push time in 12 days

push eventnebula-plugins/gradle-nebula-integration

Roberto Perez Alcolea

commit sha 975c495b43a2f4458aaedf6b48aa555e8b6f44ab

gradle-test-multi-configuration-pom: introduce TestMultiScopePomFunctionalTest.groovy

view details

push time in 12 days

release nebula-plugins/gradle-java-cross-compile-plugin

v4.3.0

released time in 12 days

created tagnebula-plugins/gradle-java-cross-compile-plugin

tagv4.3.0

Automatic configuration of bootstrap classpath for Java, Groovy and Kotlin.

created time in 12 days

delete branch nebula-plugins/gradle-java-cross-compile-plugin

delete branch : use-CompileOptions-release-property

delete time in 12 days

push eventnebula-plugins/gradle-java-cross-compile-plugin

Roberto Perez Alcolea

commit sha 09a338a81fb0ddf6f49d879eb33bbc6215f3627d

JavaCrossCompilePlugin: use CompileOption release property

view details

Roberto Perez Alcolea

commit sha a67b437ea2e6f88708aebb8c517649b31aa3bbf4

Merge pull request #17 from nebula-plugins/use-CompileOptions-release-property JavaCrossCompilePlugin: use CompileOptions release property

view details

push time in 12 days

Pull request review commentnebula-plugins/gradle-java-cross-compile-plugin

JavaCrossCompilePlugin: use CompileOption release property

 class JavaCrossCompilePlugin @Inject constructor(private val providerFactory: Pr                 val location by lazy { targetCompatibility.locate(project, providers) }                 withType(JavaCompile::class.java) {                     if (JavaVersion.current() >= JavaVersion.VERSION_1_9) {-                        it.options.compilerArgs.addAll(listOf("--release", targetCompatibility.majorVersion))+                        if (project.gradle.versionLessThan("6.6-rc-1")) {+                            it.options.compilerArgs.addAll(listOf("--release", targetCompatibility.majorVersion))+                        } else {+                            it.options.release.set(targetCompatibility.majorVersion.toInt())

use CompileOptions.release property with Gradle 6.6-rc-1 +

rpalcolea

comment created time in 12 days

Pull request review commentnebula-plugins/gradle-java-cross-compile-plugin

JavaCrossCompilePlugin: use CompileOption release property

 class JavaCrossCompilePluginIntegrationSpec extends IntegrationSpec {         writeHelloWorld('helloworld')          when:-        runTasks('--configuration-cache=on', 'compileJava')-        def result = runTasks('--configuration-cache=on', 'compileJava')+        runTasks('--configuration-cache', 'compileJava')+        def result = runTasks('--configuration-cache', 'compileJava')

feature flag for configuration cache changed between Gradle 6.5 and 6.6

rpalcolea

comment created time in 12 days

push eventnebula-plugins/gradle-nebula-integration

Roberto Perez Alcolea

commit sha 102e7b07a2b1912a1142c861b058b9f63f155d94

gradle-test-multi-configuration-pom: show scenario where a dependency is repeated in POM file and the last scope wins regardless of importance

view details

push time in 17 days

push eventnebula-plugins/gradle-resolution-rules-plugin

Roberto Perez Alcolea

commit sha 2b59c0e1d0c8d6c90b84bdd237568a13c1f2a40c

Gradle 6.6-rc-1

view details

push time in 18 days

issue commentgradle/gradle

Provide a configuration cache friendly way of looking up a subset of system properties

related to https://github.com/gradle/gradle/issues/13730 :)

Looking forward to see this introduced 👍

breskeby

comment created time in 18 days

issue closednebula-plugins/nebula-publishing-plugin

testcompile dependencies are not part of generated pom.xml from nebula maven publication

Apart from scope test, dependencies from compile and runtime are properly coming in generated pom.xml. Is there a way to include test dependencies as well? For some reason, have to use gradle 4.10.2, knowingly it is old now. can some one help me on this?

apply plugin: 'nebula.maven-publish'

group="gradle-lib-nexus" version="2.0"

dependencies { // This dependency is exported to consumers, that is to say found on their compile classpath. compile 'org.apache.commons:commons-math3:3.+'

// This dependency is used internally, and not exposed to consumers on their own compile classpath.
compile 'com.google.guava:guava:22.+'  // This looks good along with above one.

// Use JUnit test framework
 testCompile 'junit:junit:4.12'                 // **Not part of generated POM**

}

Deployment as: /* the below is for publishing individual artifacts */ publishing { repositories { maven { credentials { username "$nexusUser" password "$nexusPassword" } url "repo" } } }

POM contains: ( Need Junit dependency also to be added as scope test - is there a way ? ) <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"> <modelVersion>4.0.0</modelVersion> <groupId>gradle-lib-nexus</groupId> <artifactId>gradle-lib-nexus</artifactId> <version>2.0</version> <dependencies> <dependency> <groupId>com.google.guava</groupId> <artifactId>guava</artifactId> <version>22.0</version> <scope>compile</scope> </dependency> <dependency> <groupId>org.apache.commons</groupId> <artifactId>commons-math3</artifactId> <version>3.6.1</version> <scope>compile</scope> </dependency> </dependencies> <name>gradle-lib-nexus</name> <description/> </project>

closed time in 24 days

kalaiarasan231

issue commentnebula-plugins/nebula-publishing-plugin

testcompile dependencies are not part of generated pom.xml from nebula maven publication

Hi,

I don't think we have ergonomics in the plugin to publish those automatically. We usually recommend folks to publish common test libraries as another module or use Gradle Test Fixtures. More info in https://docs.gradle.org/current/userguide/java_testing.html#publishing_test_fixtures.

However, test fixtures are only available in Gradle 5.6+

We recommend that because the POM really only needs compile/runtime dependencies. Fixtures seem like a better fit for your use case

One thing that you could do is modify the XML yourself via gradle api and read the dependencies from the test configuration and attach them, but that would make your POM file to contain the test dependencies in there, so you have to make sure you add them with the test scope to avoid consumers pulling those automatically

I guess you could do something like this:

project.afterEvaluate {
    project.publishing {
        publications {
            withType(MavenPublication) {
                pom.withXml { XmlProvider xml ->
                    project.plugins.withType(JavaBasePlugin) {
                        def dependencies = xml.asNode()?.dependencies?.dependency
                        project.configurations.test.resolvedConfiguration.firstLevelModuleDependencies.each { dep ->
                            Node dependency = new Node(null, 'dependency')
                            dependency.appendNode('groupId', dep.moduleGroup)
                            dependency.appendNode('artifactId', dep.moduleName)
                            dependency.appendNode('version', dep.moduleVersion)
                            dependency.appendNode('scope', 'test')
                            dependencies.append(dependency)
                        }
                    }
                }
            }
        }
    }
}

I don't know if that will work but you can give it a shot. Notice that this will add all dependencies in the configuration... so this could be a huge number of them

Again, I'd recommend upgrade and start using Gradle Test Fixtures

I'll close this issue as there is nothing we can do on nebula publishing plugin side for this

kalaiarasan231

comment created time in 24 days

created tagnebula-plugins/gradle-dependency-lock-plugin

tagv9.3.0

A plugin to allow people using dynamic dependency versions to lock them to specific versions.

created time in 24 days

release nebula-plugins/gradle-dependency-lock-plugin

v9.3.0

released time in 24 days

delete branch nebula-plugins/gradle-dependency-lock-plugin

delete branch : exclude-pmd-from-global-locks

delete time in 24 days

push eventnebula-plugins/gradle-dependency-lock-plugin

Roberto Perez Alcolea

commit sha 813d48d5b11912a17865da997ba7ce4f522b051a

DependencyLockTaskConfigurer: add pmd to ignored configurations in global locks

view details

Roberto Perez Alcolea

commit sha fe53f61278057cf6fa2f0fc31f409db0fdba5f70

Merge pull request #196 from nebula-plugins/exclude-pmd-from-global-locks DependencyLockTaskConfigurer: add pmd to ignored configurations in global locks

view details

push time in 24 days

issue commentgradle/gradle

"error=7, Argument list too long" still an issue on osx / gradle 6.5

This appears to be a Kotlin issue and not a Gradle one.

You can follow the issue in https://youtrack.jetbrains.com/issue/KT-34487

It appears to be fixed in 1.4.M3

eboudrant

comment created time in 25 days

push eventnebula-plugins/nebula-bintray-plugin

Roberto Perez Alcolea

commit sha bb11a9ebf161d859e93fa53e44f89e71cb9f1a74

add test to make sure we can re-use configuration cache

view details

push time in 25 days

push eventnebula-plugins/gradle-java-cross-compile-plugin

Roberto Perez Alcolea

commit sha f2d41cde73485dc413facc5597552b3f828c1129

Add test to make sure we re-use configuration cache

view details

push time in 25 days

created tagnebula-plugins/gradle-java-cross-compile-plugin

tagv4.2.0

Automatic configuration of bootstrap classpath for Java, Groovy and Kotlin.

created time in 25 days

release nebula-plugins/gradle-java-cross-compile-plugin

v4.2.0

released time in 25 days

delete branch nebula-plugins/gradle-java-cross-compile-plugin

delete branch : use-configuration-cache

delete time in 25 days

push eventnebula-plugins/gradle-java-cross-compile-plugin

Roberto Perez Alcolea

commit sha 3b72ce18b7da82503ab6fcbfff41fd748f27286b

SDKManJDKPathProvider should use configuration cache to get user.home

view details

Roberto Perez Alcolea

commit sha 54cac9e8c23c1bfc1680c6e24fec0523862a5e75

Merge pull request #16 from nebula-plugins/use-configuration-cache SDKManJDKPathProvider should use configuration cache to get user.home

view details

push time in 25 days

created tagnebula-plugins/nebula-bintray-plugin

tagv8.5.0

Bintray Tasks

created time in 25 days

release nebula-plugins/nebula-bintray-plugin

v8.5.0

released time in 25 days

delete branch nebula-plugins/nebula-bintray-plugin

delete branch : use-configuration-cache

delete time in 25 days

push eventnebula-plugins/nebula-bintray-plugin

Roberto Perez Alcolea

commit sha a66dd548016454091d4c132c649e2056c28037b7

Use configuration cache (#48)

view details

push time in 25 days

push eventnebula-plugins/nebula-bintray-plugin

Roberto Perez Alcolea

commit sha 85fc16bf1527b505de3120b5987d56eac3616112

Use configuration cache

view details

push time in a month

push eventnebula-plugins/nebula-bintray-plugin

Roberto Perez Alcolea

commit sha 5e062fcc20bb3e63b1f134ea4fdcec2781695cbc

Use configuration cache

view details

push time in a month

create barnchnebula-plugins/nebula-bintray-plugin

branch : use-configuration-cache

created branch time in a month

push eventnebula-plugins/gradle-java-cross-compile-plugin

Roberto Perez Alcolea

commit sha 3b72ce18b7da82503ab6fcbfff41fd748f27286b

SDKManJDKPathProvider should use configuration cache to get user.home

view details

push time in a month

issue openedgradle/gradle

ProviderFactory should support reading all `systemProperties` and `environmentVariables

While looking into Configuration Cache - Undeclared reading of system properties and Configuration Cache - Undeclared reading of environment variables I found that there is no way to read al properties in a safe manner.

It is recommended to use

def enabled = providers.environmentVariable("SOME_ENV_VAR").forUseAtConfigurationTime().present

However, we have cases where we read all system or environment properties for reporting in Gradle plugins. Example build file:

apply plugin: MyPlugin

class MyPlugin implements Plugin<Project> {
    static final String OVERRIDE_PROPERTY_PREFIX = 'override.'

    @Override
    void apply(Project project) {
        def overrideProperties = System.properties.findAll { it.key.startsWith(OVERRIDE_PROPERTY_PREFIX) }
        overrideProperties.collectEntries { key, value -> [key - OVERRIDE_PROPERTY_PREFIX, value] }
    }
}

When System.properties is invoked, it produces several configuration cache warnings and fails the build:

44 configuration cache problems were found.
- unknown location: read system property 'java.runtime.name' from class 'MyPlugin'
  See https://docs.gradle.org/6.5.1/userguide/configuration_cache.html#undeclared_sys_prop_read
  See https://docs.gradle.org/6.5.1/userguide/configuration_cache.html#undeclared_sys_prop_read
- unknown location: read system property 'java.vm.vendor' from class 'MyPlugin'

Another use case: https://github.com/nebula-plugins/gradle-metrics-plugin/blob/28b59df6d4ffc5538ce7e62ebd9087b0f909b65f/src/main/java/nebula/plugin/metrics/model/Info.java#L51

I couldn't find anything related to read all env. variables/system properties in nightly docs also: https://docs.gradle.org/nightly/userguide/configuration_cache.html#undeclared_env_var_read

Since there are cases where reporting multiple properties by prefix or just not knowing all potential properties is quite common, are there plans to add something to ProviderFactory to enable this?

created time in a month

created tagnebula-plugins/gradle-info-plugin

tagv8.3.2

Plugin to gather information about the environment

created time in a month

release nebula-plugins/gradle-info-plugin

v8.3.2

released time in a month

push eventnebula-plugins/gradle-info-plugin

Roberto Perez Alcolea

commit sha 7cbb094a1c325ef7bd70c3e0ff727e06271cbd9e

Revert "Remove usage of Provider..forUseAtConfigurationTime() to make it compatible with gradle 6.x"

view details

Roberto Perez Alcolea

commit sha ffd85d655baf6cd0d7015c1754648eb9e007295a

Merge pull request #73 from nebula-plugins/revert-72-remove-forUseAtConfigurationTime Revert "Remove usage of Provider..forUseAtConfigurationTime() to make it compatible with gradle 6.x"

view details

push time in a month

delete branch rpalcolea/gradle

delete branch : 13701/fix-SystemPropertyCallSite-call

delete time in a month

PR opened gradle/gradle

Instrumented: handle cases where arguments are null when getting system properties

Fixes https://github.com/gradle/gradle/issues/13701

Context

https://github.com/gradle/gradle/pull/13585/files changed the way arguments are casted to String in order to fix support for GString. However, there are cases where the value provided is null and .toString() would throw a null pointer exception. Example:

task printMyHost {
    doFirst {
        def myHost = System.getProperty('myhost', findProperty('myhost'))
        println "MY HOST: " + myHost
    }
}

* Where:
Build file '/Users/rperezalcolea/Projects/github/nebula-plugins/gradle-nebula-integration/system-property-issue/build.gradle' line: 3

* What went wrong:
Execution failed for task ':myTask'.
> java.lang.NullPointerException (no error message)

* Try:
Run with --info or --debug option to get more log output. Run with --scan to get full insights.

Caused by: java.lang.NullPointerException
        at org.gradle.internal.classpath.Instrumented$SystemPropertyCallSite.call(Instrumented.java:435)
        at build_ez40ldtqk6rt0k1epnvu1r9ev$_run_closure1$_closure2.doCall(/Users/rperezalcolea/Projects/github/nebula-plugins/gradle-nebula-integration/system-property-issue/build.gradle:3)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at org.gradle.api.internal.AbstractTask$ClosureTaskAction.execute(AbstractTask.java:669)
        at org.gradle.api.internal.AbstractTask$ClosureTaskAction.execute(AbstractTask.java:642)
        at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter$3.run(ExecuteActionsTaskExecuter.java:569)
        at org.gradle.internal.operations.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:395)
        at org.gradle.internal.operations.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:387)
        at org.gradle.internal.operations.DefaultBuildOperationExecutor$1.execute(DefaultBuildOperationExecutor.java:157)
        at org.gradle.internal.operations.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:242)
        at org.gradle.internal.operations.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:150)
        at org.gradle.internal.operations.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:84)
        at org.gradle.internal.operations.DelegatingBuildOperationExecutor.run(DelegatingBuildOperationExecutor.java:31)

Contributor Checklist

Gradle Core Team Checklist

  • [ ] Verify design and implementation
  • [ ] Verify test coverage and CI build status
  • [ ] Verify documentation
  • [ ] Recognize contributor in release notes
+26 -7

0 comment

2 changed files

pr created time in a month

create barnchrpalcolea/gradle

branch : 13701/fix-SystemPropertyCallSite-call

created branch time in a month

push eventnebula-plugins/gradle-nebula-integration

Roberto Perez Alcolea

commit sha edbb32768c0eedf5125abbbcf354561bfbdbf7d6

add system-property-issue

view details

Roberto Perez Alcolea

commit sha 0de7f91da3b965719720ac6d5ee9f4c01dcb52be

Merge branch 'master' of ssh://github.com/nebula-plugins/gradle-nebula-integration

view details

push time in a month

issue openedgradle/gradle

SystemPropertyCallSite.call regression in Gradle 6.5.1

Hi folks,

Giving this build file:

task printMyHost {
    doFirst {
        def myHost = System.getProperty('myhost', findProperty('myhost'))
        println "MY HOST: " + myHost
    }
}

When executing the task in 6.5, we can see the following:

./gradlew myTask                                                                                                                                ✔  took 9s   10338  at 18:05:39   11.0.7+10 

> Task :myTask
MY HOST: null

BUILD SUCCESSFUL in 738ms
1 actionable task: 1 executed

However, with Gradle 6.5.1, we get the following exception:

* Where:
Build file '/Users/rperezalcolea/Projects/github/nebula-plugins/gradle-nebula-integration/system-property-issue/build.gradle' line: 3

* What went wrong:
Execution failed for task ':myTask'.
> java.lang.NullPointerException (no error message)

* Try:
Run with --info or --debug option to get more log output. Run with --scan to get full insights.

Caused by: java.lang.NullPointerException
        at org.gradle.internal.classpath.Instrumented$SystemPropertyCallSite.call(Instrumented.java:435)
        at build_ez40ldtqk6rt0k1epnvu1r9ev$_run_closure1$_closure2.doCall(/Users/rperezalcolea/Projects/github/nebula-plugins/gradle-nebula-integration/system-property-issue/build.gradle:3)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at org.gradle.api.internal.AbstractTask$ClosureTaskAction.execute(AbstractTask.java:669)
        at org.gradle.api.internal.AbstractTask$ClosureTaskAction.execute(AbstractTask.java:642)
        at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter$3.run(ExecuteActionsTaskExecuter.java:569)
        at org.gradle.internal.operations.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:395)
        at org.gradle.internal.operations.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:387)
        at org.gradle.internal.operations.DefaultBuildOperationExecutor$1.execute(DefaultBuildOperationExecutor.java:157)
        at org.gradle.internal.operations.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:242)
        at org.gradle.internal.operations.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:150)
        at org.gradle.internal.operations.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:84)
        at org.gradle.internal.operations.DelegatingBuildOperationExecutor.run(DelegatingBuildOperationExecutor.java:31)

I suspect this is related to this change introduced in 6.5.1: https://github.com/gradle/gradle/pull/13585/files

created time in a month

issue commentnebula-plugins/gradle-ospackage-plugin

8.4.0 produces "corrupt" tar files in deb packages

Hi!

Thanks for bringing this up

We rolled back the change and released 8.4.1

linsomniac

comment created time in a month

PR merged nebula-plugins/gradle-ospackage-plugin

Reviewers
Revert "feat(jdeb): enable long filename support"

This reverts commit 6c36b7bfa889bc772d7219be3c106615ab51dffc.

+0 -1

0 comment

1 changed file

chali

pr closed time in a month

created tagnebula-plugins/gradle-ospackage-plugin

tagv8.4.1

Gradle plugin for constructing linux packages, specifically RPM and DEBs.

created time in a month

release nebula-plugins/gradle-ospackage-plugin

v8.4.1

released time in a month

push eventnebula-plugins/gradle-ospackage-plugin

Martin Chalupa

commit sha db99fa111bdb9b76b7583de3a2093ac1d360f90e

Revert "feat(jdeb): enable long filename support" This reverts commit 6c36b7bfa889bc772d7219be3c106615ab51dffc.

view details

Roberto Perez Alcolea

commit sha 288469e18b9efcda7250fa7079e8d977836c3f53

Merge pull request #379 from chali/Revert Revert "feat(jdeb): enable long filename support"

view details

push time in a month

push eventnebula-plugins/nebula-test

Roberto Perez Alcolea

commit sha 4751167a716f7869736be78054485095c56d919a

Gradle 6.5.1

view details

push time in a month

push eventnebula-plugins/nebula-release-plugin

Roberto Perez Alcolea

commit sha a24ad2dc1808b27d1094a9cd939215f360fdbebb

Gradle 6.5.1

view details

push time in a month

push eventnebula-plugins/nebula-publishing-plugin

Roberto Perez Alcolea

commit sha 08cc3031e6d1fec6a764bed45ba4b48158767b39

Gradle 6.5.1

view details

push time in a month

push eventnebula-plugins/nebula-project-plugin

Roberto Perez Alcolea

commit sha 0402703aa17bb977cb0cd3c0cc25dba2d8a1924b

Gradle 6.5.1

view details

push time in a month

push eventnebula-plugins/nebula-plugin-plugin

Roberto Perez Alcolea

commit sha 36db6addaf20fa7f559925246f942492bd47ab26

Gradle 6.5.1

view details

push time in a month

push eventnebula-plugins/nebula-node-plugin

Roberto Perez Alcolea

commit sha a24be04a915096a00f5bd9db19025f5d3e7c394c

Gradle 6.5.1

view details

push time in a month

push eventnebula-plugins/nebula-kotlin-plugin

Roberto Perez Alcolea

commit sha 764b20bc911e9f81fd672e0dd1e352fd12293542

Gradle 6.5.1

view details

push time in a month

push eventnebula-plugins/nebula-hollow-plugin

Roberto Perez Alcolea

commit sha 53bd9aeee4fa3a6ece0c98e1d7de5d18d56a800d

Gradle 6.5.1

view details

push time in a month

push eventnebula-plugins/nebula-grails-plugin

Roberto Perez Alcolea

commit sha 4447b6538c2ecd29d3c244b1441fd74208ad7571

Gradle 6.5.1

view details

push time in a month

more