yes, you should remove this explicit module
FYI, you can't use Doxia Markdown 1.5 with m-site-p that uses Doxia 1.6
natively: there was a little refactoring in Doxia 1.6 that is backward
compatible (you can use new parsers with old Doxia core) but not forward
compatible (you cannot use old
Hello,
I am doing incremental Maven builds with Jenkins, where it uses mvn -amd -pl
... - This works fine, but I noticed that all tests are run regardless of
whether they are in projects which are really affected by the change or not.
Example:
I have the following structure in my Git repo:
-
I posted this question on StackOverflow but I’m stuck and haven’t been getting
much response so I decided to go to the “source” as it were.
Here’s a link to the question on SO, if you prefer to answer there (helpful
answers will get up-voted, best answer accepted):
What I hoped to accomplish was to put some specific snippets in pom.xml
or some other place and have maven pick up those snippets and drop them
in the right place in the generated web.xml.
That plugin is owned and maintained by the Tomcat guys, so feel free
to file an improvement in their bug
