[JIRA] [maven] (JENKINS-19827) Maven builds via Maven Project Plugin in Jenkins fail when using the openjpa-maven-plugin with enhance goal
Marcelo Rebasti resolved JENKINS-19827 as Cannot Reproduce Maven builds via Maven Project Plugin in Jenkins fail when using the openjpa-maven-plugin with enhance goal Chris, After 8 months without response I assume that the issue is resolved. If you still have the problem, feel free to reopen the issue. Regards. Marcelo Rebasti Change By: Marcelo Rebasti (21/Jun/14 1:31 AM) Status: Open Resolved Resolution: CannotReproduce 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/d/optout.
[JIRA] [core] (JENKINS-23378) Raise minimum requirement to servlet 3.0
Marcelo Rebasti commented on JENKINS-23378 Raise minimum requirement to servlet 3.0 Upgrading to Servlet 3.0 is a great idea, especially if only the 3% user base will be impacted. The only thing to have in consideration is that without servlet 3.1 Jenkins won't be able to use WebSockets or Server-Side Events, as both require non-blocking IO and HTTP protocol upgrade, features available from Servlet 3.1. All the libraries that I know that promise comet-style communication for Servlet 3.1 use long polling, or open a special port for the WebSocket connection. 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/d/optout.
[JIRA] [maven] (JENKINS-20209) Maven plugin sends email notification to null address
Marcelo Rebasti commented on JENKINS-20209 Maven plugin sends email notification to null address Bruno, the fix will be present in the upcoming maven integration plugin 2.1. The only version with the bug is 2.0, so you can downgrade to 1.533 too. 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] [jacoco] (JENKINS-20440) Inspector problem
Marcelo Rebasti commented on JENKINS-20440 Inspector problem I don't know if "Manage Old Data" will recognize the logger field as old data after the change, but I can give it a try and I'll tell you what happens. 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] [jacoco] (JENKINS-20440) Inspector problem
Marcelo Rebasti updated JENKINS-20440 Inspector problem Change By: Marcelo Rebasti (15/Nov/13 12:14 PM) Component/s: jacoco Component/s: maven 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] [maven] (JENKINS-19827) Maven builds via Maven Project Plugin in Jenkins fail when using the openjpa-maven-plugin with enhance goal
Marcelo Rebasti updated JENKINS-19827 Maven builds via Maven Project Plugin in Jenkins fail when using the openjpa-maven-plugin with enhance goal settings.xml used to compile openjpa-project-example. Change By: Marcelo Rebasti (12/Nov/13 11:56 PM) Attachment: settings.xml 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] [maven] (JENKINS-19827) Maven builds via Maven Project Plugin in Jenkins fail when using the openjpa-maven-plugin with enhance goal
Marcelo Rebasti commented on JENKINS-19827 Maven builds via Maven Project Plugin in Jenkins fail when using the openjpa-maven-plugin with enhance goal Chris, First of all, sorry by the delay in answer you. I wasn't able to reproduce the problem inside Jenkins alone, but I was able to reproduce it by setting tmpClassLoader=true as you said, both in Jenkins as in the command line. Jenkins don't set tmpClassLoader to any value at all. I recommends you doing 2 tests in order to know if the problem is in your jenkins configuration or in your project: 1) Try to compile the project openjpa-project-example attached to this issue in your Jenkins. For do this, you'll need use the settings.xml that I also attached. If this build works fine, the problem is something related to your project configuration and not to any openjpa project. 2) Try to build your project in a fresh installation of Jenkins. For do this, you can download any version of Jenkins (LTS or OSS, and perhaps the same that you are using in production) and run it in your computer by executing "java -jar jenkins.war". If this build works fine, the problem have to be related to your jenkins global configuration. If you can reproduce the problem in a fresh Jenkins installation with a simplified project, and you attach it to this issue, I'll be able to do some debug. Regards. Marcelo Rebasti 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.
