[jira] [Closed] (DOXIA-563) switch to Git
[ https://issues.apache.org/jira/browse/DOXIA-563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy closed DOXIA-563. --- Resolution: Fixed CI job created: https://builds.apache.org/job/doxia/ > switch to Git > - > > Key: DOXIA-563 > URL: https://issues.apache.org/jira/browse/DOXIA-563 > Project: Maven Doxia > Issue Type: Task >Affects Versions: 1.7 >Reporter: Hervé Boutemy >Assignee: Hervé Boutemy > Fix For: 1.8 > > > switch from svn https://svn.apache.org/repos/asf/maven/doxia/doxia/trunk > to git https://gitbox.apache.org/repos/asf/maven-doxia.git > with r/w mirror to github https://github.com/apache/maven-doxia/ -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (DOXIASITETOOLS-180) switch to Git
[ https://issues.apache.org/jira/browse/DOXIASITETOOLS-180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy closed DOXIASITETOOLS-180. Resolution: Fixed CI job created: https://builds.apache.org/job/doxia-sitetools/ > switch to Git > - > > Key: DOXIASITETOOLS-180 > URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-180 > Project: Maven Doxia Sitetools > Issue Type: Task >Affects Versions: 1.7.5 >Reporter: Hervé Boutemy >Assignee: Hervé Boutemy > Fix For: 1.8.0 > > > switch from svn > https://svn.apache.org/repos/asf/maven/doxia/doxia-sitetools/trunk > to git https://gitbox.apache.org/repos/asf/maven-doxia-sitetools.git > with r/w mirror to github https://github.com/apache/maven-doxia-sitetools/ -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MPDF-81) Override the copyright footer
[ https://issues.apache.org/jira/browse/MPDF-81?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16215121#comment-16215121 ] Hervé Boutemy commented on MPDF-81: --- [~spyhunter99] Doxia and Doxia Sitetools just switched from svn to Git, with GitHub integration (ie Apache GitBox): see DOXIA-563 and DOXIASITETOOLS-180 do you want to try to do the footer enhancement, before doing more complex DOXIA-562? do you want me to do this MPDF-81/DOXIA-555/DOXIASITETOOLS as a sample? I'd like to do a release in a week or 2, then we just need to know how to work together on what's feasible: and I'm confident that this copyright footer can be done (I don't know yet about DOXIA-562) > Override the copyright footer > - > > Key: MPDF-81 > URL: https://issues.apache.org/jira/browse/MPDF-81 > Project: Maven PDF Plugin > Issue Type: New Feature >Affects Versions: 1.3 >Reporter: Alex O'Ree > Fix For: 1.4 > > Attachments: maven-pdf-plugin2.pdf > > > As of right now, it doesn't look possible to override the content of the > footer which is on all non-title page pages. It currently reads (c) year - > organization All rights reserved. > I don't see anywhere in the code where this is defined or in any of the > resource files. It is in the generated fo files but it's not obvious where > the xslt is. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (SCM-852) maven-scm-plugin:check-local-modification should optionally check for unpushed commits
Konrad Windszus created SCM-852: --- Summary: maven-scm-plugin:check-local-modification should optionally check for unpushed commits Key: SCM-852 URL: https://issues.apache.org/jira/browse/SCM-852 Project: Maven SCM Issue Type: Bug Components: maven-plugin Affects Versions: 1.9.5 Reporter: Konrad Windszus Currently the goal {{check-local-modification}} only checks for local changes. But with distributed SCM systems it is very often also desirable if all local commits have been pushed to the origin as well. It would be good to optionally check for unpushed commits or not yet fetched commits with that goal. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SCM-852) maven-scm-plugin:check-local-modification should optionally check for unpushed commits
[ https://issues.apache.org/jira/browse/SCM-852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SCM-852: Description: Currently the goal {{check-local-modification}} only checks for local changes. But with distributed SCM systems it is very often also desirable to enforce that all local commits have been pushed to the origin as well. It would be good to optionally check for unpushed commits or not yet fetched commits with that goal. (was: Currently the goal {{check-local-modification}} only checks for local changes. But with distributed SCM systems it is very often also desirable if all local commits have been pushed to the origin as well. It would be good to optionally check for unpushed commits or not yet fetched commits with that goal.) > maven-scm-plugin:check-local-modification should optionally check for > unpushed commits > -- > > Key: SCM-852 > URL: https://issues.apache.org/jira/browse/SCM-852 > Project: Maven SCM > Issue Type: Bug > Components: maven-plugin >Affects Versions: 1.9.5 >Reporter: Konrad Windszus > > Currently the goal {{check-local-modification}} only checks for local > changes. But with distributed SCM systems it is very often also desirable to > enforce that all local commits have been pushed to the origin as well. It > would be good to optionally check for unpushed commits or not yet fetched > commits with that goal. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (SUREFIRE-1433) rerunFailingTestsCount does not help with crashes
[ https://issues.apache.org/jira/browse/SUREFIRE-1433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16215494#comment-16215494 ] Jesse Glick commented on SUREFIRE-1433: --- Obviously the above is not a real test. I was merely demonstrating that Surefire is not robust against unforeseeable fatal problems in the test JVM, making it ill suited to long-running test suites. JUnit itself treats any {{Throwable}} thrown out of a test method as a “failure” which {{rerunFailingTestsCount}} will process; yet lower-level errors in a forked test VM are not recoverable. > rerunFailingTestsCount does not help with crashes > - > > Key: SUREFIRE-1433 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1433 > Project: Maven Surefire > Issue Type: Bug > Components: process forking >Affects Versions: 2.20.1 > Environment: Linux, Java 8u131, Maven 3.5.0 >Reporter: Jesse Glick > Attachments: demo.zip > > > I have a CI job running lots of very slow tests, and am using > {{-Dsurefire.rerunFailingTestsCount=2 -Dmaven.test.failure.ignore > -Dsurefire.timeout=7200 -DreuseForks=false -DforkCount=2}} to run Maven. It > will typically run for about three hours, collecting a lot of passing tests, > a few flaking tests with subsequent passes, and a few true failures. But then > it will abruptly halt with the infamous > {code:none} > Failed to execute goal > org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test (default-test) on > project ...: ExecutionException The forked VM terminated without properly > saying goodbye. VM crash or System.exit called? > {code} > The timing is unpredictable but the build seems to usually fail this way; > sometimes I get lucky and it runs through all the tests, taking a number of > hours. Diagnosing the crash is not likely to be straightforward, and frankly > I do not care much—I just want Surefire to try again. Yet the > {{rerunFailingTestsCount}} flag does not accomplish this—it only retries > normal failures. > You can see this from running the attached project. While you might expect it > to go through 100 runs of the test, some failing politely and some crashing, > instead you see something like > {code:none} > ... > --- maven-surefire-plugin:2.20.1:test (default-test) @ demo --- > --- > T E S T S > --- > Running demo.CrashingTest > failing > failing > failing > crashing > Results: > Tests run: 0, Failures: 0, Errors: 0, Skipped: 0 > > BUILD FAILURE > > Total time: 2.456 s > Finished at: 2017-10-07T15:11:04-04:00 > Final Memory: 11M/222M > > Failed to execute goal > org.apache.maven.plugins:maven-surefire-plugin:2.20.1:test (default-test) on > project demo: There are test failures. > ... > {code} -- This message was sent by Atlassian JIRA (v6.4.14#64029)