[GitHub] [maven-integration-testing] mthmulders commented on a change in pull request #54: [MNG-4660] Add integration test to show that --resume-from works
mthmulders commented on a change in pull request #54: [MNG-4660] Add
integration test to show that --resume-from works
URL:
https://github.com/apache/maven-integration-testing/pull/54#discussion_r376241502
##
File path:
core-it-suite/src/test/java/org/apache/maven/it/MavenITmng4660ResumeFromTest.java
##
@@ -0,0 +1,74 @@
+package org.apache.maven.it;
+
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements. See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership. The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance
+ * with the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing,
+ * software distributed under the License is distributed on an
+ * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ * KIND, either express or implied. See the License for the
+ * specific language governing permissions and limitations
+ * under the License.
+ */
+
+import org.apache.maven.it.util.ResourceExtractor;
+
+import java.io.File;
+
+/**
+ * This is a test case for https://issues.apache.org/jira/browse/MNG-4660;>MNG-4660.
+ *
+ * @author Maarten Mulders
+ * @author Martin Kanters
+ */
+public class MavenITmng4660ResumeFromTest extends
AbstractMavenIntegrationTestCase {
+public MavenITmng4660ResumeFromTest()
+{
+// TODO Update version range once bug has been fixed!
+super( "[3.6.3,)" );
+}
+
+/**
+ * Test that the --resume-from flag resolves dependencies inside the same
Maven project
+ * without having them installed first.
+ */
+public void testIt() throws Exception
+{
+final File testDir = ResourceExtractor.simpleExtractResources(
getClass(), "/mng-4660-resume-from" );
+
+final Verifier verifier1 = newVerifier( testDir.getAbsolutePath() );
+verifier1.deleteDirectory( "target" );
+verifier1.deleteArtifacts( "org.apache.maven.its.mng4660" );
+
+try
+{
+verifier1.executeGoal("verify");
+fail( "Expected this invocation to fail" ); // See TestCase.java
+}
+catch ( final VerificationException ve )
+{
+verifier1.verifyTextInLog( "Deliberately fail test case" );
+}
+finally
+{
+verifier1.resetStreams();
+}
+
+final Verifier verifier2 = newVerifier( testDir.getAbsolutePath() );
+verifier2.setAutoclean( false );
+verifier2.addCliOption( "--resume-from" );
+verifier2.addCliOption( ":module-b" );
+verifier2.executeGoal( "compile" ); // to prevent the unit test from
failing (again)
Review comment:
We do option 2, but instead of recompiling module-a, we want to reuse the
outcome of the previous build, which did include module-a. That's why we have
`--resume-from :module-b` and _autoclean_ set to off. The test that resides in
module-b would fail again and that's why we went for `compile`.
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
With regards,
Apache Git Services
[GitHub] [maven-shade-plugin] rmannibucau commented on a change in pull request #38: [MSHADE-350] enable to rewrite the manifest
rmannibucau commented on a change in pull request #38: [MSHADE-350] enable to rewrite the manifest URL: https://github.com/apache/maven-shade-plugin/pull/38#discussion_r376223734 ## File path: src/main/java/org/apache/maven/plugins/shade/resource/ManifestResourceTransformer.java ## @@ -46,6 +46,8 @@ // Configuration private String mainClass; +private boolean skipRelocators; Review comment: Hmm, sounds like an option but current code works well for jakarta relocation too so I'm mixed to make the conf more complex/verbose for end user. Is having the boolean AND dedicated relocators ok for you? Boolean could be reversed and named "inheritDefaultRelocators". Wdyt? This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [maven-invoker-plugin] olamy commented on issue #11: (doc) Bump groovy to the latest in 2.4
olamy commented on issue #11: (doc) Bump groovy to the latest in 2.4 URL: https://github.com/apache/maven-invoker-plugin/pull/11#issuecomment-583180944 Thanks for your contribution! would you mind creating a JIra issue here https://issues.apache.org/jira/browse/MINVOKER? Thanks This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Commented] (MRELEASE-1038) releaseProfiles get overriden by exec.pomFileName
[
https://issues.apache.org/jira/browse/MRELEASE-1038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17032030#comment-17032030
]
Jeremy Landis commented on MRELEASE-1038:
-
Ugly fix...really hoping this is fixed soon. By my count 3 plugins recently
released all have pretty major regressions. This just bit me today when
releasing where I needed to split release activity from
signing activity. Those still doing open source and using obsolete and
unsupported oss-parent probably haven't noticed. Really hoping this regression
is fixed and patch released ASAP. There is very little on the master since the
first milestone and this is a rather ugly solution which has numerous jiras now
from what I've found regarding this.
> releaseProfiles get overriden by exec.pomFileName
> -
>
> Key: MRELEASE-1038
> URL: https://issues.apache.org/jira/browse/MRELEASE-1038
> Project: Maven Release Plugin
> Issue Type: Bug
> Components: perform
>Affects Versions: 3.0.0-M1
>Reporter: Benoit MESSAGER
>Priority: Minor
>
> Profiles specified in . are overrided by the
> pom file name.
> This come from : org.apache.maven.shared.release.config.ReleaseUtils line 130
> :
> {code:java}
> if ( properties.containsKey( "exec.activateProfiles" ) )
> {
> builder.setActivateProfiles( Arrays.asList( properties.getProperty(
> "exec.pomFileName" ).split( "," ) ) );
> }
> {code}
> this look like a failed copy/paste
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (DOXIA-595) Cannot build site with reporting on Windows
[
https://issues.apache.org/jira/browse/DOXIA-595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17032027#comment-17032027
]
Sylwester Lachiewicz commented on DOXIA-595:
plus with
[b73bacb2fd26f78caf26b64da3ea7eb4851d6910|https://gitbox.apache.org/repos/asf?p=maven-doxia.git;a=commit;h=b73bacb2fd26f78caf26b64da3ea7eb4851d6910]
> Cannot build site with reporting on Windows
> ---
>
> Key: DOXIA-595
> URL: https://issues.apache.org/jira/browse/DOXIA-595
> Project: Maven Doxia
> Issue Type: Bug
>Affects Versions: 1.3, 1.9
>Reporter: Michael Osipov
>Assignee: Herve Boutemy
>Priority: Major
> Fix For: 1.9.1
>
>
> Get clone from repo and run the following on Windows: {{mvn clean package
> site -Preporting -Ddoclint=none}}
> and see it fail with
> {noformat}
> [INFO]
> [INFO] --- maven-antrun-plugin:1.8:run (default) @ doxia-module-fml ---
> [WARNING] Parameter tasks is deprecated, use target instead
> [INFO] Executing tasks
> main:
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Doxia 1.9.1-SNAPSHOT ... SUCCESS [01:12
> min]
> [INFO] Doxia :: Logging API ... SUCCESS [ 50.966
> s]
> [INFO] Doxia :: Sink API .. SUCCESS [ 49.247
> s]
> [INFO] Doxia :: Test Documents SUCCESS [ 43.797
> s]
> [INFO] Doxia :: Core .. SUCCESS [01:30
> min]
> [INFO] Doxia :: Modules ... SUCCESS [ 44.828
> s]
> [INFO] Doxia :: APT Module SUCCESS [01:01
> min]
> [INFO] Doxia :: Confluence Module . SUCCESS [01:05
> min]
> [INFO] Doxia :: Simplified DocBook Module . SUCCESS [01:06
> min]
> [INFO] Doxia :: FML Module FAILURE [01:12
> min]
> [INFO] Doxia :: FO Module . SKIPPED
> [INFO] Doxia :: iText Module .. SKIPPED
> [INFO] Doxia :: Latex Module .. SKIPPED
> [INFO] Doxia :: RTF Module SKIPPED
> [INFO] Doxia :: TWiki Module .. SKIPPED
> [INFO] Doxia :: XDoc Module ... SKIPPED
> [INFO] Doxia :: XHTML Module .. SKIPPED
> [INFO] Doxia :: XHTML5 Module . SKIPPED
> [INFO] Doxia :: Markdown Module 1.9.1-SNAPSHOT SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 10:17 min
> [INFO] Finished at: 2019-08-25T18:52:23+02:00
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-antrun-plugin:1.8:run (default) on project
> doxia-module-fml: An Ant BuildException has occured:
> java.util.regex.PatternSyntaxException: Illegal/unsupported escape sequence
> near index 4
> [ERROR] ^D:\Entwicklung\Projekte\maven-doxia\doxia-modules\doxia-module-fml
> [ERROR] ^
> [ERROR] around Ant part ... value="D:\Entwicklung\Projekte\maven-doxia\doxia-modules\doxia-module-fml\target\site/xsddoc">...
> @ 5:123 in
> D:\Entwicklung\Projekte\maven-doxia\doxia-modules\doxia-module-fml\target\antrun\build-main.xml
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command
> [ERROR] mvn -rf :doxia-module-fml
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (MASFRES-29) Non parseable POM causing Maven build, installs to fail
Vikas Sinha created MASFRES-29: -- Summary: Non parseable POM causing Maven build, installs to fail Key: MASFRES-29 URL: https://issues.apache.org/jira/browse/MASFRES-29 Project: Apache Maven Resource Bundles Issue Type: Bug Reporter: Vikas Sinha Attachments: pom.xml Hello All, I am unable to run Maven configuration using my Eclipse IDE hosted on my Mac. It keeps on failing with the message that it is unable to parse a maven enforcer plugin file (see message below). There has not been any change to my Eclipse environment, my Maven project, my Maven configuration or my POM file. This was working fine 3-4 months back. Yesterday I cleaned up my entire repository (under $home/.m2) folder along with files under it and after that I am getting this error. I can see the downloaded Maven enforcer plugin jar file but it is failing while parsing (based on the error message) My eclipse plugin (m2e) uses version 1.13. I know it is a maven related issue but any help will be greatly appreciated Apache Maven 3.6.1 (d66c9c0b3152b2e69ee9bac180bb8fcc8e6af555; 2019-04-04T15:00:29-04:00) Maven home: /Users/v.si...@us.ibm.com/Documents/GitHub/FDA-BEST/hapi-fhir-develop/EMBEDDED Java version: 1.8.0_181, vendor: Oracle Corporation, runtime: /Library/Java/JavaVirtualMachines/jdk1.8.0_181.jdk/Contents/Home/jre Default locale: en_US, platform encoding: UTF-8 OS name: "mac os x", version: "10.15", arch: "x86_64", family: "mac" [DEBUG] Created new class realm maven.api [DEBUG] Importing foreign packages into class realm maven.api [DEBUG] Imported: javax.annotation.* < plexus.core [DEBUG] Imported: javax.annotation.security.* < plexus.core [DEBUG] Imported: javax.enterprise.inject.* < plexus.core [DEBUG] Imported: javax.enterprise.util.* < plexus.core [DEBUG] Imported: javax.inject.* < plexus.core [DEBUG] Imported: org.apache.maven.* < plexus.core [DEBUG] Imported: org.apache.maven.artifact < plexus.core [DEBUG] Imported: org.apache.maven.classrealm < plexus.core [DEBUG] Imported: org.apache.maven.cli < plexus.core [DEBUG] Imported: org.apache.maven.configuration < plexus.core [DEBUG] Imported: org.apache.maven.exception < plexus.core [DEBUG] Imported: org.apache.maven.execution < plexus.core [DEBUG] Imported: org.apache.maven.execution.scope < plexus.core [DEBUG] Imported: org.apache.maven.lifecycle < plexus.core [DEBUG] Imported: org.apache.maven.model < plexus.core [DEBUG] Imported: org.apache.maven.monitor < plexus.core [DEBUG] Imported: org.apache.maven.plugin < plexus.core [DEBUG] Imported: org.apache.maven.profiles < plexus.core [DEBUG] Imported: org.apache.maven.project < plexus.core [DEBUG] Imported: org.apache.maven.reporting < plexus.core [DEBUG] Imported: org.apache.maven.repository < plexus.core [DEBUG] Imported: org.apache.maven.rtinfo < plexus.core [DEBUG] Imported: org.apache.maven.settings < plexus.core [DEBUG] Imported: org.apache.maven.toolchain < plexus.core [DEBUG] Imported: org.apache.maven.usability < plexus.core [DEBUG] Imported: org.apache.maven.wagon.* < plexus.core [DEBUG] Imported: org.apache.maven.wagon.authentication < plexus.core [DEBUG] Imported: org.apache.maven.wagon.authorization < plexus.core [DEBUG] Imported: org.apache.maven.wagon.events < plexus.core [DEBUG] Imported: org.apache.maven.wagon.observers < plexus.core [DEBUG] Imported: org.apache.maven.wagon.proxy < plexus.core [DEBUG] Imported: org.apache.maven.wagon.repository < plexus.core [DEBUG] Imported: org.apache.maven.wagon.resource < plexus.core [DEBUG] Imported: org.codehaus.classworlds < plexus.core [DEBUG] Imported: org.codehaus.plexus.* < plexus.core [DEBUG] Imported: org.codehaus.plexus.classworlds < plexus.core [DEBUG] Imported: org.codehaus.plexus.component < plexus.core [DEBUG] Imported: org.codehaus.plexus.configuration < plexus.core [DEBUG] Imported: org.codehaus.plexus.container < plexus.core [DEBUG] Imported: org.codehaus.plexus.context < plexus.core [DEBUG] Imported: org.codehaus.plexus.lifecycle < plexus.core [DEBUG] Imported: org.codehaus.plexus.logging < plexus.core [DEBUG] Imported: org.codehaus.plexus.personality < plexus.core [DEBUG] Imported: org.codehaus.plexus.util.xml.Xpp3Dom < plexus.core [DEBUG] Imported: org.codehaus.plexus.util.xml.pull.XmlPullParser < plexus.core [DEBUG] Imported: org.codehaus.plexus.util.xml.pull.XmlPullParserException < plexus.core [DEBUG] Imported: org.codehaus.plexus.util.xml.pull.XmlSerializer < plexus.core [DEBUG] Imported: org.eclipse.aether.* < plexus.core [DEBUG] Imported: org.eclipse.aether.artifact < plexus.core [DEBUG] Imported: org.eclipse.aether.collection < plexus.core [DEBUG] Imported: org.eclipse.aether.deployment < plexus.core [DEBUG] Imported: org.eclipse.aether.graph < plexus.core [DEBUG] Imported: org.eclipse.aether.impl < plexus.core [DEBUG] Imported: org.eclipse.aether.installation < plexus.core [DEBUG] Imported:
[GitHub] [maven-shade-plugin] rfscholte commented on a change in pull request #38: [MSHADE-350] enable to rewrite the manifest
rfscholte commented on a change in pull request #38: [MSHADE-350] enable to rewrite the manifest URL: https://github.com/apache/maven-shade-plugin/pull/38#discussion_r376131364 ## File path: src/main/java/org/apache/maven/plugins/shade/resource/ManifestResourceTransformer.java ## @@ -46,6 +46,8 @@ // Configuration private String mainClass; +private boolean skipRelocators; Review comment: Looking at the code, it should be possible with a dedicated relocator instead of the SimpleRelocator. In this case you'll need a more delicate way than the brute search and replace all. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [maven-shade-plugin] rmannibucau commented on a change in pull request #38: [MSHADE-350] enable to rewrite the manifest
rmannibucau commented on a change in pull request #38: [MSHADE-350] enable to rewrite the manifest URL: https://github.com/apache/maven-shade-plugin/pull/38#discussion_r376103646 ## File path: src/main/java/org/apache/maven/plugins/shade/resource/ManifestResourceTransformer.java ## @@ -46,6 +46,8 @@ // Configuration private String mainClass; +private boolean skipRelocators; Review comment: Yes and no, they will have Bundle-Version entry in the manifest but most of the modules will be potential bundles but more often used in se/ee. For ex, the test i wrote used an openwebbeans output. It is used in se context, tomee, meecrowave (all not osgi) but also aries-cdi (osgi) or as plain osgi bundle. This is why i introduced this boolean. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Updated] (DOXIA-604) Upgrade to Apache FOP 2.4
[ https://issues.apache.org/jira/browse/DOXIA-604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated DOXIA-604: --- Fix Version/s: 2.0 > Upgrade to Apache FOP 2.4 > - > > Key: DOXIA-604 > URL: https://issues.apache.org/jira/browse/DOXIA-604 > Project: Maven Doxia > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Major > Fix For: 2.0 > > > This release fixes a number of bugs. In addition the following significant > functional enhancements are provided: > - Require Java 7 or later > - Drop dependency on Avalon-Framework > - Add change bar generation > - Add support for Khmer complex script > For release notes see [http://xmlgraphics.apache.org/fop/changes.html] > * FOP-1760: Add change bar generation > * FOP-2514: Empty hyphenation-character leads to "String index out of range: > 0" > * FOP-2624: FO to RTF conversion adds unnecessary \cell after ... when it is > nested inside any table cell > * FOP-2733: Drop dependency on Avalon-Framework > * FOP-2762: Serialisation issues with accessibility and conserve-memory > * FOP-2797: Bump version > * FOP-2798: Margins from blank page incorrectly used in subsequence page > * FOP-2799: Only reduce penalty if there is a existing break > * FOP-2800: IF Links point to current page instead of earlier page > * FOP-2802: Java 10 PDF/SVG to Image box not shown > * FOP-2805: Bump batik version > * FOP-2810: Incomplete implementation of the simulate-style flag > * FOP-2811: PDF larger than 100k pages can have wrong content stream > * FOP-2815: Avoid calling method not in spring-jcl > * FOP-2817: AFP should reset color for new segment > * FOP-2818: PDF color spaces are lost when embedding PDF image > * FOP-2821: 1 bit image fails when using PreloaderRawPNG > * FOP-2822: Use correct ipd for table inside float > * FOP-2823: page-index-relative not added when forwards link used to same > location > * FOP-2827: Add support for Khmer complex script > * FOP-2847: Support palette-based transparency PNG in PDF > * FOP-2853: Error for SVG using TTF fallback to AFP > * FOP-2855: Fix letter spacing of spaces inside white-space=pre text > * FOP-2856: Support compile on Java 12 > * FOP-2866: Using conserve option causes SerializationException > * FOP-2867: Hyphenation file is not reloaded after a change > * FOP-2868: OBJR should be a child of each link > * FOP-2869: basic-link to embedded file broken with encryption > * FOP-2871: Render space for accessible pdf > * FOP-2873: Update to PDFBox 2.0.16 > * FOP-2874: Conserve memory policy fails in multi-threaded environment > * FOP-2875: add support for non-ascii characters in pdf file attachment > names, fix name collisions of attachments > * FOP-2877: Table row was inside footer > * FOP-2881: Add option for page segment for GOCA > * FOP-2882: Allow PDFFormXObject to improve performance > * FOP-2883: Penalty cause table to flow into footer > * FOP-2885: Update Xerces to 2.12 > * XGC-112: TIFF resolution wrong on Java 10 > * XGC-116: Don't draw fully transparent alpha on PS -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (DOXIA-604) Upgrade to Apache FOP 2.4
[ https://issues.apache.org/jira/browse/DOXIA-604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated DOXIA-604: --- Description: This release fixes a number of bugs. In addition the following significant functional enhancements are provided: - Require Java 7 or later - Drop dependency on Avalon-Framework - Add change bar generation - Add support for Khmer complex script For release notes see [http://xmlgraphics.apache.org/fop/changes.html] * FOP-1760: Add change bar generation * FOP-2514: Empty hyphenation-character leads to "String index out of range: 0" * FOP-2624: FO to RTF conversion adds unnecessary \cell after ... when it is nested inside any table cell * FOP-2733: Drop dependency on Avalon-Framework * FOP-2762: Serialisation issues with accessibility and conserve-memory * FOP-2797: Bump version * FOP-2798: Margins from blank page incorrectly used in subsequence page * FOP-2799: Only reduce penalty if there is a existing break * FOP-2800: IF Links point to current page instead of earlier page * FOP-2802: Java 10 PDF/SVG to Image box not shown * FOP-2805: Bump batik version * FOP-2810: Incomplete implementation of the simulate-style flag * FOP-2811: PDF larger than 100k pages can have wrong content stream * FOP-2815: Avoid calling method not in spring-jcl * FOP-2817: AFP should reset color for new segment * FOP-2818: PDF color spaces are lost when embedding PDF image * FOP-2821: 1 bit image fails when using PreloaderRawPNG * FOP-2822: Use correct ipd for table inside float * FOP-2823: page-index-relative not added when forwards link used to same location * FOP-2827: Add support for Khmer complex script * FOP-2847: Support palette-based transparency PNG in PDF * FOP-2853: Error for SVG using TTF fallback to AFP * FOP-2855: Fix letter spacing of spaces inside white-space=pre text * FOP-2856: Support compile on Java 12 * FOP-2866: Using conserve option causes SerializationException * FOP-2867: Hyphenation file is not reloaded after a change * FOP-2868: OBJR should be a child of each link * FOP-2869: basic-link to embedded file broken with encryption * FOP-2871: Render space for accessible pdf * FOP-2873: Update to PDFBox 2.0.16 * FOP-2874: Conserve memory policy fails in multi-threaded environment * FOP-2875: add support for non-ascii characters in pdf file attachment names, fix name collisions of attachments * FOP-2877: Table row was inside footer * FOP-2881: Add option for page segment for GOCA * FOP-2882: Allow PDFFormXObject to improve performance * FOP-2883: Penalty cause table to flow into footer * FOP-2885: Update Xerces to 2.12 * XGC-112: TIFF resolution wrong on Java 10 * XGC-116: Don't draw fully transparent alpha on PS was: This release fixes a number of bugs. In addition the following significant functional enhancements are provided: - Require Java 7 or later - Drop dependency on Avalon-Framework - Add change bar generation - Add support for Khmer complex script For release notes see [http://xmlgraphics.apache.org/fop/changes.html] > Upgrade to Apache FOP 2.4 > - > > Key: DOXIA-604 > URL: https://issues.apache.org/jira/browse/DOXIA-604 > Project: Maven Doxia > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Major > > This release fixes a number of bugs. In addition the following significant > functional enhancements are provided: > - Require Java 7 or later > - Drop dependency on Avalon-Framework > - Add change bar generation > - Add support for Khmer complex script > For release notes see [http://xmlgraphics.apache.org/fop/changes.html] > * FOP-1760: Add change bar generation > * FOP-2514: Empty hyphenation-character leads to "String index out of range: > 0" > * FOP-2624: FO to RTF conversion adds unnecessary \cell after ... when it is > nested inside any table cell > * FOP-2733: Drop dependency on Avalon-Framework > * FOP-2762: Serialisation issues with accessibility and conserve-memory > * FOP-2797: Bump version > * FOP-2798: Margins from blank page incorrectly used in subsequence page > * FOP-2799: Only reduce penalty if there is a existing break > * FOP-2800: IF Links point to current page instead of earlier page > * FOP-2802: Java 10 PDF/SVG to Image box not shown > * FOP-2805: Bump batik version > * FOP-2810: Incomplete implementation of the simulate-style flag > * FOP-2811: PDF larger than 100k pages can have wrong content stream > * FOP-2815: Avoid calling method not in spring-jcl > * FOP-2817: AFP should reset color for new segment > * FOP-2818: PDF color spaces are lost when embedding PDF image > * FOP-2821: 1 bit image fails when using PreloaderRawPNG > * FOP-2822: Use correct ipd for table inside
[jira] [Created] (DOXIA-604) Upgrade to Apache FOP 2.4
Sylwester Lachiewicz created DOXIA-604: -- Summary: Upgrade to Apache FOP 2.4 Key: DOXIA-604 URL: https://issues.apache.org/jira/browse/DOXIA-604 Project: Maven Doxia Issue Type: Dependency upgrade Reporter: Sylwester Lachiewicz Assignee: Sylwester Lachiewicz This release fixes a number of bugs. In addition the following significant functional enhancements are provided: - Require Java 7 or later - Drop dependency on Avalon-Framework - Add change bar generation - Add support for Khmer complex script For release notes see [http://xmlgraphics.apache.org/fop/changes.html] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [maven-surefire] Tibor17 commented on issue #269: [SUREFIRE-1748] Fix reporting of empty stack trace messages
Tibor17 commented on issue #269: [SUREFIRE-1748] Fix reporting of empty stack trace messages URL: https://github.com/apache/maven-surefire/pull/269#issuecomment-583112179 @ajohnstonTE Yes right! We can of course disscuss the transport layer and application layer of the protocol. You can see that the JSON is serialized and sent in a stream and therefore the transport layer should specify the number of bytes to transfer, similar to `Content-Length`. Additionally, the frame in the transport layer should start with the magic number in order to avoid fake streams. We don't have to use Base64 in this case with JSON. The current implementation uses Base64 which copes with non-ASCII encodings, and it avoids collisions with `:`. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [maven-invoker-plugin] olamy merged pull request #10: (doc) Fix example invoker.properties
olamy merged pull request #10: (doc) Fix example invoker.properties URL: https://github.com/apache/maven-invoker-plugin/pull/10 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [maven-shade-plugin] rfscholte commented on a change in pull request #38: [MSHADE-350] enable to rewrite the manifest
rfscholte commented on a change in pull request #38: [MSHADE-350] enable to rewrite the manifest URL: https://github.com/apache/maven-shade-plugin/pull/38#discussion_r376070616 ## File path: src/main/java/org/apache/maven/plugins/shade/resource/ManifestResourceTransformer.java ## @@ -46,6 +46,8 @@ // Configuration private String mainClass; +private boolean skipRelocators; Review comment: Is there a way to discover if it is a OSGi project, e.g. via the packaging? This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [maven-shade-plugin] rmannibucau commented on a change in pull request #38: [MSHADE-350] enable to rewrite the manifest
rmannibucau commented on a change in pull request #38: [MSHADE-350] enable to rewrite the manifest URL: https://github.com/apache/maven-shade-plugin/pull/38#discussion_r376068006 ## File path: src/main/java/org/apache/maven/plugins/shade/resource/ManifestResourceTransformer.java ## @@ -46,6 +46,8 @@ // Configuration private String mainClass; +private boolean skipRelocators; Review comment: Agree but the algorithm being a bit fragile until we use a full osgi header parsers/rewriter with exception algorithms for the general case, I'd prefer a parameter to disable it for not osgi case. I can enhance the parsing but thought it is not the core of shade plugin so is not worth that logic. If wrong, happy to revise this. Not perfect state but secured - would be sad to break a project for that new behavior IMHO. Wdyt? This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [maven-shade-plugin] rmannibucau commented on a change in pull request #38: [MSHADE-350] enable to rewrite the manifest
rmannibucau commented on a change in pull request #38: [MSHADE-350] enable to rewrite the manifest URL: https://github.com/apache/maven-shade-plugin/pull/38#discussion_r376068006 ## File path: src/main/java/org/apache/maven/plugins/shade/resource/ManifestResourceTransformer.java ## @@ -46,6 +46,8 @@ // Configuration private String mainClass; +private boolean skipRelocators; Review comment: Agree but the algorithm being a bit fragile until we use a full osgi header parsers/rewriter with exception algorithms for the general case, I'd prefer a parameter to disable it for not osgi case. I can enhance the parsing but thought it is not the core of shade plugin so is kot worse that logic. If wrong, happy to revise this. Not perfect state but secured - would be sad to break a project for that new behavior IMHO. Wdyt? This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Commented] (MNG-6768) Support inheritable multiple settings
[ https://issues.apache.org/jira/browse/MNG-6768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17031888#comment-17031888 ] Marco Brandizi commented on MNG-6768: - [~rfscholte], my use case is: - I've my PC-specific settings in .m2 - I've my company-dependent settings in /company-settings.xml. These add and/or override my PC settings (or company server settings). - I need to do some test that imply using company settings and changing a few bits of them via an additional test-settings.xml file, which rely on company-settings.xml definitions. Yes, I could do it via command line parameters, but adding test-settings.xml and importing company-settings.xml from the latter can often be better than writing an .sh (eg, many parameters, many definitions. Yes, ti could be done by copying company-settings.xml into test-settings.xml, but that would create redundancy (and it's not always possible, when test-settings is in places different than , eg, in the CI system). > Support inheritable multiple settings > - > > Key: MNG-6768 > URL: https://issues.apache.org/jira/browse/MNG-6768 > Project: Maven > Issue Type: Improvement > Components: Settings >Reporter: Marco Brandizi >Priority: Minor > Fix For: waiting-for-feedback > > > As far as I know, the --settings option supports just one settings file. > Worse, when it is used, user settings in ~/.m2/settings.xml are ignored (not > tried, but I suspect global settings are too). > To me, this is rather poor. It would be much better if > # user and global settings were inherited and possibly overridden by the > further settings file. > # multiple --settings could be specified and a merge of settings > could be composed by maven (eg, blocks would come from multiple > files, would be overridden, considering the order in the command > line). > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (DOXIA-602) Upgrade test dependencies
[ https://issues.apache.org/jira/browse/DOXIA-602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz reassigned DOXIA-602: -- Assignee: Sylwester Lachiewicz > Upgrade test dependencies > - > > Key: DOXIA-602 > URL: https://issues.apache.org/jira/browse/DOXIA-602 > Project: Maven Doxia > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Trivial > > * JUnit to 4.13 > * XMLUnit to 2.6.3 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (DOXIA-602) Upgrade test dependencies
[ https://issues.apache.org/jira/browse/DOXIA-602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated DOXIA-602: --- Fix Version/s: 1.9.1 > Upgrade test dependencies > - > > Key: DOXIA-602 > URL: https://issues.apache.org/jira/browse/DOXIA-602 > Project: Maven Doxia > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Trivial > Fix For: 1.9.1 > > > * JUnit to 4.13 > * XMLUnit to 2.6.3 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [maven-shade-plugin] rfscholte commented on a change in pull request #38: [MSHADE-350] enable to rewrite the manifest
rfscholte commented on a change in pull request #38: [MSHADE-350] enable to rewrite the manifest URL: https://github.com/apache/maven-shade-plugin/pull/38#discussion_r376025839 ## File path: src/main/java/org/apache/maven/plugins/shade/resource/ManifestResourceTransformer.java ## @@ -46,6 +46,8 @@ // Configuration private String mainClass; +private boolean skipRelocators; Review comment: Do we really need this skip parameter? If the manifest file should be transformed and there are relocated classes, just apply them. I see no reason to pollute this class with a skip parameter. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Commented] (MNG-6860) Internal Error verifying Doxia site
[
https://issues.apache.org/jira/browse/MNG-6860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17031848#comment-17031848
]
Herve Boutemy commented on MNG-6860:
notice that Doxia site is a pure site, not a Java component, then {{mvn
verify}} is not really expected to be used: what is expected is {{mvn site}}
> Internal Error verifying Doxia site
> ---
>
> Key: MNG-6860
> URL: https://issues.apache.org/jira/browse/MNG-6860
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.6.1
>Reporter: Elliotte Rusty Harold
>Priority: Major
> Fix For: 3.6.3
>
>
> Checked out doxia-site from [https://github.com/apache/maven-doxia-site] and
> ran mvn verify on Linux with JDK 8.
>
> I estimate there's three different errors here to make this happen. This
> issue is for whatever in core is causing an InternalErrorException when
> likely faced with a somehow broken project setup.
>
> {noformat}
> elharo@elharo1:~/maven-doxia-site$ mvn verify
> [INFO] Scanning for projects...
> Downloading from apache.snapshots:
> [https://repository.apache.org/snapshots/org/apache/maven/maven-parent/34-SNAPSHOT/maven-metadata.xml]
> Downloading from apache.snapshots:
> [https://repository.apache.org/snapshots/org/apache/apache/22-SNAPSHOT/maven-metadata.xml]
> [ERROR] Internal error: java.lang.NullPointerException -> [Help 1]
> org.apache.maven.InternalErrorException: Internal error:
> java.lang.NullPointerException
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:120)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:192)
> at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:498)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:282)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:225)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:406)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347)
> Caused by: java.lang.NullPointerException
> at org.apache.maven.model.plugin.DefaultReportingConverter.convert
> (DefaultReportingConverter.java:243)
> at org.apache.maven.model.plugin.DefaultReportingConverter.convert
> (DefaultReportingConverter.java:213)
> at org.apache.maven.model.plugin.DefaultReportingConverter.convertReporting
> (DefaultReportingConverter.java:140)
> at org.apache.maven.model.building.DefaultModelBuilder.build
> (DefaultModelBuilder.java:479)
> at org.apache.maven.model.building.DefaultModelBuilder.build
> (DefaultModelBuilder.java:432)
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:616)
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:385)
> at org.apache.maven.graph.DefaultGraphBuilder.collectProjects
> (DefaultGraphBuilder.java:414)
> at org.apache.maven.graph.DefaultGraphBuilder.getProjectsForMavenReactor
> (DefaultGraphBuilder.java:405)
> at org.apache.maven.graph.DefaultGraphBuilder.build
> (DefaultGraphBuilder.java:82)
> at org.apache.maven.DefaultMaven.buildGraph (DefaultMaven.java:507)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:219)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:192)
> at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:498)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:282)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:225)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:406)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347)
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions,
[jira] [Updated] (MNG-6860) Internal Error verifying Doxia site
[
https://issues.apache.org/jira/browse/MNG-6860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MNG-6860:
---
Summary: Internal Error verifying Doxia site (was: Internal Error
verifying doxia)
> Internal Error verifying Doxia site
> ---
>
> Key: MNG-6860
> URL: https://issues.apache.org/jira/browse/MNG-6860
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.6.1
>Reporter: Elliotte Rusty Harold
>Priority: Major
> Fix For: 3.6.3
>
>
> Checked out doxia-site from [https://github.com/apache/maven-doxia-site] and
> ran mvn verify on Linux with JDK 8.
>
> I estimate there's three different errors here to make this happen. This
> issue is for whatever in core is causing an InternalErrorException when
> likely faced with a somehow broken project setup.
>
> {noformat}
> elharo@elharo1:~/maven-doxia-site$ mvn verify
> [INFO] Scanning for projects...
> Downloading from apache.snapshots:
> [https://repository.apache.org/snapshots/org/apache/maven/maven-parent/34-SNAPSHOT/maven-metadata.xml]
> Downloading from apache.snapshots:
> [https://repository.apache.org/snapshots/org/apache/apache/22-SNAPSHOT/maven-metadata.xml]
> [ERROR] Internal error: java.lang.NullPointerException -> [Help 1]
> org.apache.maven.InternalErrorException: Internal error:
> java.lang.NullPointerException
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:120)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:192)
> at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:498)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:282)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:225)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:406)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347)
> Caused by: java.lang.NullPointerException
> at org.apache.maven.model.plugin.DefaultReportingConverter.convert
> (DefaultReportingConverter.java:243)
> at org.apache.maven.model.plugin.DefaultReportingConverter.convert
> (DefaultReportingConverter.java:213)
> at org.apache.maven.model.plugin.DefaultReportingConverter.convertReporting
> (DefaultReportingConverter.java:140)
> at org.apache.maven.model.building.DefaultModelBuilder.build
> (DefaultModelBuilder.java:479)
> at org.apache.maven.model.building.DefaultModelBuilder.build
> (DefaultModelBuilder.java:432)
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:616)
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:385)
> at org.apache.maven.graph.DefaultGraphBuilder.collectProjects
> (DefaultGraphBuilder.java:414)
> at org.apache.maven.graph.DefaultGraphBuilder.getProjectsForMavenReactor
> (DefaultGraphBuilder.java:405)
> at org.apache.maven.graph.DefaultGraphBuilder.build
> (DefaultGraphBuilder.java:82)
> at org.apache.maven.DefaultMaven.buildGraph (DefaultMaven.java:507)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:219)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:192)
> at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:498)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:282)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:225)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:406)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347)
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
>
[jira] [Commented] (DOXIA-540) Update/remove ancient information on Doxia site
[ https://issues.apache.org/jira/browse/DOXIA-540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17031845#comment-17031845 ] Herve Boutemy commented on DOXIA-540: - the Doxia site is not tied to a Doxia release, so no "Fix Version" please > Update/remove ancient information on Doxia site > --- > > Key: DOXIA-540 > URL: https://issues.apache.org/jira/browse/DOXIA-540 > Project: Maven Doxia > Issue Type: Task > Components: Documentation >Affects Versions: 1.7 >Reporter: Michael Osipov >Priority: Major > Labels: up-for-grabs > Time Spent: 10m > Remaining Estimate: 0h > > Tasks to perform: > * Remove [Developer Docs|http://maven.apache.org/doxia/] for ancient versions. > * Remove Doxia IDE intergration is there is none working > * Remove [Upgrading|http://maven.apache.org/doxia/upgrading.html], it is > overhauled. > * Check [FAQ|http://maven.apache.org/doxia/faq.html] for validity. > * Merge [Apt > Enhancements|http://maven.apache.org/doxia/references/doxia-apt.html] into > [main site|http://maven.apache.org/doxia/references/apt-format.html]. > * Check [Issues|http://maven.apache.org/doxia/issues/index.html] for > validity. > * Update [External Resources|http://maven.apache.org/doxia/resources.html]. > * Remove ancient information from [Sink > API|http://maven.apache.org/doxia/doxia/doxia-sink-api/index.html]. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (DOXIA-540) Update/remove ancient information on Doxia site
[ https://issues.apache.org/jira/browse/DOXIA-540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated DOXIA-540: Fix Version/s: (was: 1.9.1) > Update/remove ancient information on Doxia site > --- > > Key: DOXIA-540 > URL: https://issues.apache.org/jira/browse/DOXIA-540 > Project: Maven Doxia > Issue Type: Task > Components: Documentation >Affects Versions: 1.7 >Reporter: Michael Osipov >Priority: Major > Labels: up-for-grabs > Time Spent: 10m > Remaining Estimate: 0h > > Tasks to perform: > * Remove [Developer Docs|http://maven.apache.org/doxia/] for ancient versions. > * Remove Doxia IDE intergration is there is none working > * Remove [Upgrading|http://maven.apache.org/doxia/upgrading.html], it is > overhauled. > * Check [FAQ|http://maven.apache.org/doxia/faq.html] for validity. > * Merge [Apt > Enhancements|http://maven.apache.org/doxia/references/doxia-apt.html] into > [main site|http://maven.apache.org/doxia/references/apt-format.html]. > * Check [Issues|http://maven.apache.org/doxia/issues/index.html] for > validity. > * Update [External Resources|http://maven.apache.org/doxia/resources.html]. > * Remove ancient information from [Sink > API|http://maven.apache.org/doxia/doxia/doxia-sink-api/index.html]. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MNG-6860) Internal Error verifying doxia
[
https://issues.apache.org/jira/browse/MNG-6860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MNG-6860:
---
Description:
Checked out doxia-site from [https://github.com/apache/maven-doxia-site] and
ran mvn verify on Linux with JDK 8.
I estimate there's three different errors here to make this happen. This issue
is for whatever in core is causing an InternalErrorException when likely faced
with a somehow broken project setup.
{noformat}
elharo@elharo1:~/maven-doxia-site$ mvn verify
[INFO] Scanning for projects...
Downloading from apache.snapshots:
[https://repository.apache.org/snapshots/org/apache/maven/maven-parent/34-SNAPSHOT/maven-metadata.xml]
Downloading from apache.snapshots:
[https://repository.apache.org/snapshots/org/apache/apache/22-SNAPSHOT/maven-metadata.xml]
[ERROR] Internal error: java.lang.NullPointerException -> [Help 1]
org.apache.maven.InternalErrorException: Internal error:
java.lang.NullPointerException
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:120)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:192)
at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:498)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
(Launcher.java:282)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
(Launcher.java:406)
at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347)
Caused by: java.lang.NullPointerException
at org.apache.maven.model.plugin.DefaultReportingConverter.convert
(DefaultReportingConverter.java:243)
at org.apache.maven.model.plugin.DefaultReportingConverter.convert
(DefaultReportingConverter.java:213)
at org.apache.maven.model.plugin.DefaultReportingConverter.convertReporting
(DefaultReportingConverter.java:140)
at org.apache.maven.model.building.DefaultModelBuilder.build
(DefaultModelBuilder.java:479)
at org.apache.maven.model.building.DefaultModelBuilder.build
(DefaultModelBuilder.java:432)
at org.apache.maven.project.DefaultProjectBuilder.build
(DefaultProjectBuilder.java:616)
at org.apache.maven.project.DefaultProjectBuilder.build
(DefaultProjectBuilder.java:385)
at org.apache.maven.graph.DefaultGraphBuilder.collectProjects
(DefaultGraphBuilder.java:414)
at org.apache.maven.graph.DefaultGraphBuilder.getProjectsForMavenReactor
(DefaultGraphBuilder.java:405)
at org.apache.maven.graph.DefaultGraphBuilder.build
(DefaultGraphBuilder.java:82)
at org.apache.maven.DefaultMaven.buildGraph (DefaultMaven.java:507)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:219)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:192)
at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:498)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
(Launcher.java:282)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
(Launcher.java:406)
at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347)
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please
read the following articles:
[ERROR] [Help 1]
[http://cwiki.apache.org/confluence/display/MAVEN/InternalErrorException]
{noformat}
was:
Checked out doxia-site from [https://github.com/apache/maven-doxia-site] and
ran mvn verify on Linux with JDK 8.
I estimate there's three different errors here to make this happen. This issue
is for whatever in core is causing an InternalErrorException when likely faced
with a somehow broken project setup.
elharo@elharo1:~/maven-doxia-site$ mvn verify
[INFO] Scanning for projects...
Downloading from apache.snapshots:
[https://repository.apache.org/snapshots/org/apache/maven/maven-parent/34-SNAPSHOT/maven-metadata.xml]
Downloading from
[jira] [Commented] (MCOMPILER-394) Stackoverflow while compiling Java Sources, but works after renaming project directory
[
https://issues.apache.org/jira/browse/MCOMPILER-394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17031823#comment-17031823
]
Robert Scholte commented on MCOMPILER-394:
--
I've just noticed you're still using maven-compiuler-plugin 3.1, could you at
least update it to 3.8.1?
> Stackoverflow while compiling Java Sources, but works after renaming project
> directory
> --
>
> Key: MCOMPILER-394
> URL: https://issues.apache.org/jira/browse/MCOMPILER-394
> Project: Maven Compiler Plugin
> Issue Type: Bug
>Affects Versions: 3.1
> Environment: The problem occurs with Windows 10, Windows 7 and also
> with Ubuntu.
>Reporter: Markus Bader
>Priority: Major
> Attachments: build.log
>
>
> Me and one of my colleagues have following problem (others do not): We want
> to build a maven project, but "mvn clean install" ends up in a stackoverflow
> error. But after renaming the project directory, it works. Also after
> renaming the name of the parent directory and leaving the name of the project
> directory by its original value, compilation is possible.
> I also tried changing the artifactId so that it doesn't match the folder
> name. Result: stackoverflow.
> To make it more strange: I tried to reduce the used Java classes for possibly
> identifying a class to be responsible for this phenomenon. Therefor I deleted
> a class named "MathParser" and after that compilation was possible. So I
> analysed the content of the class and found out, that the stackoverflow error
> occurs even if the class ist nearly empty. With following content I can
> reproduce the error:
>
> {code:java}
> package some.anonymised.package;
> public class MathParser {
> private void doSomething(String func) throws Exception {
> throw new Exception ("function '" + func + "' is not defined");
> }
> } {code}
> With an empty method body, the build works fine.
> I attached the log created with debug option activated (with reduced number
> of classes and reduced content of MathParser). For anonymisation purposes I
> replaced the name of some directories, packages etc. by "x".
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[GitHub] [maven-shade-plugin] rmannibucau commented on a change in pull request #38: [MSHADE-350] enable to rewrite the manifest
rmannibucau commented on a change in pull request #38: [MSHADE-350] enable to rewrite the manifest URL: https://github.com/apache/maven-shade-plugin/pull/38#discussion_r375940979 ## File path: src/main/java/org/apache/maven/plugins/shade/resource/ManifestResourceTransformer.java ## @@ -51,6 +51,8 @@ // Fields private boolean manifestDiscovered; +private boolean skipRelocators; Review comment: it is set in the pom.xml and is an user config - as mainClass is . Guess I put it in the wrong comment block ;), will move it. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [maven-shade-plugin] rmannibucau commented on a change in pull request #38: [MSHADE-350] enable to rewrite the manifest
rmannibucau commented on a change in pull request #38: [MSHADE-350] enable to rewrite the manifest URL: https://github.com/apache/maven-shade-plugin/pull/38#discussion_r375940979 ## File path: src/main/java/org/apache/maven/plugins/shade/resource/ManifestResourceTransformer.java ## @@ -51,6 +51,8 @@ // Fields private boolean manifestDiscovered; +private boolean skipRelocators; Review comment: it is set in the pom.xml and is an user config. Guess I forgot a setter, will add it. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Created] (MNG-6862) Wrong command line analysis for joined profile activation
Karl Heinz Marbaise created MNG-6862:
Summary: Wrong command line analysis for joined profile activation
Key: MNG-6862
URL: https://issues.apache.org/jira/browse/MNG-6862
Project: Maven
Issue Type: Improvement
Affects Versions: 3.6.3
Reporter: Karl Heinz Marbaise
Fix For: 3.7.0
On command line you can activate profiles via {{-PprofileName}} and activating
several profiles via {{-Pprofile1,profile2}}. Given the following command line:
{{mvn -Prun-p1,-Prun-p2 ...}}
The result is that the first profile {{run-p1}} is being activate but the
second {{run-p2}} (intended profile) is *not* because those two profiles have
been accidentally joined via {{,}} without giving spaces between.
The issue here is of course the {{,}} between them (without spaces) which is
obviously wrong but the preceding dash for the second profile {{-Prun-p2}}
violates the naming rules for profiles (If I correctly remember).
>From my point of view it would be good to identify such case and fail with an
>error...
In the end is it a question of naming a profile? Which means is it allowed
having a profile which starts with a dash ?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[GitHub] [maven-shade-plugin] eolivelli commented on a change in pull request #38: [MSHADE-350] enable to rewrite the manifest
eolivelli commented on a change in pull request #38: [MSHADE-350] enable to rewrite the manifest URL: https://github.com/apache/maven-shade-plugin/pull/38#discussion_r375940070 ## File path: src/main/java/org/apache/maven/plugins/shade/resource/ManifestResourceTransformer.java ## @@ -51,6 +51,8 @@ // Fields private boolean manifestDiscovered; +private boolean skipRelocators; Review comment: it looks like you are never setting a value, except from tests This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [maven-shade-plugin] eolivelli commented on a change in pull request #38: [MSHADE-350] enable to rewrite the manifest
eolivelli commented on a change in pull request #38: [MSHADE-350] enable to rewrite the manifest URL: https://github.com/apache/maven-shade-plugin/pull/38#discussion_r375940070 ## File path: src/main/java/org/apache/maven/plugins/shade/resource/ManifestResourceTransformer.java ## @@ -51,6 +51,8 @@ // Fields private boolean manifestDiscovered; +private boolean skipRelocators; Review comment: it looks like you are never setting a value This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [maven-invoker-plugin] pzygielo opened a new pull request #11: (doc) Bump groovy to the latest in 2.4
pzygielo opened a new pull request #11: (doc) Bump groovy to the latest in 2.4 URL: https://github.com/apache/maven-invoker-plugin/pull/11 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Commented] (MCHECKSTYLE-391) Update parent to 34
[ https://issues.apache.org/jira/browse/MCHECKSTYLE-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17031697#comment-17031697 ] Hudson commented on MCHECKSTYLE-391: Build succeeded in Jenkins: Maven TLP » maven-checkstyle-plugin » master #48 See https://builds.apache.org/job/maven-box/job/maven-checkstyle-plugin/job/master/48/ > Update parent to 34 > --- > > Key: MCHECKSTYLE-391 > URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-391 > Project: Maven Checkstyle Plugin > Issue Type: Task >Affects Versions: 3.1.0 >Reporter: Enrico Olivelli >Assignee: Enrico Olivelli >Priority: Major > Fix For: 3.1.1 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MCHECKSTYLE-365) Site Report, Rules: Violation count incorrect for duplicate rules when one uses default severity
[
https://issues.apache.org/jira/browse/MCHECKSTYLE-365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17031654#comment-17031654
]
Hudson commented on MCHECKSTYLE-365:
Build succeeded in Jenkins: Maven TLP » maven-checkstyle-plugin » master #47
See
https://builds.apache.org/job/maven-box/job/maven-checkstyle-plugin/job/master/47/
> Site Report, Rules: Violation count incorrect for duplicate rules when one
> uses default severity
>
>
> Key: MCHECKSTYLE-365
> URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-365
> Project: Maven Checkstyle Plugin
> Issue Type: Bug
>Affects Versions: 2.17, 3.0.0
>Reporter: Robert Turner
>Assignee: Enrico Olivelli
>Priority: Trivial
> Fix For: 3.1.0
>
> Attachments: Screen Shot 2018-12-31 at 14.43.18.png
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When the site report is generated, in the Rules section, the plug-in groups
> together the violation counts for rules that have the same name and message,
> but that have different severity levels -- specifically where one of the
> rules doesn't specify a severity level and uses the default ({{error}}). This
> results in both rules being listed with different properties and severity
> levels, but with the same violation count (which is incorrect).
> Also note that adding a unique {{id}} attribute to each of the rules also
> does not result in the violation counts being aggregated correctly. (the
> proposed patch does not address this aspect).
> To be correct, the report should use the same criteria for determining unique
> rules as it does for aggregating the violation counts for each rule.
> A simple user work-around for some rules (such as {{RegexpSingleline}}) is to
> change the {{message}} property for each of the rules with different severity
> levels. However, this doesn't work for other rules, such as
> {{FileTabCharacter}} as the {{message}} property is not supported for that
> rule.
> I will attach a screenshot of the issue manifesting itself, and I will
> provide a pull request for the changes to correct the issue.
> Sample rule set showing the issue:
> {code:xml}
>
>
>
>
>
>
>
>
>
>
>
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MCHECKSTYLE-389) MCHECKSTYLE-365 introduces regression with 'rules' aggregate count section on report
[ https://issues.apache.org/jira/browse/MCHECKSTYLE-389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17031653#comment-17031653 ] Hudson commented on MCHECKSTYLE-389: Build succeeded in Jenkins: Maven TLP » maven-checkstyle-plugin » master #47 See https://builds.apache.org/job/maven-box/job/maven-checkstyle-plugin/job/master/47/ > MCHECKSTYLE-365 introduces regression with 'rules' aggregate count section on > report > > > Key: MCHECKSTYLE-389 > URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-389 > Project: Maven Checkstyle Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.1.0 >Reporter: Jeremy Landis >Assignee: Enrico Olivelli >Priority: Major > Fix For: 3.1.1 > > Time Spent: 20m > Remaining Estimate: 0h > > Commit eee0ba1 in CheckstyleReportGenerator.java sets the default 'severity' > is set as 'error'. The suggestion is that it fixes count issues per adjusted > comment at that time. While that may or may not be true, what it does do is > incorrectly shut down the entire section of rules aggregation counts in some > cases. The severity only takes into account that specific one to then > aggregate. Selecting just one other than null is going to mess up the logic > as implemented here. This change needs reverted for that one specific change > only. The original issue should be reopened as it was not properly fixed. > The IT tests fails to take into account individual types. It includes both > 'info' and 'error' thus the only reason it even works. > In my test case, I'm using 'mybatis-3'. I have configured it to use google > checks so nothing else setup. It has 0 info, 3151warnings, and 0 errors. > Switching it to any other value will cause it to only reflect that section. > So using 'info', nothing shows up. Using 'error' as coded now, nothing shows > up. Using 'warning', it does show up. Continuing to use null as originally > the case, it does show up. > There really was a miscount somewhere, but that was not the right fix. For > my test, I get a miscount of +5 if using 'warning' or the original null. > That is entirely better than nothing. And therefore, the best solution for > now is to revert this change. > While my test does not have a combination of issues in 'info', 'warning', and > 'error', presumably most do and thus why this was not reported after almost a > year since the release of 3.1.0. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MCHECKSTYLE-390) Upgrade to checkstyle 8.29
[ https://issues.apache.org/jira/browse/MCHECKSTYLE-390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17031649#comment-17031649 ] Hudson commented on MCHECKSTYLE-390: Build succeeded in Jenkins: Maven TLP » maven-checkstyle-plugin » master #46 See https://builds.apache.org/job/maven-box/job/maven-checkstyle-plugin/job/master/46/ > Upgrade to checkstyle 8.29 > -- > > Key: MCHECKSTYLE-390 > URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-390 > Project: Maven Checkstyle Plugin > Issue Type: Improvement >Affects Versions: 3.1.0 >Reporter: Enrico Olivelli >Assignee: Enrico Olivelli >Priority: Major > Fix For: 3.1.1 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (MCHECKSTYLE-391) Update parent to 34
[ https://issues.apache.org/jira/browse/MCHECKSTYLE-391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Enrico Olivelli reassigned MCHECKSTYLE-391: --- Assignee: Enrico Olivelli > Update parent to 34 > --- > > Key: MCHECKSTYLE-391 > URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-391 > Project: Maven Checkstyle Plugin > Issue Type: Task >Affects Versions: 3.1.0 >Reporter: Enrico Olivelli >Assignee: Enrico Olivelli >Priority: Major > Fix For: 3.1.1 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [maven-checkstyle-plugin] eolivelli closed pull request #24: [MCHECKSTYLE-384] Update IT tests to support checkstyle 8.28
eolivelli closed pull request #24: [MCHECKSTYLE-384] Update IT tests to support checkstyle 8.28 URL: https://github.com/apache/maven-checkstyle-plugin/pull/24 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Created] (MCHECKSTYLE-391) Update parent to 34
Enrico Olivelli created MCHECKSTYLE-391: --- Summary: Update parent to 34 Key: MCHECKSTYLE-391 URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-391 Project: Maven Checkstyle Plugin Issue Type: Task Affects Versions: 3.1.0 Reporter: Enrico Olivelli Fix For: 3.1.1 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [maven-shade-plugin] rmannibucau opened a new pull request #38: [MSHADE-350] enable to rewrite the manifest
rmannibucau opened a new pull request #38: [MSHADE-350] enable to rewrite the manifest URL: https://github.com/apache/maven-shade-plugin/pull/38 Goal is to be able to use relocations in manifest imports/exports/capabilities as we do for service transformers - otherwise relocations break OSGi integration. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Created] (MSHADE-350) Enable ManifestResourceTransformer to rewrite the manifest with relocations
Romain Manni-Bucau created MSHADE-350: - Summary: Enable ManifestResourceTransformer to rewrite the manifest with relocations Key: MSHADE-350 URL: https://issues.apache.org/jira/browse/MSHADE-350 Project: Maven Shade Plugin Issue Type: Task Reporter: Romain Manni-Bucau -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (MCHECKSTYLE-389) MCHECKSTYLE-365 introduces regression with 'rules' aggregate count section on report
[ https://issues.apache.org/jira/browse/MCHECKSTYLE-389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Enrico Olivelli resolved MCHECKSTYLE-389. - Resolution: Fixed merged as de614e3ce5f4b4b7fc12e6cbd54189638e58a551 thank you [~hazendaz] I am sorry I can't set you as Assignee > MCHECKSTYLE-365 introduces regression with 'rules' aggregate count section on > report > > > Key: MCHECKSTYLE-389 > URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-389 > Project: Maven Checkstyle Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.1.0 >Reporter: Jeremy Landis >Assignee: Enrico Olivelli >Priority: Major > Fix For: 3.1.1 > > Time Spent: 20m > Remaining Estimate: 0h > > Commit eee0ba1 in CheckstyleReportGenerator.java sets the default 'severity' > is set as 'error'. The suggestion is that it fixes count issues per adjusted > comment at that time. While that may or may not be true, what it does do is > incorrectly shut down the entire section of rules aggregation counts in some > cases. The severity only takes into account that specific one to then > aggregate. Selecting just one other than null is going to mess up the logic > as implemented here. This change needs reverted for that one specific change > only. The original issue should be reopened as it was not properly fixed. > The IT tests fails to take into account individual types. It includes both > 'info' and 'error' thus the only reason it even works. > In my test case, I'm using 'mybatis-3'. I have configured it to use google > checks so nothing else setup. It has 0 info, 3151warnings, and 0 errors. > Switching it to any other value will cause it to only reflect that section. > So using 'info', nothing shows up. Using 'error' as coded now, nothing shows > up. Using 'warning', it does show up. Continuing to use null as originally > the case, it does show up. > There really was a miscount somewhere, but that was not the right fix. For > my test, I get a miscount of +5 if using 'warning' or the original null. > That is entirely better than nothing. And therefore, the best solution for > now is to revert this change. > While my test does not have a combination of issues in 'info', 'warning', and > 'error', presumably most do and thus why this was not reported after almost a > year since the release of 3.1.0. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MCHECKSTYLE-389) MCHECKSTYLE-365 introduces regression with 'rules' aggregate count section on report
[ https://issues.apache.org/jira/browse/MCHECKSTYLE-389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Enrico Olivelli updated MCHECKSTYLE-389: Fix Version/s: 3.1.1 > MCHECKSTYLE-365 introduces regression with 'rules' aggregate count section on > report > > > Key: MCHECKSTYLE-389 > URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-389 > Project: Maven Checkstyle Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.1.0 >Reporter: Jeremy Landis >Assignee: Enrico Olivelli >Priority: Major > Fix For: 3.1.1 > > Time Spent: 20m > Remaining Estimate: 0h > > Commit eee0ba1 in CheckstyleReportGenerator.java sets the default 'severity' > is set as 'error'. The suggestion is that it fixes count issues per adjusted > comment at that time. While that may or may not be true, what it does do is > incorrectly shut down the entire section of rules aggregation counts in some > cases. The severity only takes into account that specific one to then > aggregate. Selecting just one other than null is going to mess up the logic > as implemented here. This change needs reverted for that one specific change > only. The original issue should be reopened as it was not properly fixed. > The IT tests fails to take into account individual types. It includes both > 'info' and 'error' thus the only reason it even works. > In my test case, I'm using 'mybatis-3'. I have configured it to use google > checks so nothing else setup. It has 0 info, 3151warnings, and 0 errors. > Switching it to any other value will cause it to only reflect that section. > So using 'info', nothing shows up. Using 'error' as coded now, nothing shows > up. Using 'warning', it does show up. Continuing to use null as originally > the case, it does show up. > There really was a miscount somewhere, but that was not the right fix. For > my test, I get a miscount of +5 if using 'warning' or the original null. > That is entirely better than nothing. And therefore, the best solution for > now is to revert this change. > While my test does not have a combination of issues in 'info', 'warning', and > 'error', presumably most do and thus why this was not reported after almost a > year since the release of 3.1.0. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (MCHECKSTYLE-384) Incompatibil ity to Checkstyle version >= 8.24 - Upgrade to 8.28
[
https://issues.apache.org/jira/browse/MCHECKSTYLE-384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Enrico Olivelli resolved MCHECKSTYLE-384.
-
Resolution: Fixed
> Incompatibil ity to Checkstyle version >= 8.24 - Upgrade to 8.28
> -
>
> Key: MCHECKSTYLE-384
> URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-384
> Project: Maven Checkstyle Plugin
> Issue Type: Bug
> Components: checkstyle:check
>Affects Versions: 3.1.0
>Reporter: Martin
>Assignee: Enrico Olivelli
>Priority: Blocker
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The latest {{maven-checkstyle-plugin}} is incompatible to Checkstyle version
> 8.24 and newer. The check for "LineLength" was moved from "TreeWalker" to
> "Checker".
> For further details see "Breaking backward compatibility" under
> https://checkstyle.org/releasenotes.html#Release_8.24
>
> {code:none|title=Maven Console Output}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-checkstyle-plugin:3.1.0:check (validate) on
> project top-secrect: Failed during checkstyle configuration: LineLength is
> not allowed as a child in Checker -> [Help 1]
> [ERROR] ...
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (MCHECKSTYLE-384) Incompatibility to Checkstyle version >= 8.24 - Upgrade to 8.28
[
https://issues.apache.org/jira/browse/MCHECKSTYLE-384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Enrico Olivelli updated MCHECKSTYLE-384:
Fix Version/s: 3.1.1
> Incompatibility to Checkstyle version >= 8.24 - Upgrade to 8.28
>
>
> Key: MCHECKSTYLE-384
> URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-384
> Project: Maven Checkstyle Plugin
> Issue Type: Bug
> Components: checkstyle:check
>Affects Versions: 3.1.0
>Reporter: Martin
>Assignee: Enrico Olivelli
>Priority: Blocker
> Fix For: 3.1.1
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The latest {{maven-checkstyle-plugin}} is incompatible to Checkstyle version
> 8.24 and newer. The check for "LineLength" was moved from "TreeWalker" to
> "Checker".
> For further details see "Breaking backward compatibility" under
> https://checkstyle.org/releasenotes.html#Release_8.24
>
> {code:none|title=Maven Console Output}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-checkstyle-plugin:3.1.0:check (validate) on
> project top-secrect: Failed during checkstyle configuration: LineLength is
> not allowed as a child in Checker -> [Help 1]
> [ERROR] ...
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (MCHECKSTYLE-384) Incompatibility to Checkstyle version >= 8.24 - Upgrade to 8.28
[
https://issues.apache.org/jira/browse/MCHECKSTYLE-384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Enrico Olivelli updated MCHECKSTYLE-384:
Summary: Incompatibility to Checkstyle version >= 8.24 - Upgrade to 8.28
(was: Incompatibil ity to Checkstyle version >= 8.24 - Upgrade to 8.28)
> Incompatibility to Checkstyle version >= 8.24 - Upgrade to 8.28
>
>
> Key: MCHECKSTYLE-384
> URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-384
> Project: Maven Checkstyle Plugin
> Issue Type: Bug
> Components: checkstyle:check
>Affects Versions: 3.1.0
>Reporter: Martin
>Assignee: Enrico Olivelli
>Priority: Blocker
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The latest {{maven-checkstyle-plugin}} is incompatible to Checkstyle version
> 8.24 and newer. The check for "LineLength" was moved from "TreeWalker" to
> "Checker".
> For further details see "Breaking backward compatibility" under
> https://checkstyle.org/releasenotes.html#Release_8.24
>
> {code:none|title=Maven Console Output}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-checkstyle-plugin:3.1.0:check (validate) on
> project top-secrect: Failed during checkstyle configuration: LineLength is
> not allowed as a child in Checker -> [Help 1]
> [ERROR] ...
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (MCHECKSTYLE-389) MCHECKSTYLE-365 introduces regression with 'rules' aggregate count section on report
[ https://issues.apache.org/jira/browse/MCHECKSTYLE-389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Enrico Olivelli reassigned MCHECKSTYLE-389: --- Assignee: Enrico Olivelli > MCHECKSTYLE-365 introduces regression with 'rules' aggregate count section on > report > > > Key: MCHECKSTYLE-389 > URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-389 > Project: Maven Checkstyle Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.1.0 >Reporter: Jeremy Landis >Assignee: Enrico Olivelli >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > Commit eee0ba1 in CheckstyleReportGenerator.java sets the default 'severity' > is set as 'error'. The suggestion is that it fixes count issues per adjusted > comment at that time. While that may or may not be true, what it does do is > incorrectly shut down the entire section of rules aggregation counts in some > cases. The severity only takes into account that specific one to then > aggregate. Selecting just one other than null is going to mess up the logic > as implemented here. This change needs reverted for that one specific change > only. The original issue should be reopened as it was not properly fixed. > The IT tests fails to take into account individual types. It includes both > 'info' and 'error' thus the only reason it even works. > In my test case, I'm using 'mybatis-3'. I have configured it to use google > checks so nothing else setup. It has 0 info, 3151warnings, and 0 errors. > Switching it to any other value will cause it to only reflect that section. > So using 'info', nothing shows up. Using 'error' as coded now, nothing shows > up. Using 'warning', it does show up. Continuing to use null as originally > the case, it does show up. > There really was a miscount somewhere, but that was not the right fix. For > my test, I get a miscount of +5 if using 'warning' or the original null. > That is entirely better than nothing. And therefore, the best solution for > now is to revert this change. > While my test does not have a combination of issues in 'info', 'warning', and > 'error', presumably most do and thus why this was not reported after almost a > year since the release of 3.1.0. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [maven-checkstyle-plugin] eolivelli closed pull request #25: [MCHECKSTYLE-389] Partial revert of MCHECKSTYLE-365 severity change b…
eolivelli closed pull request #25: [MCHECKSTYLE-389] Partial revert of MCHECKSTYLE-365 severity change b… URL: https://github.com/apache/maven-checkstyle-plugin/pull/25 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [maven-checkstyle-plugin] eolivelli commented on issue #25: [MCHECKSTYLE-389] Partial revert of MCHECKSTYLE-365 severity change b…
eolivelli commented on issue #25: [MCHECKSTYLE-389] Partial revert of MCHECKSTYLE-365 severity change b… URL: https://github.com/apache/maven-checkstyle-plugin/pull/25#issuecomment-582908105 merged as de614e3ce5f4b4b7fc12e6cbd54189638e58a551 thank you @hazendaz This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [maven-checkstyle-plugin] eolivelli merged pull request #26: [MCHECKSTYLE-390] Upgrade to checkstyle 8.29
eolivelli merged pull request #26: [MCHECKSTYLE-390] Upgrade to checkstyle 8.29 URL: https://github.com/apache/maven-checkstyle-plugin/pull/26 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Updated] (DOXIA-603) RAT failures
[ https://issues.apache.org/jira/browse/DOXIA-603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elliotte Rusty Harold updated DOXIA-603: Description: mvn verify fails: Downloaded from central: [https://repo.maven.apache.org/maven2/org/apache/rat/apache-rat-core/0.13/apache-rat-core-0.13.jar] (128 kB at 696 kB/s) [INFO] Enabled default license matchers. [INFO] Will parse SCM ignores for exclusions... [INFO] Parsing exclusions from /home/elharo/maven-doxia-site/.gitignore [INFO] Finished adding exclusions from SCM ignore files. [INFO] 68 implicit excludes (use -debug for more details). [INFO] 5 explicit excludes (use -debug for more details). [INFO] 45 resources included (use -debug for more details) [INFO] Rat check: Summary over all files. Unapproved: 12, unknown: 12, generated: 0, approved: 30 licenses. [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 2.392 s [INFO] Finished at: 2020-02-06T07:37:23-05:00 [INFO] [ERROR] Failed to execute goal org.apache.rat:apache-rat-plugin:0.13:check (rat-check) on project doxia-site: Too many files with unapproved license: 12 See RAT report in: /home/elharo/maven-doxia-site/target/rat.txt -> [Help 1] [ERROR] was:home/elharo/maven-doxia-site/target/rat.txt > RAT failures > > > Key: DOXIA-603 > URL: https://issues.apache.org/jira/browse/DOXIA-603 > Project: Maven Doxia > Issue Type: Bug > Components: Documentation >Reporter: Elliotte Rusty Harold >Priority: Minor > Attachments: rat.txt > > > mvn verify fails: > > Downloaded from central: > [https://repo.maven.apache.org/maven2/org/apache/rat/apache-rat-core/0.13/apache-rat-core-0.13.jar] > (128 kB at 696 kB/s) > [INFO] Enabled default license matchers. > [INFO] Will parse SCM ignores for exclusions... > [INFO] Parsing exclusions from /home/elharo/maven-doxia-site/.gitignore > [INFO] Finished adding exclusions from SCM ignore files. > [INFO] 68 implicit excludes (use -debug for more details). > [INFO] 5 explicit excludes (use -debug for more details). > [INFO] 45 resources included (use -debug for more details) > [INFO] Rat check: Summary over all files. Unapproved: 12, unknown: 12, > generated: 0, approved: 30 licenses. > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 2.392 s > [INFO] Finished at: 2020-02-06T07:37:23-05:00 > [INFO] > > [ERROR] Failed to execute goal org.apache.rat:apache-rat-plugin:0.13:check > (rat-check) on project doxia-site: Too many files with unapproved license: 12 > See RAT report in: /home/elharo/maven-doxia-site/target/rat.txt -> [Help 1] > [ERROR] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (DOXIA-603) RAT failures
Elliotte Rusty Harold created DOXIA-603: --- Summary: RAT failures Key: DOXIA-603 URL: https://issues.apache.org/jira/browse/DOXIA-603 Project: Maven Doxia Issue Type: Bug Components: Documentation Reporter: Elliotte Rusty Harold Attachments: rat.txt home/elharo/maven-doxia-site/target/rat.txt -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (MNG-6861) RAT failures
[ https://issues.apache.org/jira/browse/MNG-6861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elliotte Rusty Harold resolved MNG-6861. Resolution: Invalid wrong component, oops > RAT failures > > > Key: MNG-6861 > URL: https://issues.apache.org/jira/browse/MNG-6861 > Project: Maven > Issue Type: Bug >Reporter: Elliotte Rusty Harold >Priority: Minor > > mvn verify fails: > > Downloaded from central: > https://repo.maven.apache.org/maven2/org/apache/rat/apache-rat-core/0.13/apache-rat-core-0.13.jar > (128 kB at 696 kB/s) > [INFO] Enabled default license matchers. > [INFO] Will parse SCM ignores for exclusions... > [INFO] Parsing exclusions from /home/elharo/maven-doxia-site/.gitignore > [INFO] Finished adding exclusions from SCM ignore files. > [INFO] 68 implicit excludes (use -debug for more details). > [INFO] 5 explicit excludes (use -debug for more details). > [INFO] 45 resources included (use -debug for more details) > [INFO] Rat check: Summary over all files. Unapproved: 12, unknown: 12, > generated: 0, approved: 30 licenses. > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 2.392 s > [INFO] Finished at: 2020-02-06T07:37:23-05:00 > [INFO] > > [ERROR] Failed to execute goal org.apache.rat:apache-rat-plugin:0.13:check > (rat-check) on project doxia-site: Too many files with unapproved license: 12 > See RAT report in: /home/elharo/maven-doxia-site/target/rat.txt -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e > switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please > read the following articles: > [ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (MNG-6861) RAT failures
[ https://issues.apache.org/jira/browse/MNG-6861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elliotte Rusty Harold closed MNG-6861. -- > RAT failures > > > Key: MNG-6861 > URL: https://issues.apache.org/jira/browse/MNG-6861 > Project: Maven > Issue Type: Bug >Reporter: Elliotte Rusty Harold >Priority: Minor > > mvn verify fails: > > Downloaded from central: > https://repo.maven.apache.org/maven2/org/apache/rat/apache-rat-core/0.13/apache-rat-core-0.13.jar > (128 kB at 696 kB/s) > [INFO] Enabled default license matchers. > [INFO] Will parse SCM ignores for exclusions... > [INFO] Parsing exclusions from /home/elharo/maven-doxia-site/.gitignore > [INFO] Finished adding exclusions from SCM ignore files. > [INFO] 68 implicit excludes (use -debug for more details). > [INFO] 5 explicit excludes (use -debug for more details). > [INFO] 45 resources included (use -debug for more details) > [INFO] Rat check: Summary over all files. Unapproved: 12, unknown: 12, > generated: 0, approved: 30 licenses. > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 2.392 s > [INFO] Finished at: 2020-02-06T07:37:23-05:00 > [INFO] > > [ERROR] Failed to execute goal org.apache.rat:apache-rat-plugin:0.13:check > (rat-check) on project doxia-site: Too many files with unapproved license: 12 > See RAT report in: /home/elharo/maven-doxia-site/target/rat.txt -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e > switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please > read the following articles: > [ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (MNG-6861) RAT failures
Elliotte Rusty Harold created MNG-6861: -- Summary: RAT failures Key: MNG-6861 URL: https://issues.apache.org/jira/browse/MNG-6861 Project: Maven Issue Type: Bug Reporter: Elliotte Rusty Harold mvn verify fails: Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/rat/apache-rat-core/0.13/apache-rat-core-0.13.jar (128 kB at 696 kB/s) [INFO] Enabled default license matchers. [INFO] Will parse SCM ignores for exclusions... [INFO] Parsing exclusions from /home/elharo/maven-doxia-site/.gitignore [INFO] Finished adding exclusions from SCM ignore files. [INFO] 68 implicit excludes (use -debug for more details). [INFO] 5 explicit excludes (use -debug for more details). [INFO] 45 resources included (use -debug for more details) [INFO] Rat check: Summary over all files. Unapproved: 12, unknown: 12, generated: 0, approved: 30 licenses. [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 2.392 s [INFO] Finished at: 2020-02-06T07:37:23-05:00 [INFO] [ERROR] Failed to execute goal org.apache.rat:apache-rat-plugin:0.13:check (rat-check) on project doxia-site: Too many files with unapproved license: 12 See RAT report in: /home/elharo/maven-doxia-site/target/rat.txt -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (MNG-6860) Internal Error verifying doxia
[ https://issues.apache.org/jira/browse/MNG-6860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elliotte Rusty Harold resolved MNG-6860. Fix Version/s: 3.6.3 Resolution: Fixed > Internal Error verifying doxia > -- > > Key: MNG-6860 > URL: https://issues.apache.org/jira/browse/MNG-6860 > Project: Maven > Issue Type: Bug >Reporter: Elliotte Rusty Harold >Priority: Major > Fix For: 3.6.3 > > > Checked out doxia-site from [https://github.com/apache/maven-doxia-site] and > ran mvn verify on Linux with JDK 8. > > I estimate there's three different errors here to make this happen. This > issue is for whatever in core is causing an InternalErrorException when > likely faced with a somehow broken project setup. > > elharo@elharo1:~/maven-doxia-site$ mvn verify > [INFO] Scanning for projects... > Downloading from apache.snapshots: > [https://repository.apache.org/snapshots/org/apache/maven/maven-parent/34-SNAPSHOT/maven-metadata.xml] > Downloading from apache.snapshots: > [https://repository.apache.org/snapshots/org/apache/apache/22-SNAPSHOT/maven-metadata.xml] > [ERROR] Internal error: java.lang.NullPointerException -> [Help 1] > org.apache.maven.InternalErrorException: Internal error: > java.lang.NullPointerException > at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:120) > at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956) > at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288) > at org.apache.maven.cli.MavenCli.main (MavenCli.java:192) > at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke > (NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke > (DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke (Method.java:498) > at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced > (Launcher.java:282) > at org.codehaus.plexus.classworlds.launcher.Launcher.launch > (Launcher.java:225) > at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode > (Launcher.java:406) > at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347) > Caused by: java.lang.NullPointerException > at org.apache.maven.model.plugin.DefaultReportingConverter.convert > (DefaultReportingConverter.java:243) > at org.apache.maven.model.plugin.DefaultReportingConverter.convert > (DefaultReportingConverter.java:213) > at org.apache.maven.model.plugin.DefaultReportingConverter.convertReporting > (DefaultReportingConverter.java:140) > at org.apache.maven.model.building.DefaultModelBuilder.build > (DefaultModelBuilder.java:479) > at org.apache.maven.model.building.DefaultModelBuilder.build > (DefaultModelBuilder.java:432) > at org.apache.maven.project.DefaultProjectBuilder.build > (DefaultProjectBuilder.java:616) > at org.apache.maven.project.DefaultProjectBuilder.build > (DefaultProjectBuilder.java:385) > at org.apache.maven.graph.DefaultGraphBuilder.collectProjects > (DefaultGraphBuilder.java:414) > at org.apache.maven.graph.DefaultGraphBuilder.getProjectsForMavenReactor > (DefaultGraphBuilder.java:405) > at org.apache.maven.graph.DefaultGraphBuilder.build > (DefaultGraphBuilder.java:82) > at org.apache.maven.DefaultMaven.buildGraph (DefaultMaven.java:507) > at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:219) > at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192) > at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105) > at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956) > at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288) > at org.apache.maven.cli.MavenCli.main (MavenCli.java:192) > at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke > (NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke > (DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke (Method.java:498) > at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced > (Launcher.java:282) > at org.codehaus.plexus.classworlds.launcher.Launcher.launch > (Launcher.java:225) > at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode > (Launcher.java:406) > at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347) > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e > switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please > read the following articles: > [ERROR] [Help 1] > [http://cwiki.apache.org/confluence/display/MAVEN/InternalErrorException] -- This message was sent by
[jira] [Closed] (MNG-6860) Internal Error verifying doxia
[ https://issues.apache.org/jira/browse/MNG-6860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elliotte Rusty Harold closed MNG-6860. -- > Internal Error verifying doxia > -- > > Key: MNG-6860 > URL: https://issues.apache.org/jira/browse/MNG-6860 > Project: Maven > Issue Type: Bug >Affects Versions: 3.6.1 >Reporter: Elliotte Rusty Harold >Priority: Major > Fix For: 3.6.3 > > > Checked out doxia-site from [https://github.com/apache/maven-doxia-site] and > ran mvn verify on Linux with JDK 8. > > I estimate there's three different errors here to make this happen. This > issue is for whatever in core is causing an InternalErrorException when > likely faced with a somehow broken project setup. > > elharo@elharo1:~/maven-doxia-site$ mvn verify > [INFO] Scanning for projects... > Downloading from apache.snapshots: > [https://repository.apache.org/snapshots/org/apache/maven/maven-parent/34-SNAPSHOT/maven-metadata.xml] > Downloading from apache.snapshots: > [https://repository.apache.org/snapshots/org/apache/apache/22-SNAPSHOT/maven-metadata.xml] > [ERROR] Internal error: java.lang.NullPointerException -> [Help 1] > org.apache.maven.InternalErrorException: Internal error: > java.lang.NullPointerException > at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:120) > at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956) > at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288) > at org.apache.maven.cli.MavenCli.main (MavenCli.java:192) > at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke > (NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke > (DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke (Method.java:498) > at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced > (Launcher.java:282) > at org.codehaus.plexus.classworlds.launcher.Launcher.launch > (Launcher.java:225) > at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode > (Launcher.java:406) > at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347) > Caused by: java.lang.NullPointerException > at org.apache.maven.model.plugin.DefaultReportingConverter.convert > (DefaultReportingConverter.java:243) > at org.apache.maven.model.plugin.DefaultReportingConverter.convert > (DefaultReportingConverter.java:213) > at org.apache.maven.model.plugin.DefaultReportingConverter.convertReporting > (DefaultReportingConverter.java:140) > at org.apache.maven.model.building.DefaultModelBuilder.build > (DefaultModelBuilder.java:479) > at org.apache.maven.model.building.DefaultModelBuilder.build > (DefaultModelBuilder.java:432) > at org.apache.maven.project.DefaultProjectBuilder.build > (DefaultProjectBuilder.java:616) > at org.apache.maven.project.DefaultProjectBuilder.build > (DefaultProjectBuilder.java:385) > at org.apache.maven.graph.DefaultGraphBuilder.collectProjects > (DefaultGraphBuilder.java:414) > at org.apache.maven.graph.DefaultGraphBuilder.getProjectsForMavenReactor > (DefaultGraphBuilder.java:405) > at org.apache.maven.graph.DefaultGraphBuilder.build > (DefaultGraphBuilder.java:82) > at org.apache.maven.DefaultMaven.buildGraph (DefaultMaven.java:507) > at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:219) > at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192) > at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105) > at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956) > at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288) > at org.apache.maven.cli.MavenCli.main (MavenCli.java:192) > at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke > (NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke > (DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke (Method.java:498) > at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced > (Launcher.java:282) > at org.codehaus.plexus.classworlds.launcher.Launcher.launch > (Launcher.java:225) > at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode > (Launcher.java:406) > at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347) > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e > switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please > read the following articles: > [ERROR] [Help 1] > [http://cwiki.apache.org/confluence/display/MAVEN/InternalErrorException] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MNG-6860) Internal Error verifying doxia
[ https://issues.apache.org/jira/browse/MNG-6860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elliotte Rusty Harold updated MNG-6860: --- Affects Version/s: 3.6.1 > Internal Error verifying doxia > -- > > Key: MNG-6860 > URL: https://issues.apache.org/jira/browse/MNG-6860 > Project: Maven > Issue Type: Bug >Affects Versions: 3.6.1 >Reporter: Elliotte Rusty Harold >Priority: Major > Fix For: 3.6.3 > > > Checked out doxia-site from [https://github.com/apache/maven-doxia-site] and > ran mvn verify on Linux with JDK 8. > > I estimate there's three different errors here to make this happen. This > issue is for whatever in core is causing an InternalErrorException when > likely faced with a somehow broken project setup. > > elharo@elharo1:~/maven-doxia-site$ mvn verify > [INFO] Scanning for projects... > Downloading from apache.snapshots: > [https://repository.apache.org/snapshots/org/apache/maven/maven-parent/34-SNAPSHOT/maven-metadata.xml] > Downloading from apache.snapshots: > [https://repository.apache.org/snapshots/org/apache/apache/22-SNAPSHOT/maven-metadata.xml] > [ERROR] Internal error: java.lang.NullPointerException -> [Help 1] > org.apache.maven.InternalErrorException: Internal error: > java.lang.NullPointerException > at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:120) > at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956) > at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288) > at org.apache.maven.cli.MavenCli.main (MavenCli.java:192) > at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke > (NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke > (DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke (Method.java:498) > at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced > (Launcher.java:282) > at org.codehaus.plexus.classworlds.launcher.Launcher.launch > (Launcher.java:225) > at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode > (Launcher.java:406) > at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347) > Caused by: java.lang.NullPointerException > at org.apache.maven.model.plugin.DefaultReportingConverter.convert > (DefaultReportingConverter.java:243) > at org.apache.maven.model.plugin.DefaultReportingConverter.convert > (DefaultReportingConverter.java:213) > at org.apache.maven.model.plugin.DefaultReportingConverter.convertReporting > (DefaultReportingConverter.java:140) > at org.apache.maven.model.building.DefaultModelBuilder.build > (DefaultModelBuilder.java:479) > at org.apache.maven.model.building.DefaultModelBuilder.build > (DefaultModelBuilder.java:432) > at org.apache.maven.project.DefaultProjectBuilder.build > (DefaultProjectBuilder.java:616) > at org.apache.maven.project.DefaultProjectBuilder.build > (DefaultProjectBuilder.java:385) > at org.apache.maven.graph.DefaultGraphBuilder.collectProjects > (DefaultGraphBuilder.java:414) > at org.apache.maven.graph.DefaultGraphBuilder.getProjectsForMavenReactor > (DefaultGraphBuilder.java:405) > at org.apache.maven.graph.DefaultGraphBuilder.build > (DefaultGraphBuilder.java:82) > at org.apache.maven.DefaultMaven.buildGraph (DefaultMaven.java:507) > at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:219) > at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192) > at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105) > at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956) > at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288) > at org.apache.maven.cli.MavenCli.main (MavenCli.java:192) > at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke > (NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke > (DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke (Method.java:498) > at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced > (Launcher.java:282) > at org.codehaus.plexus.classworlds.launcher.Launcher.launch > (Launcher.java:225) > at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode > (Launcher.java:406) > at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347) > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e > switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please > read the following articles: > [ERROR] [Help 1] > [http://cwiki.apache.org/confluence/display/MAVEN/InternalErrorException] -- This message was sent by
[jira] [Commented] (MNG-6860) Internal Error verifying doxia
[ https://issues.apache.org/jira/browse/MNG-6860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17031547#comment-17031547 ] Elliotte Rusty Harold commented on MNG-6860: Upgrading to 3.6.3 seems to have fixed this. > Internal Error verifying doxia > -- > > Key: MNG-6860 > URL: https://issues.apache.org/jira/browse/MNG-6860 > Project: Maven > Issue Type: Bug >Reporter: Elliotte Rusty Harold >Priority: Major > > Checked out doxia-site from [https://github.com/apache/maven-doxia-site] and > ran mvn verify on Linux with JDK 8. > > I estimate there's three different errors here to make this happen. This > issue is for whatever in core is causing an InternalErrorException when > likely faced with a somehow broken project setup. > > elharo@elharo1:~/maven-doxia-site$ mvn verify > [INFO] Scanning for projects... > Downloading from apache.snapshots: > [https://repository.apache.org/snapshots/org/apache/maven/maven-parent/34-SNAPSHOT/maven-metadata.xml] > Downloading from apache.snapshots: > [https://repository.apache.org/snapshots/org/apache/apache/22-SNAPSHOT/maven-metadata.xml] > [ERROR] Internal error: java.lang.NullPointerException -> [Help 1] > org.apache.maven.InternalErrorException: Internal error: > java.lang.NullPointerException > at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:120) > at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956) > at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288) > at org.apache.maven.cli.MavenCli.main (MavenCli.java:192) > at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke > (NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke > (DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke (Method.java:498) > at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced > (Launcher.java:282) > at org.codehaus.plexus.classworlds.launcher.Launcher.launch > (Launcher.java:225) > at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode > (Launcher.java:406) > at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347) > Caused by: java.lang.NullPointerException > at org.apache.maven.model.plugin.DefaultReportingConverter.convert > (DefaultReportingConverter.java:243) > at org.apache.maven.model.plugin.DefaultReportingConverter.convert > (DefaultReportingConverter.java:213) > at org.apache.maven.model.plugin.DefaultReportingConverter.convertReporting > (DefaultReportingConverter.java:140) > at org.apache.maven.model.building.DefaultModelBuilder.build > (DefaultModelBuilder.java:479) > at org.apache.maven.model.building.DefaultModelBuilder.build > (DefaultModelBuilder.java:432) > at org.apache.maven.project.DefaultProjectBuilder.build > (DefaultProjectBuilder.java:616) > at org.apache.maven.project.DefaultProjectBuilder.build > (DefaultProjectBuilder.java:385) > at org.apache.maven.graph.DefaultGraphBuilder.collectProjects > (DefaultGraphBuilder.java:414) > at org.apache.maven.graph.DefaultGraphBuilder.getProjectsForMavenReactor > (DefaultGraphBuilder.java:405) > at org.apache.maven.graph.DefaultGraphBuilder.build > (DefaultGraphBuilder.java:82) > at org.apache.maven.DefaultMaven.buildGraph (DefaultMaven.java:507) > at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:219) > at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192) > at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105) > at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956) > at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288) > at org.apache.maven.cli.MavenCli.main (MavenCli.java:192) > at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke > (NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke > (DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke (Method.java:498) > at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced > (Launcher.java:282) > at org.codehaus.plexus.classworlds.launcher.Launcher.launch > (Launcher.java:225) > at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode > (Launcher.java:406) > at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347) > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e > switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please > read the following articles: > [ERROR] [Help 1] > [http://cwiki.apache.org/confluence/display/MAVEN/InternalErrorException] -- This message was sent by
[jira] [Commented] (MNG-6860) Internal Error verifying doxia
[ https://issues.apache.org/jira/browse/MNG-6860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17031539#comment-17031539 ] Elliotte Rusty Harold commented on MNG-6860: Even a simple `mvn clean` reproduces this. Changing doxia-site to refer to a non-snapshot version does not fix the error. > Internal Error verifying doxia > -- > > Key: MNG-6860 > URL: https://issues.apache.org/jira/browse/MNG-6860 > Project: Maven > Issue Type: Bug >Reporter: Elliotte Rusty Harold >Priority: Major > > Checked out doxia-site from [https://github.com/apache/maven-doxia-site] and > ran mvn verify on Linux with JDK 8. > > I estimate there's three different errors here to make this happen. This > issue is for whatever in core is causing an InternalErrorException when > likely faced with a somehow broken project setup. > > elharo@elharo1:~/maven-doxia-site$ mvn verify > [INFO] Scanning for projects... > Downloading from apache.snapshots: > [https://repository.apache.org/snapshots/org/apache/maven/maven-parent/34-SNAPSHOT/maven-metadata.xml] > Downloading from apache.snapshots: > [https://repository.apache.org/snapshots/org/apache/apache/22-SNAPSHOT/maven-metadata.xml] > [ERROR] Internal error: java.lang.NullPointerException -> [Help 1] > org.apache.maven.InternalErrorException: Internal error: > java.lang.NullPointerException > at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:120) > at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956) > at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288) > at org.apache.maven.cli.MavenCli.main (MavenCli.java:192) > at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke > (NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke > (DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke (Method.java:498) > at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced > (Launcher.java:282) > at org.codehaus.plexus.classworlds.launcher.Launcher.launch > (Launcher.java:225) > at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode > (Launcher.java:406) > at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347) > Caused by: java.lang.NullPointerException > at org.apache.maven.model.plugin.DefaultReportingConverter.convert > (DefaultReportingConverter.java:243) > at org.apache.maven.model.plugin.DefaultReportingConverter.convert > (DefaultReportingConverter.java:213) > at org.apache.maven.model.plugin.DefaultReportingConverter.convertReporting > (DefaultReportingConverter.java:140) > at org.apache.maven.model.building.DefaultModelBuilder.build > (DefaultModelBuilder.java:479) > at org.apache.maven.model.building.DefaultModelBuilder.build > (DefaultModelBuilder.java:432) > at org.apache.maven.project.DefaultProjectBuilder.build > (DefaultProjectBuilder.java:616) > at org.apache.maven.project.DefaultProjectBuilder.build > (DefaultProjectBuilder.java:385) > at org.apache.maven.graph.DefaultGraphBuilder.collectProjects > (DefaultGraphBuilder.java:414) > at org.apache.maven.graph.DefaultGraphBuilder.getProjectsForMavenReactor > (DefaultGraphBuilder.java:405) > at org.apache.maven.graph.DefaultGraphBuilder.build > (DefaultGraphBuilder.java:82) > at org.apache.maven.DefaultMaven.buildGraph (DefaultMaven.java:507) > at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:219) > at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192) > at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105) > at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956) > at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288) > at org.apache.maven.cli.MavenCli.main (MavenCli.java:192) > at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke > (NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke > (DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke (Method.java:498) > at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced > (Launcher.java:282) > at org.codehaus.plexus.classworlds.launcher.Launcher.launch > (Launcher.java:225) > at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode > (Launcher.java:406) > at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347) > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e > switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please > read the following articles: > [ERROR] [Help 1] >
[jira] [Updated] (MNG-6860) Internal Error verifying doxia
[ https://issues.apache.org/jira/browse/MNG-6860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elliotte Rusty Harold updated MNG-6860: --- Description: Checked out doxia-site from [https://github.com/apache/maven-doxia-site] and ran mvn verify on Linux with JDK 8. I estimate there's three different errors here to make this happen. This issue is for whatever in core is causing an InternalErrorException when likely faced with a somehow broken project setup. elharo@elharo1:~/maven-doxia-site$ mvn verify [INFO] Scanning for projects... Downloading from apache.snapshots: [https://repository.apache.org/snapshots/org/apache/maven/maven-parent/34-SNAPSHOT/maven-metadata.xml] Downloading from apache.snapshots: [https://repository.apache.org/snapshots/org/apache/apache/22-SNAPSHOT/maven-metadata.xml] [ERROR] Internal error: java.lang.NullPointerException -> [Help 1] org.apache.maven.InternalErrorException: Internal error: java.lang.NullPointerException at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:120) at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956) at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288) at org.apache.maven.cli.MavenCli.main (MavenCli.java:192) at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke (Method.java:498) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282) at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406) at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347) Caused by: java.lang.NullPointerException at org.apache.maven.model.plugin.DefaultReportingConverter.convert (DefaultReportingConverter.java:243) at org.apache.maven.model.plugin.DefaultReportingConverter.convert (DefaultReportingConverter.java:213) at org.apache.maven.model.plugin.DefaultReportingConverter.convertReporting (DefaultReportingConverter.java:140) at org.apache.maven.model.building.DefaultModelBuilder.build (DefaultModelBuilder.java:479) at org.apache.maven.model.building.DefaultModelBuilder.build (DefaultModelBuilder.java:432) at org.apache.maven.project.DefaultProjectBuilder.build (DefaultProjectBuilder.java:616) at org.apache.maven.project.DefaultProjectBuilder.build (DefaultProjectBuilder.java:385) at org.apache.maven.graph.DefaultGraphBuilder.collectProjects (DefaultGraphBuilder.java:414) at org.apache.maven.graph.DefaultGraphBuilder.getProjectsForMavenReactor (DefaultGraphBuilder.java:405) at org.apache.maven.graph.DefaultGraphBuilder.build (DefaultGraphBuilder.java:82) at org.apache.maven.DefaultMaven.buildGraph (DefaultMaven.java:507) at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:219) at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192) at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105) at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956) at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288) at org.apache.maven.cli.MavenCli.main (MavenCli.java:192) at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke (Method.java:498) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282) at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406) at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347) [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] [http://cwiki.apache.org/confluence/display/MAVEN/InternalErrorException] was: Checked out doxia-site from [https://github.com/apache/maven-doxia-site] and ran mvn verify on a Mac with JDK 8. I estimate there's three different errors here to make this happen. This issue is for whatever in core is causing an InternalErrorException when likely faced with a somehow broken project setup. elharo@elharo1:~/maven-doxia-site$ mvn verify [INFO] Scanning for projects... Downloading from apache.snapshots: https://repository.apache.org/snapshots/org/apache/maven/maven-parent/34-SNAPSHOT/maven-metadata.xml Downloading from
[jira] [Commented] (MNG-6860) Internal Error verifying doxia
[ https://issues.apache.org/jira/browse/MNG-6860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17031524#comment-17031524 ] Elliotte Rusty Harold commented on MNG-6860: Indeed the snapshot is missing from the remote repo so that's one issue: [https://repository.apache.org/content/groups/snapshots/org/apache/maven/maven-parent/34-SNAPSHOT/] We should of course not throw an uncaught NullPointerException when this happens. > Internal Error verifying doxia > -- > > Key: MNG-6860 > URL: https://issues.apache.org/jira/browse/MNG-6860 > Project: Maven > Issue Type: Bug >Reporter: Elliotte Rusty Harold >Priority: Major > > Checked out doxia-site from [https://github.com/apache/maven-doxia-site] and > ran mvn verify on a Mac with JDK 8. > > I estimate there's three different errors here to make this happen. This > issue is for whatever in core is causing an InternalErrorException when > likely faced with a somehow broken project setup. > > elharo@elharo1:~/maven-doxia-site$ mvn verify > [INFO] Scanning for projects... > Downloading from apache.snapshots: > https://repository.apache.org/snapshots/org/apache/maven/maven-parent/34-SNAPSHOT/maven-metadata.xml > Downloading from apache.snapshots: > https://repository.apache.org/snapshots/org/apache/apache/22-SNAPSHOT/maven-metadata.xml > [ERROR] Internal error: java.lang.NullPointerException -> [Help 1] > org.apache.maven.InternalErrorException: Internal error: > java.lang.NullPointerException > at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:120) > at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956) > at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288) > at org.apache.maven.cli.MavenCli.main (MavenCli.java:192) > at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke > (NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke > (DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke (Method.java:498) > at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced > (Launcher.java:282) > at org.codehaus.plexus.classworlds.launcher.Launcher.launch > (Launcher.java:225) > at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode > (Launcher.java:406) > at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347) > Caused by: java.lang.NullPointerException > at org.apache.maven.model.plugin.DefaultReportingConverter.convert > (DefaultReportingConverter.java:243) > at org.apache.maven.model.plugin.DefaultReportingConverter.convert > (DefaultReportingConverter.java:213) > at org.apache.maven.model.plugin.DefaultReportingConverter.convertReporting > (DefaultReportingConverter.java:140) > at org.apache.maven.model.building.DefaultModelBuilder.build > (DefaultModelBuilder.java:479) > at org.apache.maven.model.building.DefaultModelBuilder.build > (DefaultModelBuilder.java:432) > at org.apache.maven.project.DefaultProjectBuilder.build > (DefaultProjectBuilder.java:616) > at org.apache.maven.project.DefaultProjectBuilder.build > (DefaultProjectBuilder.java:385) > at org.apache.maven.graph.DefaultGraphBuilder.collectProjects > (DefaultGraphBuilder.java:414) > at org.apache.maven.graph.DefaultGraphBuilder.getProjectsForMavenReactor > (DefaultGraphBuilder.java:405) > at org.apache.maven.graph.DefaultGraphBuilder.build > (DefaultGraphBuilder.java:82) > at org.apache.maven.DefaultMaven.buildGraph (DefaultMaven.java:507) > at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:219) > at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192) > at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105) > at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956) > at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288) > at org.apache.maven.cli.MavenCli.main (MavenCli.java:192) > at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke > (NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke > (DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke (Method.java:498) > at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced > (Launcher.java:282) > at org.codehaus.plexus.classworlds.launcher.Launcher.launch > (Launcher.java:225) > at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode > (Launcher.java:406) > at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347) > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e > switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about
[jira] [Commented] (MNG-6860) Internal Error verifying doxia
[ https://issues.apache.org/jira/browse/MNG-6860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17031522#comment-17031522 ] Elliotte Rusty Harold commented on MNG-6860: Apache Maven 3.6.1 (d66c9c0b3152b2e69ee9bac180bb8fcc8e6af555; 2019-04-04T15:00:29-04:00) Maven home: /opt/maven Java version: 1.8.0_232, vendor: Debian, runtime: /usr/lib/jvm/java-8-openjdk-amd64/jre Default locale: en_US, platform encoding: UTF-8 OS name: "linux", version: "5.2.17-1rodete3-amd64", arch: "amd64", family: "unix" [DEBUG] Created new class realm maven.api [DEBUG] Importing foreign packages into class realm maven.api [DEBUG] Imported: javax.annotation.* < plexus.core [DEBUG] Imported: javax.annotation.security.* < plexus.core [DEBUG] Imported: javax.enterprise.inject.* < plexus.core [DEBUG] Imported: javax.enterprise.util.* < plexus.core [DEBUG] Imported: javax.inject.* < plexus.core [DEBUG] Imported: org.apache.maven.* < plexus.core [DEBUG] Imported: org.apache.maven.artifact < plexus.core [DEBUG] Imported: org.apache.maven.classrealm < plexus.core [DEBUG] Imported: org.apache.maven.cli < plexus.core [DEBUG] Imported: org.apache.maven.configuration < plexus.core [DEBUG] Imported: org.apache.maven.exception < plexus.core [DEBUG] Imported: org.apache.maven.execution < plexus.core [DEBUG] Imported: org.apache.maven.execution.scope < plexus.core [DEBUG] Imported: org.apache.maven.lifecycle < plexus.core [DEBUG] Imported: org.apache.maven.model < plexus.core [DEBUG] Imported: org.apache.maven.monitor < plexus.core [DEBUG] Imported: org.apache.maven.plugin < plexus.core [DEBUG] Imported: org.apache.maven.profiles < plexus.core [DEBUG] Imported: org.apache.maven.project < plexus.core [DEBUG] Imported: org.apache.maven.reporting < plexus.core [DEBUG] Imported: org.apache.maven.repository < plexus.core [DEBUG] Imported: org.apache.maven.rtinfo < plexus.core [DEBUG] Imported: org.apache.maven.settings < plexus.core [DEBUG] Imported: org.apache.maven.toolchain < plexus.core [DEBUG] Imported: org.apache.maven.usability < plexus.core [DEBUG] Imported: org.apache.maven.wagon.* < plexus.core [DEBUG] Imported: org.apache.maven.wagon.authentication < plexus.core [DEBUG] Imported: org.apache.maven.wagon.authorization < plexus.core [DEBUG] Imported: org.apache.maven.wagon.events < plexus.core [DEBUG] Imported: org.apache.maven.wagon.observers < plexus.core [DEBUG] Imported: org.apache.maven.wagon.proxy < plexus.core [DEBUG] Imported: org.apache.maven.wagon.repository < plexus.core [DEBUG] Imported: org.apache.maven.wagon.resource < plexus.core [DEBUG] Imported: org.codehaus.classworlds < plexus.core [DEBUG] Imported: org.codehaus.plexus.* < plexus.core [DEBUG] Imported: org.codehaus.plexus.classworlds < plexus.core [DEBUG] Imported: org.codehaus.plexus.component < plexus.core [DEBUG] Imported: org.codehaus.plexus.configuration < plexus.core [DEBUG] Imported: org.codehaus.plexus.container < plexus.core [DEBUG] Imported: org.codehaus.plexus.context < plexus.core [DEBUG] Imported: org.codehaus.plexus.lifecycle < plexus.core [DEBUG] Imported: org.codehaus.plexus.logging < plexus.core [DEBUG] Imported: org.codehaus.plexus.personality < plexus.core [DEBUG] Imported: org.codehaus.plexus.util.xml.Xpp3Dom < plexus.core [DEBUG] Imported: org.codehaus.plexus.util.xml.pull.XmlPullParser < plexus.core [DEBUG] Imported: org.codehaus.plexus.util.xml.pull.XmlPullParserException < plexus.core [DEBUG] Imported: org.codehaus.plexus.util.xml.pull.XmlSerializer < plexus.core [DEBUG] Imported: org.eclipse.aether.* < plexus.core [DEBUG] Imported: org.eclipse.aether.artifact < plexus.core [DEBUG] Imported: org.eclipse.aether.collection < plexus.core [DEBUG] Imported: org.eclipse.aether.deployment < plexus.core [DEBUG] Imported: org.eclipse.aether.graph < plexus.core [DEBUG] Imported: org.eclipse.aether.impl < plexus.core [DEBUG] Imported: org.eclipse.aether.installation < plexus.core [DEBUG] Imported: org.eclipse.aether.internal.impl < plexus.core [DEBUG] Imported: org.eclipse.aether.metadata < plexus.core [DEBUG] Imported: org.eclipse.aether.repository < plexus.core [DEBUG] Imported: org.eclipse.aether.resolution < plexus.core [DEBUG] Imported: org.eclipse.aether.spi < plexus.core [DEBUG] Imported: org.eclipse.aether.transfer < plexus.core [DEBUG] Imported: org.eclipse.aether.version < plexus.core [DEBUG] Imported: org.fusesource.jansi.* < plexus.core [DEBUG] Imported: org.slf4j.* < plexus.core [DEBUG] Imported: org.slf4j.event.* < plexus.core [DEBUG] Imported: org.slf4j.helpers.* < plexus.core [DEBUG] Imported: org.slf4j.spi.* < plexus.core [DEBUG] Populating class realm maven.api [INFO] Error stacktraces are turned on. [DEBUG] Message scheme: color [DEBUG] Message styles: debug info warning error success failure strong mojo project [DEBUG] Reading global settings from /opt/maven/conf/settings.xml [DEBUG] Reading user settings from /home/elharo/.m2/settings.xml [DEBUG] Reading global
[jira] [Updated] (MNG-6846) conditional overwrite
[
https://issues.apache.org/jira/browse/MNG-6846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Elliotte Rusty Harold updated MNG-6846:
---
Priority: Major (was: Blocker)
> conditional overwrite
> -
>
> Key: MNG-6846
> URL: https://issues.apache.org/jira/browse/MNG-6846
> Project: Maven
> Issue Type: Bug
> Components: Bootstrap Build
>Affects Versions: 3.5.0-alpha-1, 3.5.0-beta-1, 3.5.0, 3.5.2, 3.5.3, 3.5.4,
> 3.6.0, 3.6.1, 3.6.2, 3.6.3
> Environment: os:windows
> maven:3.6.2
>Reporter: zhaoyx
>Priority: Major
> Labels: beginner, newbie
> Attachments: image-2020-01-10-20-51-23-490.png
>
> Original Estimate: 3h
> Remaining Estimate: 3h
>
> org.apache.maven.model.interpolation.AbstractStringBasedModelInterpolator＃createValueSources＃lin：167
> when I use dynamic ci, I find that if the variable ${reversion} exists in
> other projects, it will be forced to change the version. This part should be
> filtered out. We cannot control the version of other projects. I tested the
> sample used [mng-6846|https://github.com/zhaoyunxing92/mng-6846]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (MNG-6080) New scope for non-functional dependencies
[
https://issues.apache.org/jira/browse/MNG-6080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Elliotte Rusty Harold updated MNG-6080:
---
Priority: Major (was: Critical)
> New scope for non-functional dependencies
> -
>
> Key: MNG-6080
> URL: https://issues.apache.org/jira/browse/MNG-6080
> Project: Maven
> Issue Type: New Feature
> Components: Dependencies
>Affects Versions: 3.3.9
>Reporter: Paul Benedict
>Priority: Major
>
> Maven currently lacks a scope for artifacts that should not be part of the
> classpath. The classpath is the path that the Java Runtime Environment (JRE)
> searches for classes and other resource files. Given that the classpath is
> Java specific, this feature request can be generalized to accommodate
> artifacts that are not code related (directly or indirectly). It is neither
> code that executes (like a .class file = "directly") nor a resource file
> intimately linked to executable code (like a .properties file = "indirectly").
> For example, an organization may with to establish a Maven project that
> contains common look-and-feel elements to brand all their web applications.
> This project could be a ZIP archive to be included in downstream projects, in
> which each build explodes the archive into their respective web application
> context roots.
> Two names in the running for the new scope are {{"asset"}} and {{"reactor"}}.
> They are nearly equal but have a different slight emphasis. The {{"asset"}}
> name emphasizes purpose of artifact. The {{"reactor"}} name emphasizes
> purpose within the build. The Maven Team should decide among these two or
> propose a third.
> Thread where discussion originated:
> http://mail-archives.apache.org/mod_mbox/maven-dev/201608.mbox/%3CCABLGb9x5e3fE25Qj9DwvCsCSa1Dwe_e6%2BOmWjL0ZbQ07HLEm8g%40mail.gmail.com%3E
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (MNG-6860) Internal Error verifying doxia
Elliotte Rusty Harold created MNG-6860: -- Summary: Internal Error verifying doxia Key: MNG-6860 URL: https://issues.apache.org/jira/browse/MNG-6860 Project: Maven Issue Type: Bug Reporter: Elliotte Rusty Harold Checked out doxia-site from [https://github.com/apache/maven-doxia-site] and ran mvn verify on a Mac with JDK 8. I estimate there's three different errors here to make this happen. This issue is for whatever in core is causing an InternalErrorException when likely faced with a somehow broken project setup. elharo@elharo1:~/maven-doxia-site$ mvn verify [INFO] Scanning for projects... Downloading from apache.snapshots: https://repository.apache.org/snapshots/org/apache/maven/maven-parent/34-SNAPSHOT/maven-metadata.xml Downloading from apache.snapshots: https://repository.apache.org/snapshots/org/apache/apache/22-SNAPSHOT/maven-metadata.xml [ERROR] Internal error: java.lang.NullPointerException -> [Help 1] org.apache.maven.InternalErrorException: Internal error: java.lang.NullPointerException at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:120) at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956) at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288) at org.apache.maven.cli.MavenCli.main (MavenCli.java:192) at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke (Method.java:498) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282) at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406) at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347) Caused by: java.lang.NullPointerException at org.apache.maven.model.plugin.DefaultReportingConverter.convert (DefaultReportingConverter.java:243) at org.apache.maven.model.plugin.DefaultReportingConverter.convert (DefaultReportingConverter.java:213) at org.apache.maven.model.plugin.DefaultReportingConverter.convertReporting (DefaultReportingConverter.java:140) at org.apache.maven.model.building.DefaultModelBuilder.build (DefaultModelBuilder.java:479) at org.apache.maven.model.building.DefaultModelBuilder.build (DefaultModelBuilder.java:432) at org.apache.maven.project.DefaultProjectBuilder.build (DefaultProjectBuilder.java:616) at org.apache.maven.project.DefaultProjectBuilder.build (DefaultProjectBuilder.java:385) at org.apache.maven.graph.DefaultGraphBuilder.collectProjects (DefaultGraphBuilder.java:414) at org.apache.maven.graph.DefaultGraphBuilder.getProjectsForMavenReactor (DefaultGraphBuilder.java:405) at org.apache.maven.graph.DefaultGraphBuilder.build (DefaultGraphBuilder.java:82) at org.apache.maven.DefaultMaven.buildGraph (DefaultMaven.java:507) at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:219) at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192) at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105) at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956) at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288) at org.apache.maven.cli.MavenCli.main (MavenCli.java:192) at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke (Method.java:498) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282) at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406) at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347) [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/InternalErrorException -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (DOXIA-602) Upgrade test dependencies
[ https://issues.apache.org/jira/browse/DOXIA-602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated DOXIA-602: --- Summary: Upgrade test dependencies (was: Upgrade JUnit to 4.13) > Upgrade test dependencies > - > > Key: DOXIA-602 > URL: https://issues.apache.org/jira/browse/DOXIA-602 > Project: Maven Doxia > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Priority: Trivial > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (DOXIA-602) Upgrade test dependencies
[ https://issues.apache.org/jira/browse/DOXIA-602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated DOXIA-602: --- Description: * JUnit to 4.13 * XMLUnit to 2.6.3 > Upgrade test dependencies > - > > Key: DOXIA-602 > URL: https://issues.apache.org/jira/browse/DOXIA-602 > Project: Maven Doxia > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Priority: Trivial > > * JUnit to 4.13 > * XMLUnit to 2.6.3 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (DOXIA-602) Upgrade JUnit to 4.13
Sylwester Lachiewicz created DOXIA-602: -- Summary: Upgrade JUnit to 4.13 Key: DOXIA-602 URL: https://issues.apache.org/jira/browse/DOXIA-602 Project: Maven Doxia Issue Type: Dependency upgrade Reporter: Sylwester Lachiewicz -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MCHECKSTYLE-384) Incompatibil ity to Checkstyle version >= 8.24 - Upgrade to 8.28
[
https://issues.apache.org/jira/browse/MCHECKSTYLE-384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17031501#comment-17031501
]
Hudson commented on MCHECKSTYLE-384:
Build succeeded in Jenkins: Maven TLP » maven-checkstyle-plugin » master #45
See
https://builds.apache.org/job/maven-box/job/maven-checkstyle-plugin/job/master/45/
> Incompatibil ity to Checkstyle version >= 8.24 - Upgrade to 8.28
> -
>
> Key: MCHECKSTYLE-384
> URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-384
> Project: Maven Checkstyle Plugin
> Issue Type: Bug
> Components: checkstyle:check
>Affects Versions: 3.1.0
>Reporter: Martin
>Assignee: Enrico Olivelli
>Priority: Blocker
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The latest {{maven-checkstyle-plugin}} is incompatible to Checkstyle version
> 8.24 and newer. The check for "LineLength" was moved from "TreeWalker" to
> "Checker".
> For further details see "Breaking backward compatibility" under
> https://checkstyle.org/releasenotes.html#Release_8.24
>
> {code:none|title=Maven Console Output}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-checkstyle-plugin:3.1.0:check (validate) on
> project top-secrect: Failed during checkstyle configuration: LineLength is
> not allowed as a child in Checker -> [Help 1]
> [ERROR] ...
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (DOXIA-594) Problem while validating generated .fo: fo:block is not a valid child of fo:list-block
[
https://issues.apache.org/jira/browse/DOXIA-594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylwester Lachiewicz updated DOXIA-594:
---
Fix Version/s: 1.9.1
> Problem while validating generated .fo: fo:block is not a valid child of
> fo:list-block
> --
>
> Key: DOXIA-594
> URL: https://issues.apache.org/jira/browse/DOXIA-594
> Project: Maven Doxia
> Issue Type: Improvement
> Components: Module - FO
>Affects Versions: 1.9
>Reporter: Sylwester Lachiewicz
>Priority: Minor
> Fix For: 1.9.1
>
> Attachments: maven-pdf-plugin.fo, mvn-pdf-fo-snip.txt
>
>
> I have got validation error while generating PDF in maven-pdf plugin using
> command `mvn -Ppdf`
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-pdf-plugin:1.5.0-SNAPSHOT:pdf (default-cli) on
> project maven-pdf-plugin: Error during document generation: Error creating
> PDF from maven-pdf-plugin\target\pdf\maven-pdf-plugin.fo:
> org.apache.fop.fo.ValidationException:
> file:/maven-pdf-plugin/target/pdf/maven-pdf-plugin.fo:7709:13: "fo:block" is
> not a valid child of "fo:list-block"! (See position 7709:13) -> [Help 1]{code}
> Problematic generated block:
> {code:xml}
> space-before.optimum="10pt" provisional-distance-between-starts="1em"
> provisional-label-separation="1em">org.apache.maven.plugins:maven-pdf-plugin:maven-plugin:1.5.0-SNAPSHOT
> />\-org.apache.maven.reporting:maven-reporting-impl:jar:2.3:compile
> />\-commons-validator:commons-validator:jar:1.3.1:compile
> />\-commons-digester:commons-digester:jar:1.6:compile
> />\-(commons-beanutils:commons-beanutils:jar:1.6:compile
> - omitted for conflict with 1.7.0)
>
>
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (DOXIA-599) Remove element with name attribute and replace with id in element
[
https://issues.apache.org/jira/browse/DOXIA-599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylwester Lachiewicz updated DOXIA-599:
---
Fix Version/s: 1.9.1
> Remove element with name attribute and replace with id in element
> -
>
> Key: DOXIA-599
> URL: https://issues.apache.org/jira/browse/DOXIA-599
> Project: Maven Doxia
> Issue Type: Sub-task
>Reporter: Sylwester Lachiewicz
>Priority: Minor
> Fix For: 1.9.1
>
>
> *Warning*: The {{name}} attribute is obsolete. Consider putting an {{id}}
> attribute on the nearest container instead.
> From line 133, column 5; to line 133, column 53
> {{tion>↩**We}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Closed] (DOXIA-475) Support event attributes
[ https://issues.apache.org/jira/browse/DOXIA-475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz closed DOXIA-475. -- Resolution: Won't Fix > Support event attributes > > > Key: DOXIA-475 > URL: https://issues.apache.org/jira/browse/DOXIA-475 > Project: Maven Doxia > Issue Type: New Feature > Components: Core, Sink API >Affects Versions: 1.3 >Reporter: Lukas Theussl >Priority: Minor > > Currently Doxia does not support any of the [event > attributes|http://www.w3schools.com/tags/ref_eventattributes.asp], only > [standard > attributes|http://www.w3schools.com/tags/ref_standardattributes.asp] are > recognized by the sink API. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (DOXIA-540) Update/remove ancient information on Doxia site
[ https://issues.apache.org/jira/browse/DOXIA-540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated DOXIA-540: --- Fix Version/s: 1.9.1 > Update/remove ancient information on Doxia site > --- > > Key: DOXIA-540 > URL: https://issues.apache.org/jira/browse/DOXIA-540 > Project: Maven Doxia > Issue Type: Task > Components: Documentation >Affects Versions: 1.7 >Reporter: Michael Osipov >Priority: Major > Labels: up-for-grabs > Fix For: 1.9.1 > > > Tasks to perform: > * Remove [Developer Docs|http://maven.apache.org/doxia/] for ancient versions. > * Remove Doxia IDE intergration is there is none working > * Remove [Upgrading|http://maven.apache.org/doxia/upgrading.html], it is > overhauled. > * Check [FAQ|http://maven.apache.org/doxia/faq.html] for validity. > * Merge [Apt > Enhancements|http://maven.apache.org/doxia/references/doxia-apt.html] into > [main site|http://maven.apache.org/doxia/references/apt-format.html]. > * Check [Issues|http://maven.apache.org/doxia/issues/index.html] for > validity. > * Update [External Resources|http://maven.apache.org/doxia/resources.html]. > * Remove ancient information from [Sink > API|http://maven.apache.org/doxia/doxia/doxia-sink-api/index.html]. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (DOXIA-588) The Sink.JUSTIFY_XXX has no effect
[
https://issues.apache.org/jira/browse/DOXIA-588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylwester Lachiewicz updated DOXIA-588:
---
Fix Version/s: 1.9.1
> The Sink.JUSTIFY_XXX has no effect
> --
>
> Key: DOXIA-588
> URL: https://issues.apache.org/jira/browse/DOXIA-588
> Project: Maven Doxia
> Issue Type: Bug
>Reporter: QualiteSys QualiteSys
>Priority: Major
> Fix For: 1.9.1
>
>
> Hello
> I wish to use custom column alignments in tables.
> The Sink.JUSTIFY_LEFT or RIGHT seams not working.
>
> Is this code valid ?
> {code:java} sink.table();
> int[] j = {
> Sink.JUSTIFY_LEFT,
> Sink.JUSTIFY_RIGHT
> };
> sink.tableRows(j, true);{code}
> I haven't found examples up to now.
> Thanks for your help
> Didier
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Closed] (DOXIA-388) Use internal xdoc and fml xsds for validation when in offline mode
[ https://issues.apache.org/jira/browse/DOXIA-388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz closed DOXIA-388. -- Resolution: Won't Fix > Use internal xdoc and fml xsds for validation when in offline mode > -- > > Key: DOXIA-388 > URL: https://issues.apache.org/jira/browse/DOXIA-388 > Project: Maven Doxia > Issue Type: New Feature > Components: Module - Fml, Module - Xdoc, Module - Xhtml, Modules >Reporter: Lukas Theussl >Priority: Major > > I think that at least xdoc and fml (maybe xhtml) modules should include the > necessary files do enable validation without internet connection. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (DOXIA-598) Generated XHML5 content does not W3 HTML5 Validation Service
[ https://issues.apache.org/jira/browse/DOXIA-598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated DOXIA-598: --- Fix Version/s: 1.9.1 > Generated XHML5 content does not W3 HTML5 Validation Service > > > Key: DOXIA-598 > URL: https://issues.apache.org/jira/browse/DOXIA-598 > Project: Maven Doxia > Issue Type: Bug >Affects Versions: 1.9 >Reporter: Michael Osipov >Priority: Major > Fix For: 1.9.1 > > > Several parts of the pages fail. Each failure class shall be documented with > a sub task. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [maven-checkstyle-plugin] eolivelli opened a new pull request #26: [MCHECKSTYLE-390] Upgrade to checkstyle 8.29
eolivelli opened a new pull request #26: [MCHECKSTYLE-390] Upgrade to checkstyle 8.29 URL: https://github.com/apache/maven-checkstyle-plugin/pull/26 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [maven-checkstyle-plugin] eolivelli commented on issue #26: [MCHECKSTYLE-390] Upgrade to checkstyle 8.29
eolivelli commented on issue #26: [MCHECKSTYLE-390] Upgrade to checkstyle 8.29 URL: https://github.com/apache/maven-checkstyle-plugin/pull/26#issuecomment-582856086 waiting for CI https://builds.apache.org/job/maven-box/job/maven-checkstyle-plugin/job/MCHECKSTYLE-390/ This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Created] (MCHECKSTYLE-390) Upgrade to checkstyle 8.29
Enrico Olivelli created MCHECKSTYLE-390: --- Summary: Upgrade to checkstyle 8.29 Key: MCHECKSTYLE-390 URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-390 Project: Maven Checkstyle Plugin Issue Type: Improvement Affects Versions: 3.1.0 Reporter: Enrico Olivelli Assignee: Enrico Olivelli Fix For: 3.1.1 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [maven-checkstyle-plugin] eolivelli commented on issue #25: [MCHECKSTYLE-389] Partial revert of MCHECKSTYLE-365 severity change b…
eolivelli commented on issue #25: [MCHECKSTYLE-389] Partial revert of MCHECKSTYLE-365 severity change b… URL: https://github.com/apache/maven-checkstyle-plugin/pull/25#issuecomment-582854622 rebased onto current master waiting for CI again https://builds.apache.org/job/maven-box/job/maven-checkstyle-plugin/job/MCHECKSTYLE-389/ This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Commented] (MCHECKSTYLE-384) Incompatibil ity to Checkstyle version >= 8.24 - Upgrade to 8.28
[
https://issues.apache.org/jira/browse/MCHECKSTYLE-384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17031479#comment-17031479
]
Enrico Olivelli commented on MCHECKSTYLE-384:
-
[~hazendaz] I can't set you as Assignee, btw I have merged your patch as
e1e2f28620e2baed8351fea5fa524e98749df55c
I am going to upgrade to 8.29 and then cut a release
> Incompatibil ity to Checkstyle version >= 8.24 - Upgrade to 8.28
> -
>
> Key: MCHECKSTYLE-384
> URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-384
> Project: Maven Checkstyle Plugin
> Issue Type: Bug
> Components: checkstyle:check
>Affects Versions: 3.1.0
>Reporter: Martin
>Assignee: Enrico Olivelli
>Priority: Blocker
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The latest {{maven-checkstyle-plugin}} is incompatible to Checkstyle version
> 8.24 and newer. The check for "LineLength" was moved from "TreeWalker" to
> "Checker".
> For further details see "Breaking backward compatibility" under
> https://checkstyle.org/releasenotes.html#Release_8.24
>
> {code:none|title=Maven Console Output}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-checkstyle-plugin:3.1.0:check (validate) on
> project top-secrect: Failed during checkstyle configuration: LineLength is
> not allowed as a child in Checker -> [Help 1]
> [ERROR] ...
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (MCHECKSTYLE-384) Incompatibility to Checkstyle version >= 8.24
[
https://issues.apache.org/jira/browse/MCHECKSTYLE-384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Enrico Olivelli reassigned MCHECKSTYLE-384:
---
Assignee: Enrico Olivelli
> Incompatibility to Checkstyle version >= 8.24
> --
>
> Key: MCHECKSTYLE-384
> URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-384
> Project: Maven Checkstyle Plugin
> Issue Type: Bug
> Components: checkstyle:check
>Affects Versions: 3.1.0
>Reporter: Martin
>Assignee: Enrico Olivelli
>Priority: Blocker
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The latest {{maven-checkstyle-plugin}} is incompatible to Checkstyle version
> 8.24 and newer. The check for "LineLength" was moved from "TreeWalker" to
> "Checker".
> For further details see "Breaking backward compatibility" under
> https://checkstyle.org/releasenotes.html#Release_8.24
>
> {code:none|title=Maven Console Output}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-checkstyle-plugin:3.1.0:check (validate) on
> project top-secrect: Failed during checkstyle configuration: LineLength is
> not allowed as a child in Checker -> [Help 1]
> [ERROR] ...
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (MCHECKSTYLE-384) Incompatibil ity to Checkstyle version >= 8.24 - Upgrade to 8.28
[
https://issues.apache.org/jira/browse/MCHECKSTYLE-384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Enrico Olivelli updated MCHECKSTYLE-384:
Summary: Incompatibil ity to Checkstyle version >= 8.24 - Upgrade to 8.28
(was: Incompatibility to Checkstyle version >= 8.24 )
> Incompatibil ity to Checkstyle version >= 8.24 - Upgrade to 8.28
> -
>
> Key: MCHECKSTYLE-384
> URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-384
> Project: Maven Checkstyle Plugin
> Issue Type: Bug
> Components: checkstyle:check
>Affects Versions: 3.1.0
>Reporter: Martin
>Assignee: Enrico Olivelli
>Priority: Blocker
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The latest {{maven-checkstyle-plugin}} is incompatible to Checkstyle version
> 8.24 and newer. The check for "LineLength" was moved from "TreeWalker" to
> "Checker".
> For further details see "Breaking backward compatibility" under
> https://checkstyle.org/releasenotes.html#Release_8.24
>
> {code:none|title=Maven Console Output}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-checkstyle-plugin:3.1.0:check (validate) on
> project top-secrect: Failed during checkstyle configuration: LineLength is
> not allowed as a child in Checker -> [Help 1]
> [ERROR] ...
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[GitHub] [maven-checkstyle-plugin] eolivelli commented on issue #24: [MCHECKSTYLE-384] Update IT tests to support checkstyle 8.28
eolivelli commented on issue #24: [MCHECKSTYLE-384] Update IT tests to support checkstyle 8.28 URL: https://github.com/apache/maven-checkstyle-plugin/pull/24#issuecomment-582853379 merged as e1e2f28620e2baed8351fea5fa524e98749df55c thank you @hazendaz This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [maven-invoker-plugin] pzygielo opened a new pull request #10: (doc) Fix example invoker.properties
pzygielo opened a new pull request #10: (doc) Fix example invoker.properties URL: https://github.com/apache/maven-invoker-plugin/pull/10 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Updated] (MCOMPILER-394) Stackoverflow while compiling Java Sources, but works after renaming project directory
[
https://issues.apache.org/jira/browse/MCOMPILER-394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Markus Bader updated MCOMPILER-394:
---
Environment: The problem occurs with Windows 10, Windows 7 and also with
Ubuntu. (was: The problem occurs with Windows 10 and also with Windows 7.)
> Stackoverflow while compiling Java Sources, but works after renaming project
> directory
> --
>
> Key: MCOMPILER-394
> URL: https://issues.apache.org/jira/browse/MCOMPILER-394
> Project: Maven Compiler Plugin
> Issue Type: Bug
>Affects Versions: 3.1
> Environment: The problem occurs with Windows 10, Windows 7 and also
> with Ubuntu.
>Reporter: Markus Bader
>Priority: Major
> Attachments: build.log
>
>
> Me and one of my colleagues have following problem (others do not): We want
> to build a maven project, but "mvn clean install" ends up in a stackoverflow
> error. But after renaming the project directory, it works. Also after
> renaming the name of the parent directory and leaving the name of the project
> directory by its original value, compilation is possible.
> I also tried changing the artifactId so that it doesn't match the folder
> name. Result: stackoverflow.
> To make it more strange: I tried to reduce the used Java classes for possibly
> identifying a class to be responsible for this phenomenon. Therefor I deleted
> a class named "MathParser" and after that compilation was possible. So I
> analysed the content of the class and found out, that the stackoverflow error
> occurs even if the class ist nearly empty. With following content I can
> reproduce the error:
>
> {code:java}
> package some.anonymised.package;
> public class MathParser {
> private void doSomething(String func) throws Exception {
> throw new Exception ("function '" + func + "' is not defined");
> }
> } {code}
> With an empty method body, the build works fine.
> I attached the log created with debug option activated (with reduced number
> of classes and reduced content of MathParser). For anonymisation purposes I
> replaced the name of some directories, packages etc. by "x".
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[GitHub] [maven-checkstyle-plugin] eolivelli commented on issue #24: [MCHECKSTYLE-384] Update IT tests to support checkstyle 8.28
eolivelli commented on issue #24: [MCHECKSTYLE-384] Update IT tests to support checkstyle 8.28 URL: https://github.com/apache/maven-checkstyle-plugin/pull/24#issuecomment-582839031 I did not rebase and squash all of the commits. I have re-launched CI This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [maven-checkstyle-plugin] eolivelli commented on issue #24: [MCHECKSTYLE-384] Update IT tests to support checkstyle 8.28
eolivelli commented on issue #24: [MCHECKSTYLE-384] Update IT tests to support checkstyle 8.28 URL: https://github.com/apache/maven-checkstyle-plugin/pull/24#issuecomment-582839070 https://builds.apache.org/job/maven-box/job/maven-checkstyle-plugin/job/MCHECKSTYLE-384/ This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Commented] (MCOMPILER-394) Stackoverflow while compiling Java Sources, but works after renaming project directory
[
https://issues.apache.org/jira/browse/MCOMPILER-394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17031445#comment-17031445
]
Markus Bader commented on MCOMPILER-394:
Update: We've now renamed the root folder which fixed the problem - for a few
weeks. After that the issue came back - even Jenkins runs into the problem now
and then.
> Stackoverflow while compiling Java Sources, but works after renaming project
> directory
> --
>
> Key: MCOMPILER-394
> URL: https://issues.apache.org/jira/browse/MCOMPILER-394
> Project: Maven Compiler Plugin
> Issue Type: Bug
>Affects Versions: 3.1
> Environment: The problem occurs with Windows 10 and also with Windows
> 7.
>Reporter: Markus Bader
>Priority: Major
> Attachments: build.log
>
>
> Me and one of my colleagues have following problem (others do not): We want
> to build a maven project, but "mvn clean install" ends up in a stackoverflow
> error. But after renaming the project directory, it works. Also after
> renaming the name of the parent directory and leaving the name of the project
> directory by its original value, compilation is possible.
> I also tried changing the artifactId so that it doesn't match the folder
> name. Result: stackoverflow.
> To make it more strange: I tried to reduce the used Java classes for possibly
> identifying a class to be responsible for this phenomenon. Therefor I deleted
> a class named "MathParser" and after that compilation was possible. So I
> analysed the content of the class and found out, that the stackoverflow error
> occurs even if the class ist nearly empty. With following content I can
> reproduce the error:
>
> {code:java}
> package some.anonymised.package;
> public class MathParser {
> private void doSomething(String func) throws Exception {
> throw new Exception ("function '" + func + "' is not defined");
> }
> } {code}
> With an empty method body, the build works fine.
> I attached the log created with debug option activated (with reduced number
> of classes and reduced content of MathParser). For anonymisation purposes I
> replaced the name of some directories, packages etc. by "x".
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[GitHub] [maven-surefire] ajohnstonTE commented on issue #269: [SUREFIRE-1748] Fix reporting of empty stack trace messages
ajohnstonTE commented on issue #269: [SUREFIRE-1748] Fix reporting of empty stack trace messages URL: https://github.com/apache/maven-surefire/pull/269#issuecomment-582795866 Sure, I'll help out on that. If I understand you correctly, the change would be: Rather than encoding the events as values separated by colons, with there being an expected number of values in expected positions for the different event types, it would instead serialize the events into JSON. That JSON would get serialized into base64, then consumed on the other end and deserialized back into JSON, and finally deserialized back into the original event classes. That sound right? This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
