-
Task
-
Resolution: Unresolved
-
Neutral
-
None
-
None
-
None
-
-
Empty show more show less
-
Empty show more show less
As mentioned in the Maven Release plugin docs
sdfs
Maven 3 (and previously 2) provides a default release profile named release-profile that builds and attaches source and javadoc jar: this is defined in the super POM. This profile is activated by default during release:perform with Maven Release Plugin 2.x, unless deactivated by configuring useReleaseProfile parameter to false.
[...]
In order to prepare for Maven 4, each project will instead require to define their own release profile that they'll be able to customise to match their needs.
Turns out that profile in Maven's Super POM didn't do anything too fancy re: sources and javadoc, but just these:
<profiles> <!-- NOTE: The release profile will be removed from future versions of the super POM --> <profile> <id>release-profile</id> <build> <plugins> <plugin> <inherited>true</inherited> <artifactId>maven-source-plugin</artifactId> <executions> <execution> <id>attach-sources</id> <goals> <goal>jar-no-fork</goal> </goals> </execution> </executions> </plugin> <plugin> <inherited>true</inherited> <artifactId>maven-javadoc-plugin</artifactId> <executions> <execution> <id>attach-javadocs</id> <goals> <goal>jar</goal> </goals> </execution> </executions> </plugin>
Acceptance criteria