Re: [mojo-dev] [VOTE] Release animal sniffer maven plugin 1.9

2012-10-10 Thread Stephen Connolly 
+1

The only issue I see is that the parent has not been updated so the LaF is
the old site style.

I don't see that as a blocker as Robert *should* be able to fix that (and
if he cannot he will just update his tooling ;-) ), but we should fix the
parent on trunk so the next release has the correct site style from the get
go.

This is your first release vote here isn't it... welcome to the mojo!

-Stephen

On 10 October 2012 03:05, Kohsuke Kawaguchi  wrote:

>
> I'd like to release Maven Animal Sniffer plugin 1.9.
>
> 2 issues have been fixed: http://jira.codehaus.org/**
> browse/MANIMALSNIFFER/**fixforversion/18569
>
> Staging repository:
>   
> https://nexus.codehaus.org/**content/repositories/**orgcodehausmojo-041/
>
> Site:
>   
> http://mojo.codehaus.org/**animal-sniffer/
>
> Tag:
>   
> https://svn.codehaus.org/mojo/**tags/animal-sniffer-parent-1.**9/
>
>
> Vote open for 72H (and will pass on lazy consensus)
> [+1]
> [0]
> [-1]
>
>
> My +1.
>
>
> --
> Kohsuke Kawaguchi  http://kohsuke.org/
>
> --**--**-
> To unsubscribe from this list, please visit:
>
>
> http://xircles.codehaus.org/**manage_email
>
>
>

Re: [mojo-dev] [VOTE] Release animal sniffer maven plugin 1.9

2012-10-10 Thread Stephen Connolly 
forgot to say, builds fine from source

On 10 October 2012 09:05, Stephen Connolly
wrote:

> +1
>
> The only issue I see is that the parent has not been updated so the LaF is
> the old site style.
>
> I don't see that as a blocker as Robert *should* be able to fix that (and
> if he cannot he will just update his tooling ;-) ), but we should fix the
> parent on trunk so the next release has the correct site style from the get
> go.
>
> This is your first release vote here isn't it... welcome to the mojo!
>
> -Stephen
>
>
> On 10 October 2012 03:05, Kohsuke Kawaguchi  wrote:
>
>>
>> I'd like to release Maven Animal Sniffer plugin 1.9.
>>
>> 2 issues have been fixed: http://jira.codehaus.org/**
>> browse/MANIMALSNIFFER/**fixforversion/18569
>>
>> Staging repository:
>>   https://nexus.codehaus.org/**content/repositories/**
>> orgcodehausmojo-041/
>>
>> Site:
>>   
>> http://mojo.codehaus.org/**animal-sniffer/
>>
>> Tag:
>>   
>> https://svn.codehaus.org/mojo/**tags/animal-sniffer-parent-1.**9/
>>
>>
>> Vote open for 72H (and will pass on lazy consensus)
>> [+1]
>> [0]
>> [-1]
>>
>>
>> My +1.
>>
>>
>> --
>> Kohsuke Kawaguchi  http://kohsuke.org/
>>
>> --**--**-
>> To unsubscribe from this list, please visit:
>>
>>
>> http://xircles.codehaus.org/**manage_email
>>
>>
>>
>

Re: [mojo-dev] [VOTE] Release animal sniffer maven plugin 1.9

2012-10-10 Thread Tony Chemit 
On Tue, 09 Oct 2012 19:05:51 -0700
Kohsuke Kawaguchi  wrote:

+1

works fine on my projects,

thanks,

tony.

> 
> I'd like to release Maven Animal Sniffer plugin 1.9.
> 
> 2 issues have been fixed: 
> http://jira.codehaus.org/browse/MANIMALSNIFFER/fixforversion/18569
> 
> Staging repository:
>https://nexus.codehaus.org/content/repositories/orgcodehausmojo-041/
> 
> Site:
>http://mojo.codehaus.org/animal-sniffer/
> 
> Tag:
>https://svn.codehaus.org/mojo/tags/animal-sniffer-parent-1.9/
> 
> 
> Vote open for 72H (and will pass on lazy consensus)
> [+1]
> [0]
> [-1]
> 
> 
> My +1.
> 
> 



-- 
Tony Chemit

tél: +33 (0) 2 40 50 29 28
email: che...@codelutin.com
http://www.codelutin.com

-
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

Re: [mojo-dev] [VOTE] Release animal sniffer maven plugin 1.9

2012-10-10 Thread Olivier Lamy 
+1

2012/10/10 Kohsuke Kawaguchi :
>
> I'd like to release Maven Animal Sniffer plugin 1.9.
>
> 2 issues have been fixed:
> http://jira.codehaus.org/browse/MANIMALSNIFFER/fixforversion/18569
>
> Staging repository:
>   https://nexus.codehaus.org/content/repositories/orgcodehausmojo-041/
>
> Site:
>   http://mojo.codehaus.org/animal-sniffer/
>
> Tag:
>   https://svn.codehaus.org/mojo/tags/animal-sniffer-parent-1.9/
>
>
> Vote open for 72H (and will pass on lazy consensus)
> [+1]
> [0]
> [-1]
>
>
> My +1.
>
>
> --
> Kohsuke Kawaguchi  http://kohsuke.org/
>
> -
> To unsubscribe from this list, please visit:
>
>http://xircles.codehaus.org/manage_email
>
>



-- 
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy

-
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

[mojo-dev] [jira] (MJAXB-55) Provide means to set the file name of generated XML schema

2012-10-10 Thread selckin (JIRA) 














































selckin
 commented on  MJAXB-55


Provide means to set the file name of generated XML schema















documentation has  instead of 



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira





-
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

[mojo-dev] [jira] (MJAXB-74) Compatibility with m2e 1.2.0

2012-10-10 Thread Stephen Cooper (JIRA) 














































Stephen Cooper
 commented on  MJAXB-74


Compatibility with m2e 1.2.0















Oh - thanks! We had dependency managed all the plugins and hadn't re-vistited this one in a while. We had an old version.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira





-
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

[mojo-dev] [jira] (MOJO-1875) When codenarc mojo calls fail missing method exception is thrown

2012-10-10 Thread Ben McGuire (JIRA) 














































Ben McGuire
 created  MOJO-1875


When codenarc mojo calls fail missing method exception is thrown















Issue Type:


Bug



Affects Versions:


codenarc-maven-plugin-0.17-2



Assignee:


Garvin LeClaire



Attachments:


mojo_fail.patch



Components:


codenarc



Created:


10/Oct/12 12:20 PM



Description:


This is a duplicate of http://jira.codehaus.org/browse/MOJO-1873 but I forgot to put in the component on it and can't go back and edit it. 

When the number of violations for a priority level is surpassed then fail method does not look to be called correctly. Below is the groovy.lang.MissingMethodException exception that is thrown. Instead of calling the fail method a exception of type MojoFailureException should be thrown. This is according to the maven docs at http://maven.apache.org/guides/plugin/guide-java-plugin-development.html


[INFO] 
[ERROR] FATAL ERROR
[INFO] 
[INFO] No signature of method: org.codehaus.mojo.codenarc.CodeNarcMojo.fail() is applicable for argument types: (java.lang.String) values: {"totalPriority1Violations exceeded threshold of 0 errors with 2"}
[INFO] 
[INFO] Trace
groovy.lang.MissingMethodException: No signature of method: org.codehaus.mojo.codenarc.CodeNarcMojo.fail() is applicable for argument types: (java.lang.String) values: {"totalPriority1Violations exceeded threshold of 0 errors with 2"}
	at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.unwrap(ScriptBytecodeAdapter.java:55)
	at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.invokeMethodOnCurrentN(ScriptBytecodeAdapter.java:91)
	at org.codehaus.mojo.codenarc.CodeNarcMojo.executeReport(CodeNarcMojo.groovy:397)
	at org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:190)
	at org.apache.maven.reporting.AbstractMavenReport.execute(AbstractMavenReport.java:99)
	at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
	at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
	at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
	at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
	at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
	at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
	at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
	at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	at com.intellij.rt.execution.application.AppMain.main(AppMain.java:120)

[mojo-dev] [jira] (MOJO-1876) Excludes does not work

2012-10-10 Thread Ben McGuire (JIRA) 














































Ben McGuire
 created  MOJO-1876


Excludes does not work















Issue Type:


Bug



Affects Versions:


codenarc-maven-plugin-0.17-2



Assignee:


Garvin LeClaire



Attachments:


Fix_excludes_issue.patch



Components:


codenarc



Created:


10/Oct/12 12:22 PM



Description:


Again this is a duplicate of http://jira.codehaus.org/browse/MOJO-1874 because I didn't add a component to it and can't edit it after the fact.

Currently the excludes parameter is being added as an includes parameter.




Environment:


Maven 2.2.1




Project:


Mojo



Priority:


Major



Reporter:


Ben McGuire




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira





-
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

[mojo-dev] [jira] (MJAXB-55) Provide means to set the file name of generated XML schema

2012-10-10 Thread Anders Hammar (JIRA) 














































Anders Hammar
 commented on  MJAXB-55


Provide means to set the file name of generated XML schema















@selckin: Please file e new (bug) ticket if you've found some error! Also, please include more details so that it is possible to knwo where the error is.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira





-
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

RE: [mojo-dev] [VOTE] Release animal sniffer maven plugin 1.9

2012-10-10 Thread Robert Scholte 

Site is fixed ;) Actually I wasn't able to do the site-deployment with the 
mojo-parent-28 due to duplicate Logger instances (so the thread on maven-dev is 
a serious risk). Upgrading to version 30 just before the site-deployment fixed 
the issue. Not something I can fix with the plugin. -Robert btw: tooling is a 
big word. It's a Maven plugin with a chain of calls on Maven Components in the 
right order ;)
 Date: Wed, 10 Oct 2012 09:05:27 +0100
From: stephen.alan.conno...@gmail.com
To: dev@mojo.codehaus.org
Subject: Re: [mojo-dev] [VOTE] Release animal sniffer maven plugin 1.9

+1
The only issue I see is that the parent has not been updated so the LaF is the 
old site style.
I don't see that as a blocker as Robert *should* be able to fix that (and if he 
cannot he will just update his tooling ;-) ), but we should fix the parent on 
trunk so the next release has the correct site style from the get go.

This is your first release vote here isn't it... welcome to the mojo!
-Stephen

On 10 October 2012 03:05, Kohsuke Kawaguchi  wrote:



I'd like to release Maven Animal Sniffer plugin 1.9.



2 issues have been fixed: 
http://jira.codehaus.org/browse/MANIMALSNIFFER/fixforversion/18569



Staging repository:

  https://nexus.codehaus.org/content/repositories/orgcodehausmojo-041/



Site:

  http://mojo.codehaus.org/animal-sniffer/



Tag:

  https://svn.codehaus.org/mojo/tags/animal-sniffer-parent-1.9/





Vote open for 72H (and will pass on lazy consensus)

[+1]

[0]

[-1]





My +1.





-- 

Kohsuke Kawaguchi  http://kohsuke.org/



-

To unsubscribe from this list, please visit:



   http://xircles.codehaus.org/manage_email

[mojo-dev] [VOTE] Release buildnumber-maven-plugin 1.2

2012-10-10 Thread Benson Margulies 
Greeting and Salutations,

We solved some issues issues:


Release Notes - Mojo Build Number Maven Plugin - Version 1.2



** Bug
* [MBUILDNUM-1] - javasvn issues, not respecting developerConnection
* [MBUILDNUM-2] - Incorrect regexp in items documentation on
create-mojo.html
* [MBUILDNUM-71] - buildnumber plugin doc errors
* [MBUILDNUM-75] - ClassCastException in CreateMojo.getScmBranch
* [MBUILDNUM-76] - ${buildNumber} in finalName not resolved to
value when Artifact.getFile() called in maven-android-plugin
* [MBUILDNUM-85] - Buildnumber plugin doesn't fail on doCheck if
file is modified
* [MBUILDNUM-89] - doUpdate is not documented



** Improvement
* [MBUILDNUM-12] - There is no way how to get SVN revision into
formatted buildNumber
* [MBUILDNUM-13] - Add @threadSafe support for maven3

** New Feature
* [MBUILDNUM-7] - Special item scmVersion to format build numbers
with both scm version and serial number


There are still plenty of issues in JIRA.

The new site has just been deployed here:
http://mojo.codehaus.org/buildnumber-maven-plugin

Staging Repository
https://nexus.codehaus.org/content/repositories/orgcodehausmojo-043/

This vote will be open for 72 hours and will use apathy (lazy consensus).

[+1] release it
[0] don't care
[-1] don't release!

Thanks,

Benson

P.S.

Here is my +1

-
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

[mojo-dev] autoreq: no

2012-10-10 Thread Crawford, Andrew 
Hello,

I've been scouring the RPM Plugin documentation and Google search results, 
trying to find a way to set the value of "autoreq" to "no" in the .spec file 
that RPM-Plugin produces.  So far I have not found any way to accomplish this 
(using configuration), and wanted to ping this list to see if it's possible.

I do not have root access in my environment, but would still like to create and 
deploy custom RPM files.  To do this, I need to maintain my own "private" RPM 
database.  When the value of "autoreq" is set to "yes" in the RPM-Plugin's 
.spec file, this setup fails as it thinks things like /bin/sh are not present 
on the system.

I know I can use the "--nodeps" RPM argument, but then I cannot checks for the 
dependencies that I do want to manage (one custom RPM requiring another custom 
RPM).  The best way to get what I need would be to disable the auto dependency 
(autoreq) setting.

Please let me know if there is a configuration directive available to disable 
this setting.

Thanks,
Andrew C.

Re: [mojo-dev] autoreq: no

2012-10-10 Thread Graham Leggett 
On 10 Oct 2012, at 23:20, "Crawford, Andrew"  wrote:

> I've been scouring the RPM Plugin documentation and Google search results, 
> trying to find a way to set the value of "autoreq" to "no" in the .spec file 
> that RPM-Plugin produces.  So far I have not found any way to accomplish this 
> (using configuration), and wanted to ping this list to see if it's possible.  
> 
> I do not have root access in my environment, but would still like to create 
> and deploy custom RPM files.  To do this, I need to maintain my own "private" 
> RPM database.  When the value of "autoreq" is set to "yes" in the 
> RPM-Plugin's .spec file, this setup fails as it thinks things like /bin/sh 
> are not present on the system.  
> 
> I know I can use the "--nodeps" RPM argument, but then I cannot checks for 
> the dependencies that I do want to manage (one custom RPM requiring another 
> custom RPM).  The best way to get what I need would be to disable the auto 
> dependency (autoreq) setting.  
> 
> Please let me know if there is a configuration directive available to disable 
> this setting.  

Is this not covered by the plugin docs?

Regards,
Graham
--

Re: [mojo-dev] autoreq: no

2012-10-10 Thread Crawford, Andrew 
Hi Graham,

I sure couldn't find it in plugin docs (spent significant time 
looking/digging).  If it is there somewhere, I certainly apologize, but as 
mentioned, I could not locate anything (nor could Google).

Andrew

From: Graham Leggett mailto:minf...@sharp.fm>>
Reply-To: "dev@mojo.codehaus.org" 
mailto:dev@mojo.codehaus.org>>
Date: Wednesday, October 10, 2012 5:13 PM
To: "dev@mojo.codehaus.org" 
mailto:dev@mojo.codehaus.org>>
Cc: "dev@mojo.codehaus.org" 
mailto:dev@mojo.codehaus.org>>
Subject: Re: [mojo-dev] autoreq: no

On 10 Oct 2012, at 23:20, "Crawford, Andrew" 
mailto:andrew.crawf...@nike.com>> wrote:

I've been scouring the RPM Plugin documentation and Google search results, 
trying to find a way to set the value of "autoreq" to "no" in the .spec file 
that RPM-Plugin produces.  So far I have not found any way to accomplish this 
(using configuration), and wanted to ping this list to see if it's possible.

I do not have root access in my environment, but would still like to create and 
deploy custom RPM files.  To do this, I need to maintain my own "private" RPM 
database.  When the value of "autoreq" is set to "yes" in the RPM-Plugin's 
.spec file, this setup fails as it thinks things like /bin/sh are not present 
on the system.

I know I can use the "--nodeps" RPM argument, but then I cannot checks for the 
dependencies that I do want to manage (one custom RPM requiring another custom 
RPM).  The best way to get what I need would be to disable the auto dependency 
(autoreq) setting.

Please let me know if there is a configuration directive available to disable 
this setting.

Is this not covered by the plugin docs?

Regards,
Graham
--

Re: [mojo-dev] autoreq: no

2012-10-10 Thread Graham Leggett 
On 11 Oct 2012, at 01:38, "Crawford, Andrew"  wrote:

> I sure couldn't find it in plugin docs (spent significant time 
> looking/digging).  If it is there somewhere, I certainly apologize, but as 
> mentioned, I could not locate anything (nor could Google).  

Plugin docs are auto generated in maven (as I understand), so if the docs are 
missing, I would guess the functionality doesn't exist right now.

Have you considered creating a patch? Seems a useful thing to have.

Regards,
Graham
--


-
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email