Ben Hale

Hey there @mateuszrzeszutek. We would be happy to accept such a contribution, although unlike YourKit it should be enabled via a service binding which contains connection information such as the...

@saturnism It will be an option for deploying Java applications, but likely not the most common way to do it. Over the years we've found that enterprise Java applications have...

Pulling from a Maven repository (typically Artifactory) is definitely on our radar. It’s already the most common way to push to Cloud Foundry (CI pipeline pushes to Artifactory, subsequent steps...

@saturnism https://github.com/cloudfoundry/build-system-buildpack The first cuts of both the `riff-buildpack-group` and the `java-buildpack-group` both contain this to optionally build from source.

@ctatineni The `build-system-buildpack` is built for use with [Cloud Native Buildpacks](https://buildpacks.io) and will not work straight out of the box with `knative`. There's a fair amount of work being done...

This was the result of nothing more than a version update? The `` declaration hasn't changed?

Correct @zmackie. This is properly located in each platform because only the platform can reliably examine source information before sanitizing it for build. An example of this is that each...

@stefanprodan I'll update to match your proposal.

@stefanprodan as I was implementing I was thinking about where `policy` should exist in the hierarchy and I was wondering what you thought about moving it under a `filterTags` level....

@squaremo I'd love to start engaging on the idea of source extensibility. We've got some experience in this subject and I think we can bring some alternative view points to...