michael-o commented on PR #173:
URL:
https://github.com/apache/maven-doxia-sitetools/pull/173#issuecomment-2363189879
Looking at your usecase I have the feeling that we have a conceptual flaw in
our design. Implicit parents do not seem right after all and you are trying to
remedy this with a parameter at the wrong place IMHO. I think that we either
need something like:
```xml
<site>
<parent>
<groupId>com.mycompany.app</groupId>
<artifactId>my-app</artifactId>
<version>1</version>
</parent>
</site>
```
(type and classifier are implied)
or we can make the `site.xml` a provided dependency of our build in the POM
directly. If the site descriptor follows the rules of the POM then introducing
a parent seems natural to me, no?
See this one:
https://repo1.maven.org/maven2/org/apache/maven/maven-parent/43/maven-parent-43-site.xml
Either:
```xml
<site>
<parent>
<groupId>org.apache.maven</groupId>
<artifactId>maven-parent</artifactId>
<version>43</version>
</parent>
</site>
```
OR
```xml
<project>
<dependencies>
<dependency>
<groupId>org.apache.maven</groupId>
<artifactId>maven-parent</artifactId>
<version>43</version>
<type>xml</type>
<classifier>site</classifer>
</dependency>
</dependencies>
</site>
```
WDYT?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
