Resolve group and name in Gradle non-workspace build

[Marc Schlegel]

I am working on a little PR for the kafka-clients module which currently doesnt provide OSGi metadata.

After applying the biz.aQute.bnd.builder which worked as expected. The last missing thing is the bsn which I would like to overwrite in the bnd-file. When using a Maven build I can write the following to resolve variables from Maven

Bundle-SymbolicName: ${project.groupId}.${project.artifactId}

I cannot find the documentation what the correct placeholder are for a non-workspace Gradle build. 

regards

Marc

[BJ Hargrave]

If you set the Bundle-Name header in the jar.manifest DSL, you will have full access to the Gradle project properties.

The Bnd Gradle plugin for non-workspace build does not make the Gradle project properties available to the Bnd Builder. Not sure if that is a good idea or not... Hmmm....

--
You received this message because you are subscribed to the Google Groups "bndtools-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bndtools-user...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

BJ

[BJ Hargrave]

You can pass any desire gradle properties into the Bnd Builder using the jar.manifest DSL.

jar {
    manifest {
        attributes('-groupid': group.toString(),
                   'artifactId': archivesBaseName)
    }
}

You can then reference those variables in your bnd file.

Bundle-SymbolicName: ${-groupid}.${artifactId}

Note: I used -groupid since that is the Bnd convention and it uses in the pom generation code as the groupId if not otherwise specified.

Many Gradle project/task properties have non-String values, while all Bnd properties are Strings. So it would require special handling to flatten them to Strings.

--

BJ

[Marc Schlegel]

As always, thank you very much BJ

Unfortunately in Kafka the group is specified within gradle.properties which is not yet set when creating the attributes. Currently it results in a bsn "build.kafka-clients" rather than "org.apache.kafka.kafka-clients". 

[BJ Hargrave]

Properties from gradle.properties are available during task configuration. So you can easily reference them in the jar task configuration.

[Marc Schlegel]

Found the mistake: I had to use project.group.toString() instead of just group.toString()

[BJ Hargrave]

Ah, yes, task.group is completely different :-)

[Marc Schlegel]

Well, PR is created [1]. Lets hope it gets accepted so I dont have to create some wrapping artifact :-)

Thanks again for the help and the nice documentation about the Gradle plugin

[1] https://github.com/apache/kafka/pull/2807

[BJ Hargrave]

So I ended up adding support for access to gradle properties in the bnd file. See https://github.com/bndtools/bnd/pull/1982

It was not as hard as I thought.

This will be in 3.4.