Toolkit should be able to upload maven generated jar

[yunus]

When I want to upload a Lambda function via Eclipse AWS toolkit, the outcome becomes different than maven created jar. I place the log4j.properties file under sr/main/resources and only if I use “mvn package”, Lambda runtime picks it. If I use Eclipse toolkit, log4j.properties remains under Resources folder and lambda runtime is not able to find it. Is there a way to order eclipse toolkit only upload maven generated Jar?

[ksclarke]

+1

[tvand]

+1 Generally, the package created by the Eclipse plugin seems to consider the settings from pom.xml, but is one directoy level off. Because of the problem mentioned above, I put log4j2.xml into /src/main/java and added

<resource>
    <directory>${basedir}/src/main/java</directory>
    <includes>
        <include>log4j2.xml</include>
    </includes>
</resource>

to pom.xml, which resulted in log4j2.xml being copied to the /java-subdirectory in the Lambda package

[mynameisgv]

+1. It uploads a zip file and makes it difficult to debug between local and lambda runtime.