You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After multiple tests, current situation is:
The elastic-apm-agent pom.xml has two related plugins involved with the source jar build-
the maven-source-plugin is invoked at the prepare-package phase
the maven-shade-plugin creates a source jar with the shaded sources
I am not entirely sure the first is required here, it is required for the attach source jar.
Invoking the exact same command as invoked by Jenkins - ./mvnw clean install -DskipTests=true -Dmaven.javadoc.skip=true creates the jar as expected. However, on Jenkins, the jar is created only with the shaded sources and without our sources (at least - this is what gets stored for the build artifacts).
The text was updated successfully, but these errors were encountered:
Doing some other task that required me to unarchive and look into jars reminded me this was never fixed.
The issue also affects our Javadoc jar. Both it and the sources jar only contain the co.elastic.apm.agent.premain package.
Maybe time to look into this.
After multiple tests, current situation is:
The elastic-apm-agent pom.xml has two related plugins involved with the source jar build-
prepare-package
phaseI am not entirely sure the first is required here, it is required for the attach source jar.
Invoking the exact same command as invoked by Jenkins -
./mvnw clean install -DskipTests=true -Dmaven.javadoc.skip=true
creates the jar as expected. However, on Jenkins, the jar is created only with the shaded sources and without our sources (at least - this is what gets stored for the build artifacts).The text was updated successfully, but these errors were encountered: