Closed psx95 closed 1 year ago
Can you verify if
-srcs.jar
and-javadoc.jar
are generated appropriately for the raw component?
In the same location in the local .m2
repository, I can see exporter-auto-0.1.0-alpha-SNAPSHOT-javadoc.jar
& exporter-auto-0.1.0-alpha-SNAPSHOT-sources.jar
, looked at their contents and they looked appropriate.
One other thing that I suspect is a change required in how we determine if an artifact is release version here - Since the artifact ends with -shaded
here this would result in false, but I am not sure about this.
Thoughts ?
One other thing that I suspect is a change required in how we determine if an artifact is release version here - Since the artifact ends with
-shaded
here this would result in false, but I am not sure about this.Thoughts ?
The artifact ends with -shaded
but not the version (which is what that check cares about). I would guess that the logic doesn't need to be changed.
Supports #215
Currently, if
gradle.properties
haveshadowed
property set to true, then only shadowed variant is published, this change also configures the maven-publish plugin to publish normal Jar along with the shadow-jar.The
artifactId
is currently set to be thearchivesBaseName
which based on current configuration for auto-exporter should contain the suffix -shaded
.Testing
./gradlew clean build
Ran
./gradlew publishToMavenLocal
& verified that the.m2
repository contained both - shaded and non-shaded JARs.Generated artifacts through local publish
Below is the tree structure of the generated artifacts (from local
.m2
repo)JAR contents for sources JAR -
jar tf exporter-auto-0.1.0-alpha-SNAPSHOT-sources.jar
Verified that the sources and javadoc JARs are for the un-shaded variant.