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

2015-06-08 Thread Vincent Latombe
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 other value you
currently use)

Cheers,

Vincent

[1]
http://blog.sonatype.com/2009/08/create-a-customized-build-process-in-maven/#.VXXWhUZ5zaU

Vincent

2015-06-08 19:21 GMT+02:00 Behrooz Nobakht nob...@gmail.com:

 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 remove this requirement.
 What am I missing?

 Thanks,
 Behrooz


 On Mon, Jun 8, 2015 at 6:36 PM, Behrooz Nobakht nob...@gmail.com wrote:

  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
 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 directories listed in the
  model of the build.
 
  Hope that helps,
  Andreas
 
  Am Montag, 8. Juni 2015 schrieb Behrooz Nobakht :
 
   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
   sources files from a schema.
  
   I'm a bit clueless at this moment how to achieve the same for a custom
   plugin I'm developing.
   Any specific documentation, hints, or example sources I can look into
  for
   this?
  
   Thanks in advance,
   Behrooz
  
 
 
 
 
  --
  -- Behrooz Nobakht
 



 --
 -- Behrooz Nobakht



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

2015-06-08 Thread Behrooz Nobakht
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 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 other value you
 currently use)

 Cheers,

 Vincent

 [1]

 http://blog.sonatype.com/2009/08/create-a-customized-build-process-in-maven/#.VXXWhUZ5zaU

 Vincent

 2015-06-08 19:21 GMT+02:00 Behrooz Nobakht nob...@gmail.com:

  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 remove this requirement.
  What am I missing?
 
  Thanks,
  Behrooz
 
 
  On Mon, Jun 8, 2015 at 6:36 PM, Behrooz Nobakht nob...@gmail.com
 wrote:
 
   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
  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 directories listed in the
   model of the build.
  
   Hope that helps,
   Andreas
  
   Am Montag, 8. Juni 2015 schrieb Behrooz Nobakht :
  
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
sources files from a schema.
   
I'm a bit clueless at this moment how to achieve the same for a
 custom
plugin I'm developing.
Any specific documentation, hints, or example sources I can look
 into
   for
this?
   
Thanks in advance,
Behrooz
   
  
  
  
  
   --
   -- Behrooz Nobakht
  
 
 
 
  --
  -- Behrooz Nobakht
 




-- 
-- Behrooz Nobakht


Unable to Update to DOXIA 1.6 (latest)

2015-06-08 Thread Tibor Digana
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 like maven-reporting-impl
which depends on latest doxia-core?


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

2015-06-08 Thread Behrooz Nobakht
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 remove this requirement.
What am I missing?

Thanks,
Behrooz


On Mon, Jun 8, 2015 at 6:36 PM, Behrooz Nobakht nob...@gmail.com wrote:

 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 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 directories listed in the
 model of the build.

 Hope that helps,
 Andreas

 Am Montag, 8. Juni 2015 schrieb Behrooz Nobakht :

  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
  sources files from a schema.
 
  I'm a bit clueless at this moment how to achieve the same for a custom
  plugin I'm developing.
  Any specific documentation, hints, or example sources I can look into
 for
  this?
 
  Thanks in advance,
  Behrooz
 




 --
 -- Behrooz Nobakht




-- 
-- Behrooz Nobakht


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

2015-06-08 Thread Jason van Zyl
+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:
 https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHADE%20AND%20status%20%3D%20Open%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC
 
 Staging repo:
 https://repository.apache.org/content/repositories/maven-1189
 https://repository.apache.org/content/repositories/maven-1189/org/apache/maven/plugins/maven-shade-plugin/2.4/maven-shade-plugin-2.4-source-release.zip
 
 Source release checksum(s):
 maven-shade-plugin-2.4-source-release.zip sha1: 
 2ffe5cb14f62410523a59f9eb1e181d78ad47659
 
 
 Staging site:
 http://maven.apache.org/plugins-archives/maven-shade-plugin-LATEST/
 
 Guide to testing staged releases:
 http://maven.apache.org/guides/development/guide-testing-releases.html
 
 Vote open for 72 hours.
 
 [ ] +1
 [ ] +0
 [ ] -1
 
 Kind regards
 Karl Heinz Marbaise
 
 -
 To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
 For additional commands, e-mail: dev-h...@maven.apache.org
 

Thanks,

Jason

--
Jason van Zyl
Founder, Takari and Apache Maven
http://twitter.com/jvanzyl
http://twitter.com/takari_io
-

Simplex sigillum veri. (Simplicity is the seal of truth.)













-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org



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

2015-06-08 Thread Mark Struberg
+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 are still a couple of issues left in JIRA:
 https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHADE%20AND%20status%20%3D%20Open%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC
 
 Staging repo:
 https://repository.apache.org/content/repositories/maven-1189
 https://repository.apache.org/content/repositories/maven-1189/org/apache/maven/plugins/maven-shade-plugin/2.4/maven-shade-plugin-2.4-source-release.zip
 
 Source release checksum(s):
 maven-shade-plugin-2.4-source-release.zip sha1: 
 2ffe5cb14f62410523a59f9eb1e181d78ad47659
 
 
 Staging site:
 http://maven.apache.org/plugins-archives/maven-shade-plugin-LATEST/
 
 Guide to testing staged releases:
 http://maven.apache.org/guides/development/guide-testing-releases.html
 
 Vote open for 72 hours.
 
 [ ] +1
 [ ] +0
 [ ] -1
 
 Kind regards
 Karl Heinz Marbaise
 
 -
 To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
 For additional commands, e-mail: dev-h...@maven.apache.org
 
 
 Thanks,
 
 Jason
 
 --
 Jason van Zyl
 Founder, Takari and Apache Maven
 http://twitter.com/jvanzyl
 http://twitter.com/takari_io
 -
 
 Simplex sigillum veri. (Simplicity is the seal of truth.)
 
 
 
 
 
 
 
 
 
 
 
 
 
 -
 To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
 For additional commands, e-mail: dev-h...@maven.apache.org
 


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org



Doxia does not generate br

2015-06-08 Thread Tibor Digana
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
https://github.com/apache/maven-surefire/pull/41


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

2015-06-08 Thread birkedal
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.apache.org/jira/browse/MNG-5658): 
https://issues.apache.org/jira/browse/MNG-5658?focusedCommentId=14420034page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14420034


---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org



Fix for MCHECKSTYLE-295

2015-06-08 Thread Csaba Kozák
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,
Csabi


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

2015-06-08 Thread josephw
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 a POSIX shell on Solaris:

# Do the Solaris Dance:
if [ ! -d ~root ]  ; then
exec /usr/xpg4/bin/sh $0 $@ 



---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org



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

2015-06-08 Thread Behrooz Nobakht
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
sources files from a schema.

I'm a bit clueless at this moment how to achieve the same for a custom
plugin I'm developing.
Any specific documentation, hints, or example sources I can look into for
this?

Thanks in advance,
Behrooz


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

2015-06-08 Thread Behrooz Nobakht
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 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 directories listed in the
 model of the build.

 Hope that helps,
 Andreas

 Am Montag, 8. Juni 2015 schrieb Behrooz Nobakht :

  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
  sources files from a schema.
 
  I'm a bit clueless at this moment how to achieve the same for a custom
  plugin I'm developing.
  Any specific documentation, hints, or example sources I can look into for
  this?
 
  Thanks in advance,
  Behrooz
 




-- 
-- Behrooz Nobakht


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

2015-06-08 Thread Andreas Gudian
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 directories listed in the
model of the build.

Hope that helps,
Andreas

Am Montag, 8. Juni 2015 schrieb Behrooz Nobakht :

 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
 sources files from a schema.

 I'm a bit clueless at this moment how to achieve the same for a custom
 plugin I'm developing.
 Any specific documentation, hints, or example sources I can look into for
 this?

 Thanks in advance,
 Behrooz