Unable to Update to DOXIA 1.6 (latest)

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 l

Re: Mojo API to add target/generated-sources/DIR to eclipse's source folder

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 wrote: > This annotation just allows you to skip the declaration when you > add t

Re: Mojo API to add target/generated-sources/DIR to eclipse's source folder

This annotation just allows you to skip the declaration when you add the execution to your pom. If you want to skip the block, you'll need to create a custom packaging [1]. Then you'd specify my-packaging in your pom, instead of jar (or any other value you currently use) Cheers, Vincent [1] h

Re: Mojo API to add target/generated-sources/DIR to eclipse's source folder

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 `` when I'm using the plugin; otherwise it's just ignored. I was expecting that the Mojo annotation would remove t

Re: Mojo API to add target/generated-sources/DIR to eclipse's source folder

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 wrote: > Hi, > > You can check the build-helper-maven-plugin, which has a tiny goal to add a > source direct

Re: Mojo API to add target/generated-sources/DIR to eclipse's source folder

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 directorie

Mojo API to add target/generated-sources/DIR to eclipse's source folder

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 s

[GitHub] maven pull request: MNG-5837: Use a subshell, rather than the 'loc...

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 ensure

Re: [VOTE] Release Apache Maven Shade Plugin version 2.4

+1 LieGrue, strub > Am 08.06.2015 um 12:32 schrieb Jason van Zyl : > > +1 > >> On Jun 7, 2015, at 6:15 AM, Karl Heinz Marbaise wrote: >> >> Hi, >> >> We solved 14 issues: >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317921&version=12331393 >> >> There are still a c

Fix for MCHECKSTYLE-295

Hi, as we already discussed on maven-users, there is an issue 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, Cs

[GitHub] maven pull request: MNG-5837: Use a subshell, rather than the 'loc...

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 [MNG-5658](https://issues.a

Re: [VOTE] Release Apache Maven Shade Plugin version 2.4

+1 > On Jun 7, 2015, at 6:15 AM, Karl Heinz Marbaise wrote: > > Hi, > > We solved 14 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317921&version=12331393 > > There are still a couple of issues left in JIRA: > https://issues.apache.org/jira/issues/?jql=project%20

Doxia does not generate

Can somebody experienced with Doxia tell me what's going on with the call sink.lineBreak()? It really looks like 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 http