This annotation just allows you to skip the phase declaration when you
add the execution to your pom.
If you want to skip the execution block, you'll need to create a custom
packaging [1]. Then you'd specify packagingmy-packaging/packaging in
your pom, instead of packagingjar/packaging (or any
Thank you, Vincent for the link. It completely describes the way to
create default execution without the need to configure it when using the
plugin.
I learnt a lot!
On Mon, Jun 8, 2015 at 7:53 PM, Vincent Latombe vincent.lato...@gmail.com
wrote:
This annotation just allows you to skip the
After repackaging DOXIA class RenderingContext from package
doxia.sink.render to doxia.siterenderer I am not able to update DOXIA to
Version 1.6.
The surefire project depends on latest maven-reporting-impl:2.3 which needs
old class RenderingContex.
Has this solution, for instance another artifact
Let me continue with another question. Currently, my Mojo implementation has
@Mojo(name = my-goal-name, defaultPhase = LifecyclePhase.GENERATE_SOURCES)
However, I still need to add `execution` when I'm using the plugin;
otherwise it's just ignored.
I was expecting that the Mojo annotation would
+1
On Jun 7, 2015, at 6:15 AM, Karl Heinz Marbaise khmarba...@gmx.de wrote:
Hi,
We solved 14 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317921version=12331393
There are still a couple of issues left in JIRA:
+1
LieGrue,
strub
Am 08.06.2015 um 12:32 schrieb Jason van Zyl ja...@takari.io:
+1
On Jun 7, 2015, at 6:15 AM, Karl Heinz Marbaise khmarba...@gmx.de wrote:
Hi,
We solved 14 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317921version=12331393
There
Can somebody experienced with Doxia tell me what's going on with the call
sink.lineBreak()?
It really looks like br is generated if and only if the previous line is
finished with \n, i.e., sink.text( line + \n );
Is it expected Doxia optimization or a bug?
I found this issue after I dig into
Github user birkedal commented on the pull request:
https://github.com/apache/maven/pull/50#issuecomment-109946813
Looks like there are still problems on Solaris after applying the patch. It
seams like it's the `$()` that is problematic. See this comment on
Hi,
as we already discussed on maven-users, there is an issue
https://issues.apache.org/jira/browse/MCHECKSTYLE-295 with test resources
in the maven-checkstyle-plugin. I attached a patch to the JIRA ticket for
fixing the issue and adding an integration test.
Please have a look at it.
Thanks,
Github user josephw commented on the pull request:
https://github.com/apache/maven/pull/50#issuecomment-110022166
I've pushed a further change to switch $(..) to backticks. However, perhaps
[this idiom](https://bugs.freedesktop.org/show_bug.cgi?id=5278) would be a
better way to
Hi,
I am trying to follow what `maven-plugin-plugin` Mojo does when generating
HelpMojo.java.
It also updates eclipse's .classpath some way (?) that I can see the
`target/generated-sources/plugin`
as a source folder in my IDE.
Similarly, this is also what maven-jaxb2-plugin does when generating
Hi Andreas,
Thank you for the pointer. It helped and it worked.
I was using an improper life cycle phase as the default.
Cheers,
Behrooz
On Mon, Jun 8, 2015 at 6:13 PM, Andreas Gudian andreas.gud...@gmail.com
wrote:
Hi,
You can check the build-helper-maven-plugin, which has a tiny goal to
Hi,
You can check the build-helper-maven-plugin, which has a tiny goal to add a
source directory to the project:
https://github.com/mojohaus/build-helper-maven-plugin/blob/master/src/main/java/org/codehaus/mojo/buildhelper/AddSourceMojo.java
The maven-eclipse-plugin picks up all source
13 matches
Mail list logo
