Add support for binaries in the java11 standard buildpath

[loosebazooka]

Currently, artifacts are presumed to be jars and processed according (inspected). This feature request is to allow non-jar artifacts as long as the user has defined a custom entrypoint in the app.yaml.

• app entrypoint parsing (Add entrypoint extraction to AppYaml parser #839)
• support binary buildpath in staging (Add binary path to staging #842)

[loosebazooka]

@ludoch FYI

[loosebazooka]

Testing instructions

1. clone repo
2. ./mvnw clean install
3. modify pom config for app-maven-plugin in test app

<plugin>
    <groupId>com.google.cloud.tools</groupId>
    <artifactId>appengine-maven-plugin</artifactId>
    <version>2.2.0</version>
    <dependencies>
        <dependency>
            <groupId>com.google.cloud.tools</groupId>
            <artifactId>appengine-plugins-core</artifactId>
            <version>0.8.3-SNAPSHOT</version>
        </dependency>
    </dependencies>
</plugin>

[ludoch]

Tested with a Quarkus native application. Ship it. Please update the plugin doc so the feature is easy to discover with Graal-VM native image binaries.

…

On Thu, Jun 18, 2020 at 7:12 AM Appu ***@***.***> wrote: Testing instructions 1. clone repo 2. ./mvnw clean install 3. modify pom config for app-maven-plugin in test app <plugin> <groupId>com.google.cloud.tools</groupId> <artifactId>appengine-maven-plugin</artifactId> <version>2.2.0</version> <dependencies> <dependency> <groupId>com.google.cloud.tools</groupId> <artifactId>appengine-plugins-core</artifactId> <version>0.8.3-SNAPSHOT</version> </dependency> </dependencies> </plugin> — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#840 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAATRTKY4UADZCFEXGBUC5DRXIOEBANCNFSM4N5AY3OQ> .