Github user Adabaskar closed the pull request at:
https://github.com/apache/maven-doxia-tools/pull/1
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the fea
Am 2016-02-11 um 23:35 schrieb Hervé BOUTEMY:
Hi,
We solved 38 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12330653&styleName=Text&projectId=12317320
(thanks to everybody who contributed)
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/
Hi,
We solved 38 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12330653&styleName=Text&projectId=12317320
(thanks to everybody who contributed)
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20DOXIASITETOOLS%20A
Oh I wasn't saying opposition to what Karl is doing... more just saying
that the ultimate way I want us to go is using multibranch with
literate/pipeline (literate for the simple stuff, such as plugins, where
the README.md can be
# The Maven XYZ Plugin
> ## Build instructions
> ```
> mvn clean ver
GitHub user Adabaskar opened a pull request:
https://github.com/apache/maven-doxia-tools/pull/1
Changing plugin's prefix avoids old version conflicts
If plugin is invoced via the mvn goal "doxia:render-books" there is often a
conflict with the older 1.2 Version plugin already being
