Amazon Lambda HTTP native image failure archetype fix

[oztimpower]

Fix #13692

Native image failure to build archetype

Reproduce:

mvn archetype:generate \
       -DarchetypeGroupId=io.quarkus \
       -DarchetypeArtifactId=quarkus-amazon-lambda-http-archetype \
       -DarchetypeVersion=1.10.3.Final

mvn package -Pnative

Removing fat jar resolves:

  <plugin>
     <groupId>io.quarkus</groupId>
      <artifactId>quarkus-maven-plugin</artifactId>
       <version>${quarkus-plugin.version}</version>

        <configuration>
             <uberJar>true</uberJar>
         </configuration>

    </plugin>

[ghost]

Thanks for your pull request!

The title of your pull request does not follow our editorial rules. Could you have a look?

• title should not contain an issue number (use 'Fix Allow * expression for quarkus:add-extension #1234' in the description instead)

This message is automatically generated by a bot.

[patriot1burke]

@oztimpower Please resolve conflicts. Thanks for fix.

[gsmet]

@patriot1burke is it good for you now? Looks like something that I should backport to 1.10.4.Final that I will release this afternoon.

[gsmet]

@oztimpower and just to be sure, we can deploy lambdas that are not fat jars?

[oztimpower]

The runner jar is built as a Uber jar no matter what, the Pom doesn’t need to specifying it anymore. The corresponding amazon-lambda extension doesn’t require Uber jar in the Pom anymore.

The issue that I observed was that with the legacy Uber jar set it was renaming the jar, adding an original extension to the file name which prevented it being found for native image. The jar that is deployed is not this one, it is the runner, so no, the change has no effect - a fat jar, the runner is deployed to Amazon Lambda, not the original.

[patriot1burke]

Hmmm, I thought I changed this so that fat jar isn't required.

[oztimpower]

Yes that’s what I was trying to say. Fat jar manually specified is no longer required - it was legacy in the Pom (and could be removed).