Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
We have defined maven-site-plugin:attach-descriptor in build/plugins
It cause to every ASF projects have execute this goals - but it is only needed for parents pom and only in case when parent want to publish site descriptor.
In child projects such task is not needed.
Each ASF project should manage it and add this only in place where is needed, with inherited set to false, as example:
<plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-site-plugin</artifactId> <inherited>false</inherited> <executions> <execution> <id>attach-descriptor</id> <goals> <goal>attach-descriptor</goal> </goals> </execution> </executions> </plugin>
After removing from ASF parent we can simplify next step of releasing ASF parent - special manually maintained documentation layout.
Attachments
Issue Links
- is related to
-
RAT-345 Dependency updates via dependabot performed for release 0.17
- In Progress
-
DOXIASITETOOLS-348 Extend site descriptor to enforce a parent
- Closed
- relates to
-
MPOM-120 attach site descriptor only for pom packaging
- Closed
-
MPOM-482 Publish site descriptor with new parent
- Closed
- links to