[JIRA] [violations] (JENKINS-17722) Violations Codenarc Parser doesn't respect SourceDirectory XML tag

2013-07-25 Thread s...@red-illusions.dk (JIRA)














































Sune Wettersteen
 commented on  JENKINS-17722


Violations Codenarc Parser doesn't respect SourceDirectory XML tag















Looks like there has been quite some activity on this. Any idea when this fix will be released with a plugin update?



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 


[JIRA] (JENKINS-11964) [Regression] Cannot build a single module in a Maven multi-module job with Maven 3

2012-05-31 Thread s...@red-illusions.dk (JIRA)

[ 
https://issues.jenkins-ci.org/browse/JENKINS-11964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163367#comment-163367
 ] 

Sune Wettersteen commented on JENKINS-11964:


Is anyone actively looking into this?
It is one of the stumbling blocks for us in order to upgrade to maven 3.

Any feedback is appreciated.

> [Regression] Cannot build a single module in a Maven multi-module job with 
> Maven 3
> --
>
> Key: JENKINS-11964
> URL: https://issues.jenkins-ci.org/browse/JENKINS-11964
> Project: Jenkins
>  Issue Type: Bug
>  Components: maven
>Reporter: henryju
>Assignee: olamy
>
> We have upgraded from Jenkins 1.399 to Jenkins 1.441. Our Maven jobs are now 
> run by Maven 3.0.3 instead of Maven 2.2.1.
> When a job is a Maven multi-module project, it is possible to run a single 
> submodule (on the job page, click on "Modules", then start the build for a 
> given submodule). It was working fine with our old instance but now the build 
> fails with status "ABORTED".
> See thread: 
> http://jenkins.361315.n4.nabble.com/Build-Maven-submodule-gt-ABORTED-td4128116.html
> Is it possible to reintroduce this feature?
> Thanks

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira