-
Notifications
You must be signed in to change notification settings - Fork 121
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Split plugin and site modules #595
Split plugin and site modules #595
Conversation
Right now the doxia module is calle |
* Remove use of deprecated constructor * Add 'asciidoc' as valid file extension
bb54a92
to
3d3af7b
Compare
IMPORTANT: For history reasons I am not changing the project repo yet. I have seen IntelliJ not liking that the parent module is "asciidoctor-maven-tools" and the folder is "asciidoctor-maven-plugin", and furthermore there's sub-module called "asciidoctor-maven-plugin" ... but can be fixed renaming the folder. |
Completed successfull deployment (just staging) on Maven Central with new structure, this will be the layout, the new artifacts all appear under |
* Create parent module: asciidoctor-maven-tools * Create new dedicated modules: asciidoctor-maven-plugin, asciidoctor-doxia-module, asciidoctor-maven-commons * Remove unused gmaven-plugin eclipse condiguration * Remove use of commons-lang3 for StringUtils.isBlank * Remove use of deprecated constructor in AsciidoctorDoxiaParserModule * Add 'asciidoc' as valid file extension in AsciidoctorDoxiaParserModule * Update docs
Thank you for opening a pull request and contributing to asciidoctor-maven-plugin!
What kind of change does this PR introduce? (check at least one)
What is the goal of this pull request?
Splig the Maven Plugin and Doxia components in different modules following Maven practices.
Current Jar works as both because we are generating the appropiate metadata for both use cases, but it requires users to download dependencies they don't need.
Are there any alternative ways to implement this?
n/a
Are there any implications of this pull request? Anything a user must know?
Published artifacts change, from single jar
org.asciidoctor:asciidoctor-maven-plugin
we will have 3:org.asciidoctor:asciidoctor-maven-plugin
org.asciidoctor:asciidoctor-doxia-module
org.asciidoctor:asciidoctor-maven-commons
(shared dependency by both).Is it related to an existing issue?
Closes #574
Finally, please add a corresponding entry to CHANGELOG.adoc