Skip to content

[MPOM-483] Make a separate module for documentation - #210

Merged
slawekjaranowski merged 1 commit into
masterfrom
MPOM-483
Apr 13, 2024
Merged

[MPOM-483] Make a separate module for documentation#210
slawekjaranowski merged 1 commit into
masterfrom
MPOM-483

Conversation

@slawekjaranowski

@slawekjaranowski slawekjaranowski commented Apr 12, 2024

Copy link
Copy Markdown
Member

@ctubbsii ctubbsii left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Personally, I think creating a separate module for docs is confusing. From a project structure perspective, it looks like the docs are documentation for the docs module, and that the main module doesn't have docs, when it's the other way around. In general, I think I'd prefer keeping the site generation for the module in the same module that is being documented. Doing it this way seems to be not very "Maven-y".

Comment thread docs/pom.xml Outdated
@slawekjaranowski

Copy link
Copy Markdown
Member Author

In ASF parent pom there is more trick about publishing documentation and publishing parent pom.
For documentation perspective we need add some information to pom ... but we don't want to propagate it to child project.
So current we have a special site-pom.xml which must by manually edited during release process.
I trying to avoid such manual taks.
https://maven.apache.org/developers/release/parent-pom-release.html

@jira-importer

Copy link
Copy Markdown

Resolve #403

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants