[jira] [Updated] (MNG-8286) Add a condition profile based on a simple expressions
[
https://issues.apache.org/jira/browse/MNG-8286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet updated MNG-8286:
-
Component/s: Profiles
> Add a condition profile based on a simple expressions
> -
>
> Key: MNG-8286
> URL: https://issues.apache.org/jira/browse/MNG-8286
> Project: Maven
> Issue Type: New Feature
> Components: Profiles
>Reporter: Guillaume Nodet
>Assignee: Guillaume Nodet
>Priority: Major
> Fix For: 4.0.0-beta-5
>
>
> GitHub Pull Request: [https://github.com/apache/maven/pull/1771]
> h1. Condition-Based Profile Activation in Maven
> In addition to the traditional activation mechanisms (JDK version, OS
> properties, file existence, etc.), Maven now supports a powerful
> condition-based activation through the condition field. This new mechanism
> allows for more flexible and expressive profile activation rules.
> h2. Condition Syntax
> The condition is specified as a string expression that can include various
> functions, comparisons, and logical operators.
> Some key features include:
> Property access: {{{}$\{property.name{
> Comparison operators: {{{}=={}}}, {{{}!={}}}, {{{}<{}}}, {{{}>{}}},
> {{{}<={}}}, {{>=}}
> Logical operators: {{&&}} (AND), {{||}} (OR), {{not(...)}}
> Functions: {{{}exists(...){}}}, {{{}missing(...){}}}, {{{}matches(...){}}},
> {{{}inrange(...){}}}, and more
> h2. Supported Functions
> The following functions are supported in condition expressions:
> * {{{}length(string){}}}: Returns the length of the given string.
> * {{{}upper(string){}}}: Converts the string to uppercase.
> * {{{}lower(string){}}}: Converts the string to lowercase.
> * {{{}substring(string, start, [end]){}}}: Returns a substring of the given
> string.
> * {{{}indexOf(string, substring){}}}: Returns the index of the first
> occurrence of substring in string, or -1 if not found.
> * {{{}contains(string, substring){}}}: Checks if the string contains the
> substring.
> * {{{}matches(string, regex){}}}: Checks if the string matches the given
> regular expression.
> * {{{}not(condition){}}}: Negates the given condition.
> * {{{}if(condition, trueValue, falseValue){}}}: Returns trueValue if the
> condition is true, falseValue otherwise.
> * {{{}exists(path){}}}: Checks if the file or directory at the given path
> exists.
> * {{{}missing(path){}}}: Checks if the file or directory at the given path
> does not exist.
> * {{{}inrange(version, range){}}}: Checks if the given version is within the
> specified version range.
> h2. Examples
> * JDK version range: {{inrange(${java.version}, '[11,)')}} (JDK 11 or higher)
> * OS check: {{${os.name} == 'windows'}}
> * File existence: {{exists('${project.basedir}/some-file.txt')}}
> * Property check: {{${my.property} != 'some-value'}}
> * Regex matching: {{matches(${os.version}, '.*aws')}}
> * Complex condition: {{${os.name} == 'windows' && ${os.arch} != 'amd64' &&
> inrange(${os.version}, '[10,)')}}
> * String length check: {{length(${user.name}) > 5}}
> * Substring with version: {{substring(${java.version}, 0, 3) == '1.8'}}
> * Using indexOf: {{indexOf(${java.version}, '-') > 0}}
> * Conditional logic: {{if(contains(${java.version}, '\-'),
> substring(${java.version}, 0, indexOf(${java.version}, '-')),
> ${java.version})}}
> This flexible condition mechanism allows for more precise control over
> profile activation, enabling developers to create profiles that respond to a
> wide range of environmental factors and project states.
> This will be triggered using a new profile activation in the 4.1.0 model:
> {code:xml}
>
>
> inrange(${maven.version}, '[4,)')
>
>
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-5761) Dependency management is not transitive.
[ https://issues.apache.org/jira/browse/MNG-5761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17887170#comment-17887170 ] Christian Schulte commented on MNG-5761: DefaultDependencyManager goes back to Maven 3.4, which never got released. So this is what should have been the default behaviour from day one. I am no longer doing Java development. To make a long story short. I took a look at the Jira issues somewhen 2015 or so - one of those you seem to have reopened - and just fixed inconsistencies, bugs and such. This was not possible due to integration tests starting to fail - no matter if the test was testing correct behaviour or not. It was then decided to reset almost all of my work and retain behaviour - even if inconsistent or just not behaving as advertised. I kept a 3.4-SNAPSHOT version in my private Github repository. You can download it from there and you will soon get, why nothing of that will ever land in an official release. When it was clear, there will be no more changes in resolution behaviour for pom 4.0, I added some warning messages as well. That's the version I did run locally somewhen 7 years ago and I would run locally, when I would still be doing Java things. I do not even know, if it still works at all. I read the notification mail by accident, when configuration my spam filter. [3.4-SNAPSHOT|https://github.com/ChristianSchulte/maven/releases/tag/2017-11-27] > Dependency management is not transitive. > > > Key: MNG-5761 > URL: https://issues.apache.org/jira/browse/MNG-5761 > Project: Maven > Issue Type: Bug > Components: Dependencies >Affects Versions: 3.2.5 >Reporter: Jeff Schnitzer >Priority: Critical > Fix For: 4.0.x-candidate > > Attachments: MNG-5761.zip, depending-pom2.xml > > > A detailed description of the issue is here: > http://stackoverflow.com/questions/28312975/maven-dependencymanagement-version-ignored-in-transitive-dependencies > The short of it is that maven appears to be using the wrong > version in a transitive dependency. There are two > relevant sections in the build, one pulled in by guice > and one pulled in by gwizard-parent. These are the dependency paths from the > top: > gwizard-example -> gwizard-config -> gwizard-parent > gwizard-example -> gwizard-config -> guice -> guice-parent > gwizard-parent's dependencyManagement specifies guava 18 > guice-parent's dependencyManagement specifies guava 16 > Guava 16 is winning. This seems highly undesirable, and in fact it breaks our > build. I would expect that in a version # fight, "closest to the top" should > win. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MJAR-314) Use a predefined constant for project.build.outputTimestamp
Sergey Ponomarev created MJAR-314:
-
Summary: Use a predefined constant for
project.build.outputTimestamp
Key: MJAR-314
URL: https://issues.apache.org/jira/browse/MJAR-314
Project: Maven JAR Plugin
Issue Type: Improvement
Reporter: Sergey Ponomarev
The "Configuring for Reproducible Builds" guide shows and example how to
specify a static outputTimestamp:
2023-01-01T00:00:00Z
The date inside is really doesn't matter and I used the property as is but was
afraid of being asked on a review why the 2023 year was used so used the
current year.
But still during a review I was asked:
bq. these changes are likely going to confuse future developers ("This date
shouldn't be static! Lets make it a variable!").
The Gradle has an option preserveFileTimestamps = false that will just put 1
Feb 1980 as a date. The 1 Jan 1980 is a minimal date in Zip archive but the 1
Jan has some special treatment by Java that's why the Gradle team used the 1
Feb.
See more detailed description in CONSTANT_TIME_FOR_ZIP_ENTRIES
https://github.com/gradle/gradle/blob/master/platforms/core-runtime/files/src/main/java/org/gradle/api/internal/file/archive/ZipEntryConstants.java#L39
I don't think it worth to declare some new property e.g.
true
But we can simply make a special constant value like:
REPRODUCIBLE_BUILD_STATIC_DATE
Then the constant will be replaced with the same 1 Feb 1980 to be similar with
Gradle produced artifacts.
This constant should make it more clear intention of the outputTimestamp but
also easier to find an explanation for this.
The outputTimestamp parsing is performed in the maven-archiver but the
maven-compiler-plugin and maven-jar-plugin would need to update a JavaDoc for
the outputTimestamp config option
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MJAR-314) Use a predefined constant for project.build.outputTimestamp
[
https://issues.apache.org/jira/browse/MJAR-314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17887155#comment-17887155
]
Sergey Ponomarev commented on MJAR-314:
---
I created a PR https://github.com/apache/maven-archiver/pull/72
The main problem is that users may try to use the constant with older plugin
versions and get an error "Text 'REPRODUCIBLE_BUILD_STATIC_DATE' could not be
parsed at index 0".
They'll have to upgrade the jar plugin, likely it's safe to upgrade it without
any problems.
> Use a predefined constant for project.build.outputTimestamp
> ---
>
> Key: MJAR-314
> URL: https://issues.apache.org/jira/browse/MJAR-314
> Project: Maven JAR Plugin
> Issue Type: Improvement
>Reporter: Sergey Ponomarev
>Priority: Major
>
> The "Configuring for Reproducible Builds" guide shows and example how to
> specify a static outputTimestamp:
>
> 2023-01-01T00:00:00Z
> The date inside is really doesn't matter and I used the property as is but
> was afraid of being asked on a review why the 2023 year was used so used the
> current year.
> But still during a review I was asked:
> bq. these changes are likely going to confuse future developers ("This date
> shouldn't be static! Lets make it a variable!").
> The Gradle has an option preserveFileTimestamps = false that will just put 1
> Feb 1980 as a date. The 1 Jan 1980 is a minimal date in Zip archive but the 1
> Jan has some special treatment by Java that's why the Gradle team used the 1
> Feb.
> See more detailed description in CONSTANT_TIME_FOR_ZIP_ENTRIES
> https://github.com/gradle/gradle/blob/master/platforms/core-runtime/files/src/main/java/org/gradle/api/internal/file/archive/ZipEntryConstants.java#L39
> I don't think it worth to declare some new property e.g.
> true
> But we can simply make a special constant value like:
>
> REPRODUCIBLE_BUILD_STATIC_DATE
> Then the constant will be replaced with the same 1 Feb 1980 to be similar
> with Gradle produced artifacts.
> This constant should make it more clear intention of the outputTimestamp but
> also easier to find an explanation for this.
> The outputTimestamp parsing is performed in the maven-archiver but the
> maven-compiler-plugin and maven-jar-plugin would need to update a JavaDoc for
> the outputTimestamp config option
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (DOXIATOOLS-84) Emit Velocity statements in special Sink events which prevent wrong escaping
[
https://issues.apache.org/jira/browse/DOXIATOOLS-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17887139#comment-17887139
]
Konrad Windszus commented on DOXIATOOLS-84:
---
The SinkWrapper approach does not work, as after parsing the original VLT
statements can no longer be reconstructed (missing new lines, ...).
Even when doing the separation of VLT and regular output before doing the
actual doxia source parsing you might end up with an invalid sequence of Sink
methods (as the VLT semantics are not taken into account there).
> Emit Velocity statements in special Sink events which prevent wrong escaping
>
>
> Key: DOXIATOOLS-84
> URL: https://issues.apache.org/jira/browse/DOXIATOOLS-84
> Project: Maven Doxia Tools
> Issue Type: Improvement
> Components: Doxia Converter
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
>Priority: Major
>
> Velocity is often used together with markup
> (https://maven.apache.org/plugins/maven-site-plugin/examples/creating-content.html#Filtering).
> When parsing markup including Velocity statements (directives, references
> and comments) those are included in the regular {{Sink.text(...)}} event.
> Therefore it is often incorrectly escaped when being emitted by a Sink.
> Although usually Velocity is supposed to be executed *before* markup is
> passed to a parser, there are cases where one wants to retain the Velocity
> statements and references in the markup (e.g. for converting from one format
> to another with https://maven.apache.org/doxia/doxia-tools/doxia-converter/).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ARCHETYPE-505) archetype:create-from-project,the .gitignore file not copy to archetype-resources
[
https://issues.apache.org/jira/browse/ARCHETYPE-505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17887140#comment-17887140
]
Slawomir Jaranowski commented on ARCHETYPE-505:
---
There is an option: {{useDefaultExcludes}}
https://maven.apache.org/archetype/maven-archetype-plugin/faq.html#excludes
> archetype:create-from-project,the .gitignore file not copy to
> archetype-resources
> -
>
> Key: ARCHETYPE-505
> URL: https://issues.apache.org/jira/browse/ARCHETYPE-505
> Project: Maven Archetype
> Issue Type: Bug
> Components: Archetypes
>Affects Versions: 2.4
> Environment: maven 3.3 ,maven-archetype-plugin 2.4
>Reporter: feilong
>Priority: Major
> Attachments: webapp-springmvc32.zip
>
>
> I have a very simple maven test project for {{archetype:create-from-project}}
> such as :(you can download from the Attachment)
> {noformat}
> | .gitignore
> | pom.xml
> |
> \---src
> +---main
> | \---java
> | overview.html
> |
> \---test
> {noformat}
> only {{.gitignore}} and {{pom.xml}}, and {{overview.html}} files
> and I excute the command line in the root folder:
> {code:xml}
> mvn -X archetype:create-from-project
> {code}
> I see ,in the
> {{target\generated-sources\archetype\src\main\resources\archetype-resources}}
> folder, only
> {noformat}
> | pom.xml
> |
> \---src
> \---main
> \---java
> overview.html
> {noformat}
> no {{.gitignore}} file
>
> first , I search the same issue in jira, there is #ARCHETYPE-474 , but not as
> my scene
>
> I search some solution in stackoverflow
> http://stackoverflow.com/questions/7981060/maven-archetype-plugin-doesnt-let-resources-in-archetype-resources-through#answer-37322323
> In pom.xml,I have also configed that
> {code:xml}
>
> maven-resources-plugin
> 3.0.1
>
> utf-8
> true
> false
>
>
>
> default-resources
> process-resources
>
> resources
>
>
> true
>
>
>
> default-testResources
> process-test-resources
>
> testResources
>
>
>
>
> {code}
> {{maven-resources-plugin}} set {{addDefaultExcludes}} attribute to {{false}}
> but does't work
>
> so, I look for the maven-archetype source code in github
> https://github.com/apache/maven-archetype
> the
> org.apache.maven.archetype.creator.FilesetArchetypeCreator.*createArchetypeFiles*(Properties,
> List, String, File, File, String) method
> line 796 show that:
> {code:title=FilesetArchetypeCreator.java|borderStyle=solid}
> private void createArchetypeFiles( Properties reverseProperties,
> List fileSets, String packageName,
>File basedir, File
> archetypeFilesDirectory, String defaultEncoding )
> throws IOException
> {
> getLogger().debug( "Creating Archetype/Module files from " + basedir
> + " to " + archetypeFilesDirectory );
> for ( FileSet fileSet : fileSets )
> {
> DirectoryScanner scanner = new DirectoryScanner();
> scanner.setBasedir( basedir );
> scanner.setIncludes( (String[]) concatenateToList(
> fileSet.getIncludes(), fileSet.getDirectory() ).toArray(
> new String[fileSet.getIncludes().size()] ) );
> scanner.setExcludes( (String[]) fileSet.getExcludes().toArray(
> new String[fileSet.getExcludes().size()] ) );
> scanner.addDefaultExcludes();
> getLogger().debug( "Using fileset " + fileSet );
> scanner.scan();
> List fileSetResources = Arrays.asList(
> scanner.getIncludedFiles() );
> getLogger().debug( "Scanned " + fileSetResources.size() + "
> resources" );
>
> .
> {code}
> here is {{scanner.addDefaultExcludes();}}
> So , the result log show that :
> {noformat}
> [DEBUG] Creating Archetype/Module files from
> C:\Users\feilong\feilong\feilong-archetypes\0726-232539 to
> C:\Users\feilong\feilong\feilong-archetypes\0726-232539\
> target\generated-sources\archetype\src\main\resources\archetype-resources
> [DEBUG] Using fileset src/main/java (Copied-Flat) [**/*.html -- ]
> [DEBUG] Scanned 1 resources
> [DEBUG] Package as Directory: Package:com.baozun.store->com\baozun\store
> [DEBUG] InputFileName:src\main\java\overview.html
> [DEBUG] OutputFileName:src\main\java\overview.html
> [DEBUG] Copied src/main/java files
> [DEBUG] Using fileset (Copied-Flat) [.gitignore -- ]
> [DEBUG] Scanned 0 resources
> [DEBUG] Package as Directory: Package:com.baozun.store->com\bao
[jira] [Closed] (ARCHETYPE-505) archetype:create-from-project,the .gitignore file not copy to archetype-resources
[
https://issues.apache.org/jira/browse/ARCHETYPE-505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Slawomir Jaranowski closed ARCHETYPE-505.
-
Resolution: Duplicate
> archetype:create-from-project,the .gitignore file not copy to
> archetype-resources
> -
>
> Key: ARCHETYPE-505
> URL: https://issues.apache.org/jira/browse/ARCHETYPE-505
> Project: Maven Archetype
> Issue Type: Bug
> Components: Archetypes
>Affects Versions: 2.4
> Environment: maven 3.3 ,maven-archetype-plugin 2.4
>Reporter: feilong
>Priority: Major
> Attachments: webapp-springmvc32.zip
>
>
> I have a very simple maven test project for {{archetype:create-from-project}}
> such as :(you can download from the Attachment)
> {noformat}
> | .gitignore
> | pom.xml
> |
> \---src
> +---main
> | \---java
> | overview.html
> |
> \---test
> {noformat}
> only {{.gitignore}} and {{pom.xml}}, and {{overview.html}} files
> and I excute the command line in the root folder:
> {code:xml}
> mvn -X archetype:create-from-project
> {code}
> I see ,in the
> {{target\generated-sources\archetype\src\main\resources\archetype-resources}}
> folder, only
> {noformat}
> | pom.xml
> |
> \---src
> \---main
> \---java
> overview.html
> {noformat}
> no {{.gitignore}} file
>
> first , I search the same issue in jira, there is #ARCHETYPE-474 , but not as
> my scene
>
> I search some solution in stackoverflow
> http://stackoverflow.com/questions/7981060/maven-archetype-plugin-doesnt-let-resources-in-archetype-resources-through#answer-37322323
> In pom.xml,I have also configed that
> {code:xml}
>
> maven-resources-plugin
> 3.0.1
>
> utf-8
> true
> false
>
>
>
> default-resources
> process-resources
>
> resources
>
>
> true
>
>
>
> default-testResources
> process-test-resources
>
> testResources
>
>
>
>
> {code}
> {{maven-resources-plugin}} set {{addDefaultExcludes}} attribute to {{false}}
> but does't work
>
> so, I look for the maven-archetype source code in github
> https://github.com/apache/maven-archetype
> the
> org.apache.maven.archetype.creator.FilesetArchetypeCreator.*createArchetypeFiles*(Properties,
> List, String, File, File, String) method
> line 796 show that:
> {code:title=FilesetArchetypeCreator.java|borderStyle=solid}
> private void createArchetypeFiles( Properties reverseProperties,
> List fileSets, String packageName,
>File basedir, File
> archetypeFilesDirectory, String defaultEncoding )
> throws IOException
> {
> getLogger().debug( "Creating Archetype/Module files from " + basedir
> + " to " + archetypeFilesDirectory );
> for ( FileSet fileSet : fileSets )
> {
> DirectoryScanner scanner = new DirectoryScanner();
> scanner.setBasedir( basedir );
> scanner.setIncludes( (String[]) concatenateToList(
> fileSet.getIncludes(), fileSet.getDirectory() ).toArray(
> new String[fileSet.getIncludes().size()] ) );
> scanner.setExcludes( (String[]) fileSet.getExcludes().toArray(
> new String[fileSet.getExcludes().size()] ) );
> scanner.addDefaultExcludes();
> getLogger().debug( "Using fileset " + fileSet );
> scanner.scan();
> List fileSetResources = Arrays.asList(
> scanner.getIncludedFiles() );
> getLogger().debug( "Scanned " + fileSetResources.size() + "
> resources" );
>
> .
> {code}
> here is {{scanner.addDefaultExcludes();}}
> So , the result log show that :
> {noformat}
> [DEBUG] Creating Archetype/Module files from
> C:\Users\feilong\feilong\feilong-archetypes\0726-232539 to
> C:\Users\feilong\feilong\feilong-archetypes\0726-232539\
> target\generated-sources\archetype\src\main\resources\archetype-resources
> [DEBUG] Using fileset src/main/java (Copied-Flat) [**/*.html -- ]
> [DEBUG] Scanned 1 resources
> [DEBUG] Package as Directory: Package:com.baozun.store->com\baozun\store
> [DEBUG] InputFileName:src\main\java\overview.html
> [DEBUG] OutputFileName:src\main\java\overview.html
> [DEBUG] Copied src/main/java files
> [DEBUG] Using fileset (Copied-Flat) [.gitignore -- ]
> [DEBUG] Scanned 0 resources
> [DEBUG] Package as Directory: Package:com.baozun.store->com\baozun\store
> [DEBUG] Copied files
> [DEBUG] Created files for webapp-springmvc3
> {noformat}
> when scan {{.gitignore}} , {{Scanned 0 resources}}
>
[jira] [Closed] (ARCHETYPE-628) error thrown when trying to create maven project from command line
[ https://issues.apache.org/jira/browse/ARCHETYPE-628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Slawomir Jaranowski closed ARCHETYPE-628. - Resolution: Information Provided > error thrown when trying to create maven project from command line > -- > > Key: ARCHETYPE-628 > URL: https://issues.apache.org/jira/browse/ARCHETYPE-628 > Project: Maven Archetype > Issue Type: Bug > Components: Plugin > Environment: I just configured version 3.8.4, I have windows 10, I > have already configured the environment variables (M2_HOME, MAVEN_HOME) >Reporter: CLAUDIA MARTINEZ >Priority: Major > Attachments: maven_error.txt > > > I just configured version 3.8.4, I have windows 10, I have already configured > the environment variables (M2_HOME, MAVEN_HOME), and I am trying to create a > maven project from the console with the following line: > mvn archetype:generate > or I have also tried with the sentence that they suggest in the maven site: > mvn archetype:generate -DgroupId=com.mycompany.app -DartifactId=my-app > -DarchetypeArtifactId=maven-archetype-quickstart -DarchetypeVersion=1.4 > -DinteractiveMode=false > But it always throws me the same error (see attached txt file), that the > plugin for the "Archetype" prefix was not found. > I already googled the error, and it seems that everything works very well for > everyone, but it has not allowed me to create the project from the command > line. > I hope you can help me. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARCHETYPE-628) error thrown when trying to create maven project from command line
[
https://issues.apache.org/jira/browse/ARCHETYPE-628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17887142#comment-17887142
]
Slawomir Jaranowski commented on ARCHETYPE-628:
---
Please try with newer Maven and JDK version.
I logs I see ...
{noformat}
aused by: javax.net.ssl.SSLException: java.lang.RuntimeException: Unexpected
error: java.security.InvalidAlgorithmParameterException: the trustAnchors
parameter must be non-empty
at sun.security.ssl.Alerts.getSSLException (Alerts.java:214)
at sun.security.ssl.SSLSocketImpl.fatal (SSLSocketImpl.java:1958)
at sun.security.ssl.SSLSocketImpl.fatal (SSLSocketImpl.java:1915)
at sun.security.ssl.SSLSocketImpl.handleException (SSLSocketImpl.java:1898)
at sun.security.ssl.SSLSocketImpl.startHandshake (SSLSocketImpl.java:1419)
at sun.security.ssl.SSLSocketImpl.startHandshake (SSLSocketImpl.java:1396)
{noformat}
The problem is not connected to archetype plugin.
> error thrown when trying to create maven project from command line
> --
>
> Key: ARCHETYPE-628
> URL: https://issues.apache.org/jira/browse/ARCHETYPE-628
> Project: Maven Archetype
> Issue Type: Bug
> Components: Plugin
> Environment: I just configured version 3.8.4, I have windows 10, I
> have already configured the environment variables (M2_HOME, MAVEN_HOME)
>Reporter: CLAUDIA MARTINEZ
>Priority: Major
> Attachments: maven_error.txt
>
>
> I just configured version 3.8.4, I have windows 10, I have already configured
> the environment variables (M2_HOME, MAVEN_HOME), and I am trying to create a
> maven project from the console with the following line:
> mvn archetype:generate
> or I have also tried with the sentence that they suggest in the maven site:
> mvn archetype:generate -DgroupId=com.mycompany.app -DartifactId=my-app
> -DarchetypeArtifactId=maven-archetype-quickstart -DarchetypeVersion=1.4
> -DinteractiveMode=false
> But it always throws me the same error (see attached txt file), that the
> plugin for the "Archetype" prefix was not found.
> I already googled the error, and it seems that everything works very well for
> everyone, but it has not allowed me to create the project from the command
> line.
> I hope you can help me.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (ARCHETYPE-630) adding a message for debug
[ https://issues.apache.org/jira/browse/ARCHETYPE-630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Slawomir Jaranowski closed ARCHETYPE-630. - Fix Version/s: 3.3.0 Resolution: Fixed > adding a message for debug > -- > > Key: ARCHETYPE-630 > URL: https://issues.apache.org/jira/browse/ARCHETYPE-630 > Project: Maven Archetype > Issue Type: Improvement >Reporter: Andra Puscas >Priority: Minor > Fix For: 3.3.0 > > > As I have some problems downloading the archetype catalog I needed to do some > debugging and I added a message, to make it more clear. > This is the PR: [https://github.com/apache/maven-archetype/pull/109] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ARCHETYPE-451) Fix documentation
[ https://issues.apache.org/jira/browse/ARCHETYPE-451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Slawomir Jaranowski updated ARCHETYPE-451: -- Fix Version/s: waiting-for-feedback > Fix documentation > - > > Key: ARCHETYPE-451 > URL: https://issues.apache.org/jira/browse/ARCHETYPE-451 > Project: Maven Archetype > Issue Type: Bug > Components: Documentation >Reporter: Bozhidar Bozhanov >Priority: Major > Fix For: waiting-for-feedback > > > The guide for creating an archetype does not work. The archetype.xml does not > seem to be respected. > Using :create-from-project generates a completely different file > (archetype-metadata.xml), which is not present in the guide: > http://maven.apache.org/guides/mini/guide-creating-archetypes.html -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARCHETYPE-630) adding a message for debug
[ https://issues.apache.org/jira/browse/ARCHETYPE-630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17887143#comment-17887143 ] Slawomir Jaranowski commented on ARCHETYPE-630: --- PR merged: https://github.com/apache/maven-archetype/commit/59c5818b7e198e5ff3ac6452f4f81fcb3b48a140 > adding a message for debug > -- > > Key: ARCHETYPE-630 > URL: https://issues.apache.org/jira/browse/ARCHETYPE-630 > Project: Maven Archetype > Issue Type: Improvement >Reporter: Andra Puscas >Priority: Minor > > As I have some problems downloading the archetype catalog I needed to do some > debugging and I added a message, to make it more clear. > This is the PR: [https://github.com/apache/maven-archetype/pull/109] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARCHETYPE-451) Fix documentation
[ https://issues.apache.org/jira/browse/ARCHETYPE-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17887144#comment-17887144 ] Slawomir Jaranowski commented on ARCHETYPE-451: --- Looks like documentation was fixed ... > Fix documentation > - > > Key: ARCHETYPE-451 > URL: https://issues.apache.org/jira/browse/ARCHETYPE-451 > Project: Maven Archetype > Issue Type: Bug > Components: Documentation >Reporter: Bozhidar Bozhanov >Priority: Major > > The guide for creating an archetype does not work. The archetype.xml does not > seem to be respected. > Using :create-from-project generates a completely different file > (archetype-metadata.xml), which is not present in the guide: > http://maven.apache.org/guides/mini/guide-creating-archetypes.html -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (ARCHETYPE-679) groovy.text.SimpleTemplateEngine Not Found
[
https://issues.apache.org/jira/browse/ARCHETYPE-679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Slawomir Jaranowski reassigned ARCHETYPE-679:
-
Assignee: Slawomir Jaranowski
> groovy.text.SimpleTemplateEngine Not Found
> --
>
> Key: ARCHETYPE-679
> URL: https://issues.apache.org/jira/browse/ARCHETYPE-679
> Project: Maven Archetype
> Issue Type: Bug
> Components: Archetypes
>Affects Versions: 3.3.0
>Reporter: Reza Rahman
>Assignee: Slawomir Jaranowski
>Priority: Major
> Fix For: 3.3.1
>
>
> I am posting this issue on behalf of the official Jakarta EE Starter project
> at the Eclipse Foundation:
> [https://start.jakarta.ee|https://start.jakarta.ee/]. We make use of Maven
> Archetypes in the Starter under the hood and also as an API:
> [https://github.com/eclipse-ee4j/starter/tree/master/archetype.]
> We are pretty dependent on Groovy and use groovy.text.SimpleTemplateEngine
> for some critical functionality:
> [https://github.com/eclipse-ee4j/starter/blob/ca9b5028b7fe3b47ecf4b5e5c22e89bc941e99a0/archetype/src/main/resources/META-INF/archetype-post-generate.groovy#L144].
>
> A few days ago we noticed that the Archetype is suddenly broken with the
> following error:
> {{[ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-archetype-plugin:3.3.0:generate (default-cli)
> on project standalone-pom: startup failed:}}
> {{[ERROR] Script1.groovy: 144: unable to resolve class
> groovy.text.SimpleTemplateEngine}}
> {{[ERROR] @ line 144, column 18.}}
> {{[ERROR] def engine = new groovy.text.SimpleTemplateEngine()}}
> {{[ERROR] ^}}
> {{[ERROR]}}
> {{[ERROR] 1 error}}
> This seems to coincide with the 3.3.0 release of maven-archetype-plugin. Any
> idea what is going on and how to fix this?
> Please LMK if you need anything from us?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (ARCHETYPE-685) Fix namespace in modello models
[ https://issues.apache.org/jira/browse/ARCHETYPE-685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Slawomir Jaranowski updated ARCHETYPE-685: -- Affects Version/s: 3.3.0 > Fix namespace in modello models > > > Key: ARCHETYPE-685 > URL: https://issues.apache.org/jira/browse/ARCHETYPE-685 > Project: Maven Archetype > Issue Type: Bug >Affects Versions: 3.3.0 >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: 3.3.1 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MNG-5761) Dependency management is not transitive.
[ https://issues.apache.org/jira/browse/MNG-5761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Didier Loiseau updated MNG-5761: Attachment: depending-pom2.xml > Dependency management is not transitive. > > > Key: MNG-5761 > URL: https://issues.apache.org/jira/browse/MNG-5761 > Project: Maven > Issue Type: Bug > Components: Dependencies >Affects Versions: 3.2.5 >Reporter: Jeff Schnitzer >Priority: Critical > Fix For: 4.0.x-candidate > > Attachments: MNG-5761.zip, depending-pom2.xml > > > A detailed description of the issue is here: > http://stackoverflow.com/questions/28312975/maven-dependencymanagement-version-ignored-in-transitive-dependencies > The short of it is that maven appears to be using the wrong > version in a transitive dependency. There are two > relevant sections in the build, one pulled in by guice > and one pulled in by gwizard-parent. These are the dependency paths from the > top: > gwizard-example -> gwizard-config -> gwizard-parent > gwizard-example -> gwizard-config -> guice -> guice-parent > gwizard-parent's dependencyManagement specifies guava 18 > guice-parent's dependencyManagement specifies guava 16 > Guava 16 is winning. This seems highly undesirable, and in fact it breaks our > build. I would expect that in a version # fight, "closest to the top" should > win. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARCHETYPE-682) [REGRESSION] With the latest maven-archetype-plugin version 3.3.0, facing the error, "Error merging velocity templates: Encountered "" at " whi
[
https://issues.apache.org/jira/browse/ARCHETYPE-682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17887082#comment-17887082
]
Slawomir Jaranowski commented on ARCHETYPE-682:
---
There is a special syntax in velocity, like:
{code}
#@vmname( $arg1 $arg2 ) here is the body#end
{code}
so you can not use
{code}
#@echo off
{code}
this one will be ok:
{code}
# @echo off
{code}
The empty line at the end of file is not matter in such case
> [REGRESSION] With the latest maven-archetype-plugin version 3.3.0, facing the
> error, "Error merging velocity templates: Encountered "" at
> " while creating a new maven project using archetype
>
>
> Key: ARCHETYPE-682
> URL: https://issues.apache.org/jira/browse/ARCHETYPE-682
> Project: Maven Archetype
> Issue Type: Bug
> Components: Archetypes, Plugin
>Affects Versions: 3.3.0
>Reporter: Sasi Kumar
>Priority: Major
> Labels: EOF, archetype
> Attachments: sample-archetype.zip
>
>
> [https://mvnrepository.com/artifact/org.apache.maven.plugins/maven-archetype-plugin/3.3.0]
>
> Facing the following issue with the latest version of
> maven-archetype-plugin/3.3.0
> *Error merging velocity templates: Encountered "" at *
> *[exec] [ERROR] Was expecting one of:*
> *[exec] [ERROR] "\u001c" ...*
> *[exec] [ERROR] "\u001c" ...*
> *[exec] [ERROR] "||" ...*
> *[exec] [ERROR] "|" ...*
> *[exec] [ERROR] "(" ...*
> *[exec] [ERROR] ")" ...*
> *[exec] [ERROR] ...*
> *[exec] [ERROR] "]]#" ...*
> *[exec] [ERROR] ...*
> *[exec] [ERROR] ...*
> *[exec] [ERROR] ...*
> *[exec] [ERROR] ...*
> *[exec] [ERROR] ...*
> *[exec] [ERROR] ...*
> *[exec] [ERROR] ...*
> *[exec] [ERROR] "
> {" ...* *[exec] [ERROR] "}
> " ...*
> *[exec] [ERROR] "" ...*
> *[exec] [ERROR] "*
> *" ...*
> *[exec] [ERROR] ...*
> *[exec] [ERROR] ...*
> *[exec] [ERROR] ...*
> *[exec] [ERROR] "{" ...*
> *[exec] [ERROR] "\u001c" ...*
> *[exec] [ERROR] -> [Help 1]*
>
> This happens while parsing a shell script file that ends with {*}"cd../.."
> without Line Feed{*}. This is working fine till maven-archetype-plugin/3.2.1
> but starts failing from last week after the new version of
> maven-archetype-plugin/3.3.0 released on 26th Sep, 2024. Help us resolve this
> as soon. Thanks.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ARCHETYPE-682) [REGRESSION] With the latest maven-archetype-plugin version 3.3.0, facing the error, "Error merging velocity templates: Encountered "" at " whi
[
https://issues.apache.org/jira/browse/ARCHETYPE-682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17887083#comment-17887083
]
Slawomir Jaranowski commented on ARCHETYPE-682:
---
We upgrade velocity from 1.7 to 2.3
> [REGRESSION] With the latest maven-archetype-plugin version 3.3.0, facing the
> error, "Error merging velocity templates: Encountered "" at
> " while creating a new maven project using archetype
>
>
> Key: ARCHETYPE-682
> URL: https://issues.apache.org/jira/browse/ARCHETYPE-682
> Project: Maven Archetype
> Issue Type: Bug
> Components: Archetypes, Plugin
>Affects Versions: 3.3.0
>Reporter: Sasi Kumar
>Priority: Major
> Labels: EOF, archetype
> Attachments: sample-archetype.zip
>
>
> [https://mvnrepository.com/artifact/org.apache.maven.plugins/maven-archetype-plugin/3.3.0]
>
> Facing the following issue with the latest version of
> maven-archetype-plugin/3.3.0
> *Error merging velocity templates: Encountered "" at *
> *[exec] [ERROR] Was expecting one of:*
> *[exec] [ERROR] "\u001c" ...*
> *[exec] [ERROR] "\u001c" ...*
> *[exec] [ERROR] "||" ...*
> *[exec] [ERROR] "|" ...*
> *[exec] [ERROR] "(" ...*
> *[exec] [ERROR] ")" ...*
> *[exec] [ERROR] ...*
> *[exec] [ERROR] "]]#" ...*
> *[exec] [ERROR] ...*
> *[exec] [ERROR] ...*
> *[exec] [ERROR] ...*
> *[exec] [ERROR] ...*
> *[exec] [ERROR] ...*
> *[exec] [ERROR] ...*
> *[exec] [ERROR] ...*
> *[exec] [ERROR] "
> {" ...* *[exec] [ERROR] "}
> " ...*
> *[exec] [ERROR] "" ...*
> *[exec] [ERROR] "*
> *" ...*
> *[exec] [ERROR] ...*
> *[exec] [ERROR] ...*
> *[exec] [ERROR] ...*
> *[exec] [ERROR] "{" ...*
> *[exec] [ERROR] "\u001c" ...*
> *[exec] [ERROR] -> [Help 1]*
>
> This happens while parsing a shell script file that ends with {*}"cd../.."
> without Line Feed{*}. This is working fine till maven-archetype-plugin/3.2.1
> but starts failing from last week after the new version of
> maven-archetype-plugin/3.3.0 released on 26th Sep, 2024. Help us resolve this
> as soon. Thanks.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-5761) Dependency management is not transitive.
[
https://issues.apache.org/jira/browse/MNG-5761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17887084#comment-17887084
]
Didier Loiseau commented on MNG-5761:
-
[~cstamas], I just checked with
{code:bash}
$ mvn -v
Apache Maven 4.0.0-beta-4 (697c543b4e3bbec1b99e9d4d1ee8e0302e748f09)
Maven home: /home/didier/.sdkman/candidates/maven/4.0.0-beta-4
Java version: 21.0.2, vendor: Oracle Corporation, runtime:
/home/didier/.sdkman/candidates/java/21.0.2-open
Default locale: en_GB, platform encoding: UTF-8
OS name: "linux", version: "6.8.0-45-generic", arch: "amd64", family: "unix"
{code}
and it does not fix the issue… for first level dependencies.
So basically, it does not fix it for the attached [^MNG-5761.zip] provided by
[~slanglois], you still get the same output as in his comment:
{code:bash}
$ mvn dependency:tree -f depending-pom.xml
…
[INFO] --- dependency:3.8.0:tree (default-cli) @ depending ---
[INFO] MNG-5761:depending:pom:1.0-SNAPSHOT
[INFO] \- MNG-5761:dependent:pom:1.0-SNAPSHOT:compile
[INFO]\- commons-beanutils:commons-beanutils:jar:1.9.2:compile
[INFO] +- commons-logging:commons-logging:jar:1.1.1:compile
[INFO] \- commons-collections:commons-collections:jar:3.2.1:compile
{code}
However, if you add another level, as with [^depending-pom2.xml], you get the
expected output ({{{}commons-collections:jar:3.2.2{}}}):
{code:bash}
$ mvn install -f depending-pom.xml
$ mvn dependency:tree -f depending-pom2.xml
…
[INFO] --- dependency:3.8.0:tree (default-cli) @ depending2 ---
[INFO] MNG-5761:depending2:pom:1.0-SNAPSHOT
[INFO] \- MNG-5761:depending:pom:1.0-SNAPSHOT:compile
[INFO] \- MNG-5761:dependent:pom:1.0-SNAPSHOT:compile
[INFO] \- commons-beanutils:commons-beanutils:jar:1.9.2:compile
[INFO] +- commons-logging:commons-logging:jar:1.1.1:compile
[INFO] \-
commons-collections:commons-collections:jar:3.2.2:compile{code}
The issue seems to come from [these 3
lines|https://github.com/apache/maven-resolver/blob/32844e4eb8d444838953f1d49be2ecb71db15b78/maven-resolver-util/src/main/java/org/eclipse/aether/util/graph/manager/ClassicDependencyManager.java#L91-L93]
in {{{}ClassicDependencyManager{}}}:
{code:java}
@Override
public DependencyManager deriveChildManager(DependencyCollectionContext
context) {
// MNG-4720: Maven2 backward compatibility
// Removing this IF makes one IT fail here (read comment above):
//
https://github.com/apache/maven-integration-testing/blob/b4e8fd52b99a058336f9c7c5ec44fdbc1427759c/core-it-suite/src/test/java/org/apache/maven/it/MavenITmng4720DependencyManagementExclusionMergeTest.java#L67
if (depth == 1) {
return newInstance(managedVersions, managedScopes,
managedOptionals, managedLocalPaths, managedExclusions);
}
return super.deriveChildManager(context);
}
{code}
Basically, it ignores the context for the first level of dependencies. This
seems to be reminiscent from [the implementation Resolver
1.9|https://github.com/apache/maven-resolver/blob/maven-resolver-1.9.22/maven-resolver-util/src/main/java/org/eclipse/aether/util/graph/manager/ClassicDependencyManager.java#L85-L92],
where it was the case for all layers above 1.
I guess this logic shouldn’t apply if {{{}deriveUntil > 2{}}}? Otherwise it’s
quite inconsistent.
This would make the behaviour almost identical to the
{{DefaultDependencyManager}} though, so I’m wondering why the latter isn’t used
instead (and its name makes that even more confusing). I suppose it affects the
management of exclusions?
> Dependency management is not transitive.
>
>
> Key: MNG-5761
> URL: https://issues.apache.org/jira/browse/MNG-5761
> Project: Maven
> Issue Type: Bug
> Components: Dependencies
>Affects Versions: 3.2.5
>Reporter: Jeff Schnitzer
>Priority: Critical
> Fix For: 4.0.x-candidate
>
> Attachments: MNG-5761.zip, depending-pom2.xml
>
>
> A detailed description of the issue is here:
> http://stackoverflow.com/questions/28312975/maven-dependencymanagement-version-ignored-in-transitive-dependencies
> The short of it is that maven appears to be using the wrong
> version in a transitive dependency. There are two
> relevant sections in the build, one pulled in by guice
> and one pulled in by gwizard-parent. These are the dependency paths from the
> top:
> gwizard-example -> gwizard-config -> gwizard-parent
> gwizard-example -> gwizard-config -> guice -> guice-parent
> gwizard-parent's dependencyManagement specifies guava 18
> guice-parent's dependencyManagement specifies guava 16
> Guava 16 is winning. This seems highly undesirable, and in fact it breaks our
> build. I would expect that in a version # fight, "closest to the top" should
> win.
--
This message was sent by Atlas
[jira] [Comment Edited] (MNG-5761) Dependency management is not transitive.
[
https://issues.apache.org/jira/browse/MNG-5761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17887084#comment-17887084
]
Didier Loiseau edited comment on MNG-5761 at 10/5/24 10:30 AM:
---
[~cstamas], I just checked with
{code:bash}
$ mvn -v
Apache Maven 4.0.0-beta-4 (697c543b4e3bbec1b99e9d4d1ee8e0302e748f09)
Maven home: /home/didier/.sdkman/candidates/maven/4.0.0-beta-4
Java version: 21.0.2, vendor: Oracle Corporation, runtime:
/home/didier/.sdkman/candidates/java/21.0.2-open
Default locale: en_GB, platform encoding: UTF-8
OS name: "linux", version: "6.8.0-45-generic", arch: "amd64", family: "unix"
{code}
and it does not fix the issue… for first level dependencies.
So basically, it does not fix it for the attached [^MNG-5761.zip] provided by
[~slanglois], you still get the same output as in his comment:
{code:bash}
$ mvn dependency:tree -f depending-pom.xml
…
[INFO] --- dependency:3.8.0:tree (default-cli) @ depending ---
[INFO] MNG-5761:depending:pom:1.0-SNAPSHOT
[INFO] \- MNG-5761:dependent:pom:1.0-SNAPSHOT:compile
[INFO]\- commons-beanutils:commons-beanutils:jar:1.9.2:compile
[INFO] +- commons-logging:commons-logging:jar:1.1.1:compile
[INFO] \- commons-collections:commons-collections:jar:3.2.1:compile
{code}
However, if you add another level, as with [^depending-pom2.xml], you get the
expected output ({{{}commons-collections:jar:3.2.2{}}}):
{code:bash}
$ mvn install -f depending-pom.xml
$ mvn dependency:tree -f depending-pom2.xml
…
[INFO] --- dependency:3.8.0:tree (default-cli) @ depending2 ---
[INFO] MNG-5761:depending2:pom:1.0-SNAPSHOT
[INFO] \- MNG-5761:depending:pom:1.0-SNAPSHOT:compile
[INFO] \- MNG-5761:dependent:pom:1.0-SNAPSHOT:compile
[INFO] \- commons-beanutils:commons-beanutils:jar:1.9.2:compile
[INFO] +- commons-logging:commons-logging:jar:1.1.1:compile
[INFO] \-
commons-collections:commons-collections:jar:3.2.2:compile{code}
The issue seems to come from [these 3
lines|https://github.com/apache/maven-resolver/blob/32844e4eb8d444838953f1d49be2ecb71db15b78/maven-resolver-util/src/main/java/org/eclipse/aether/util/graph/manager/ClassicDependencyManager.java#L91-L93]
in {{{}ClassicDependencyManager{}}}:
{code:java}
@Override
public DependencyManager deriveChildManager(DependencyCollectionContext
context) {
// MNG-4720: Maven2 backward compatibility
// Removing this IF makes one IT fail here (read comment above):
//
https://github.com/apache/maven-integration-testing/blob/b4e8fd52b99a058336f9c7c5ec44fdbc1427759c/core-it-suite/src/test/java/org/apache/maven/it/MavenITmng4720DependencyManagementExclusionMergeTest.java#L67
if (depth == 1) {
return newInstance(managedVersions, managedScopes,
managedOptionals, managedLocalPaths, managedExclusions);
}
return super.deriveChildManager(context);
}
{code}
Basically, it ignores the context for the first level of dependencies. This
seems to be reminiscent from [the implementation Resolver
1.9|https://github.com/apache/maven-resolver/blob/maven-resolver-1.9.22/maven-resolver-util/src/main/java/org/eclipse/aether/util/graph/manager/ClassicDependencyManager.java#L85-L92],
where it was the case for all layers above 1.
I guess this logic shouldn’t apply if {{{}deriveUntil > 2{}}}? Otherwise it’s
quite inconsistent.
This would make the behaviour almost identical to the
{{DefaultDependencyManager}} though, so I’m wondering why the latter isn’t used
instead (and its name makes that even more confusing). I suppose it affects the
management of exclusions?
Edit: actually that behavior would be the one of
{{TransitiveDependencyManager}} (still not sure about the {{deriveUntil}}
effects)
was (Author: didier loiseau):
[~cstamas], I just checked with
{code:bash}
$ mvn -v
Apache Maven 4.0.0-beta-4 (697c543b4e3bbec1b99e9d4d1ee8e0302e748f09)
Maven home: /home/didier/.sdkman/candidates/maven/4.0.0-beta-4
Java version: 21.0.2, vendor: Oracle Corporation, runtime:
/home/didier/.sdkman/candidates/java/21.0.2-open
Default locale: en_GB, platform encoding: UTF-8
OS name: "linux", version: "6.8.0-45-generic", arch: "amd64", family: "unix"
{code}
and it does not fix the issue… for first level dependencies.
So basically, it does not fix it for the attached [^MNG-5761.zip] provided by
[~slanglois], you still get the same output as in his comment:
{code:bash}
$ mvn dependency:tree -f depending-pom.xml
…
[INFO] --- dependency:3.8.0:tree (default-cli) @ depending ---
[INFO] MNG-5761:depending:pom:1.0-SNAPSHOT
[INFO] \- MNG-5761:dependent:pom:1.0-SNAPSHOT:compile
[INFO]\- commons-beanutils:commons-beanutils:jar:1.9.2:compile
[INFO] +- commons-logging:commons-logging:jar:1.1.1:compile
[INFO] \- commons-collections:commons-collections:jar:3.2.1:compile
{code}
However, if you add another level, as with [^depending-pom2.xml],
[jira] [Commented] (ARCHETYPE-684) Not providing a directory element in the fileset results in a null directory instead
[
https://issues.apache.org/jira/browse/ARCHETYPE-684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17887086#comment-17887086
]
Slawomir Jaranowski commented on ARCHETYPE-684:
---
https://github.com/codehaus-plexus/modello/issues/472
> Not providing a directory element in the fileset results in a null directory
> instead
>
>
> Key: ARCHETYPE-684
> URL: https://issues.apache.org/jira/browse/ARCHETYPE-684
> Project: Maven Archetype
> Issue Type: Bug
> Components: Generator
>Affects Versions: 3.2.1, 3.3.0
>Reporter: Giovanni van der Schelde
>Priority: Major
> Attachments: reproducer.zip
>
>
> When you have a directory structure like:
> {code:java}
> src/
> main/resources/
>src/
>example.yml{code}
> And a fileSet in the archetype-descriptor like:
> {code:java}
>
>
>
> *.yml
>
> {code}
> When you generate the archetype you won't get the .yml files, but instead you
> get an empty directory with the name `null`.
> When you explicitly provide the element, the `null` directory
> disappears and the .yml file is copied.
> I think it would make sense to either;
> a) Log an error or warning that the xml is incomplete
> b) When no directory is provided, use a default (of the root directory)
> instead
> Where option B makes to most sense to me.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ARCHETYPE-684) Not providing a directory element in the fileset results in a null directory instead
[
https://issues.apache.org/jira/browse/ARCHETYPE-684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17887085#comment-17887085
]
Slawomir Jaranowski commented on ARCHETYPE-684:
---
We have defined in modello:
{code}
directory
1.0.0+
String
true
{code}
so should be required
> Not providing a directory element in the fileset results in a null directory
> instead
>
>
> Key: ARCHETYPE-684
> URL: https://issues.apache.org/jira/browse/ARCHETYPE-684
> Project: Maven Archetype
> Issue Type: Bug
> Components: Generator
>Affects Versions: 3.2.1, 3.3.0
>Reporter: Giovanni van der Schelde
>Priority: Major
> Attachments: reproducer.zip
>
>
> When you have a directory structure like:
> {code:java}
> src/
> main/resources/
>src/
>example.yml{code}
> And a fileSet in the archetype-descriptor like:
> {code:java}
>
>
>
> *.yml
>
> {code}
> When you generate the archetype you won't get the .yml files, but instead you
> get an empty directory with the name `null`.
> When you explicitly provide the element, the `null` directory
> disappears and the .yml file is copied.
> I think it would make sense to either;
> a) Log an error or warning that the xml is incomplete
> b) When no directory is provided, use a default (of the root directory)
> instead
> Where option B makes to most sense to me.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (MPMD-406) java.lang.NoSuchMethodError: 'void org.apache.maven.doxia.sink.Sink.verbatim()' updating from 3.24.0 to 3.25.0
[
https://issues.apache.org/jira/browse/MPMD-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17887105#comment-17887105
]
Gary D. Gregory edited comment on MPMD-406 at 10/5/24 1:45 PM:
---
I'm trying... something simple at first.
In commons-parent at
https://github.com/apache/commons-parent/blob/801b06a43698422b444fd7241e2f1c0f7fd89edb/src/site/site.xml#L54C1-L56C27
If I say instead:
{code:xml}
org.apache.maven.skins
maven-default-skin
1.3
{code}
and run:
{code}
mvn clean site
{code}
It blows up with:
{code}
[INFO] <<< surefire-report:3.5.0:report (default-site) < [surefire]test @
commons-parent <<<
[INFO]
[INFO] '[surefire]test' forked phase execution for
maven-surefire-report-plugin:report report preparation done
[INFO] Detected 3 reports for maven-surefire-report-plugin:3.5.0:
failsafe-report-only, report, report-only
[INFO] Configuring report plugin apache-rat-plugin:0.16.1
[INFO] Detected 1 report for apache-rat-plugin:0.16.1: rat
[INFO] Skipping org.apache.maven.plugins:maven-javadoc-plugin:3.10.1:javadoc
report
[INFO] Skipping
org.apache.maven.plugins:maven-project-info-reports-plugin:3.6.2:modules report
[INFO] Skipping
org.apache.maven.plugins:maven-project-info-reports-plugin:3.6.2:team report
[INFO] Skipping
org.apache.maven.plugins:maven-project-info-reports-plugin:3.6.2:dependencies
report
[WARNING] Site model of 'org.apache.commons:commons-parent:pom:77-SNAPSHOT' for
default locale is still using the old pre-version 2.0.0 model. You MUST migrate
to the new model as soon as possible otherwise your build will break in the
future!
[INFO] Relativizing site links with respect to localized project URL:
https://commons.apache.org/proper/commons-parent/
[INFO] Rendering content with org.apache.maven.skins:maven-default-skin:jar:1.3
skin
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 6.977 s
[INFO] Finished at: 2024-10-05T09:27:07-04:00
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.20.0:site (default-site) on
project commons-parent: Failed to create context for skin: Skin does not
contain template at META-INF/maven/site.vm -> [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
{code}
Full console log:
https://gist.github.com/garydgregory/a0d6950afd70720c9a7ecc206d682c4f
My end goal is to use current plugins... but it's not easy, I can't find
documentation on how to upgrade from the maven site plugin 3.12.1 to 3.20.0
The page https://maven.apache.org/plugins/maven-site-plugin/migrate.html is not
up to date.
Any guidance would be appreciated.
TY.
was (Author: garydgregory):
I'm trying... something simple at first.
In commons-parent at
https://github.com/apache/commons-parent/blob/801b06a43698422b444fd7241e2f1c0f7fd89edb/src/site/site.xml#L54C1-L56C27
If I say instead:
{code:xml}
org.apache.maven.skins
maven-default-skin
1.3
{code}
and run:
{code}
mvn clean site
{code}
It blows up with:
{code}
[INFO] <<< surefire-report:3.5.0:report (default-site) < [surefire]test @
commons-parent <<<
[INFO]
[INFO] '[surefire]test' forked phase execution for
maven-surefire-report-plugin:report report preparation done
[INFO] Detected 3 reports for maven-surefire-report-plugin:3.5.0:
failsafe-report-only, report, report-only
[INFO] Configuring report plugin apache-rat-plugin:0.16.1
[INFO] Detected 1 report for apache-rat-plugin:0.16.1: rat
[INFO] Skipping org.apache.maven.plugins:maven-javadoc-plugin:3.10.1:javadoc
report
[INFO] Skipping
org.apache.maven.plugins:maven-project-info-reports-plugin:3.6.2:modules report
[INFO] Skipping
org.apache.maven.plugins:maven-project-info-reports-plugin:3.6.2:team report
[INFO] Skipping
org.apache.maven.plugins:maven-project-info-reports-plugin:3.6.2:dependencies
report
[WARNING] Site model of 'org.apache.commons:commons-parent:pom:77-SNAPSHOT' for
default locale is still using the old pre-version 2.0.0 model. You MUST migrate
to the new model as soon as possible otherwise your build will break in the
future!
[INFO] Relativizing site links with respect to localized project URL:
https://commons.apache.org/proper/commons-parent/
[INFO] Rendering content with org.apache.maven.skins:maven-default-skin:jar:1.3
skin
[INFO]
[INFO] BUILD
[jira] [Commented] (MPMD-406) java.lang.NoSuchMethodError: 'void org.apache.maven.doxia.sink.Sink.verbatim()' updating from 3.24.0 to 3.25.0
[
https://issues.apache.org/jira/browse/MPMD-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17887105#comment-17887105
]
Gary D. Gregory commented on MPMD-406:
--
I'm trying... something simple at first.
In commons-parent at
https://github.com/apache/commons-parent/blob/801b06a43698422b444fd7241e2f1c0f7fd89edb/src/site/site.xml#L54C1-L56C27
If I say instead:
{code:xml}
org.apache.maven.skins
maven-default-skin
1.3
{code}
and run:
{code}
mvn clean site
{code}
It blows up with:
{code}
[INFO] <<< surefire-report:3.5.0:report (default-site) < [surefire]test @
commons-parent <<<
[INFO]
[INFO] '[surefire]test' forked phase execution for
maven-surefire-report-plugin:report report preparation done
[INFO] Detected 3 reports for maven-surefire-report-plugin:3.5.0:
failsafe-report-only, report, report-only
[INFO] Configuring report plugin apache-rat-plugin:0.16.1
[INFO] Detected 1 report for apache-rat-plugin:0.16.1: rat
[INFO] Skipping org.apache.maven.plugins:maven-javadoc-plugin:3.10.1:javadoc
report
[INFO] Skipping
org.apache.maven.plugins:maven-project-info-reports-plugin:3.6.2:modules report
[INFO] Skipping
org.apache.maven.plugins:maven-project-info-reports-plugin:3.6.2:team report
[INFO] Skipping
org.apache.maven.plugins:maven-project-info-reports-plugin:3.6.2:dependencies
report
[WARNING] Site model of 'org.apache.commons:commons-parent:pom:77-SNAPSHOT' for
default locale is still using the old pre-version 2.0.0 model. You MUST migrate
to the new model as soon as possible otherwise your build will break in the
future!
[INFO] Relativizing site links with respect to localized project URL:
https://commons.apache.org/proper/commons-parent/
[INFO] Rendering content with org.apache.maven.skins:maven-default-skin:jar:1.3
skin
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 6.977 s
[INFO] Finished at: 2024-10-05T09:27:07-04:00
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.20.0:site (default-site) on
project commons-parent: Failed to create context for skin: Skin does not
contain template at META-INF/maven/site.vm -> [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
{code}
Full console log:
https://gist.github.com/garydgregory/a0d6950afd70720c9a7ecc206d682c4f
My end goal is to use current plugins... but it's not easy, I can't find
documentation on how to upgrade from the maven site plugin 3.12.1 to 3.20.0
The page https://maven.apache.org/plugins/maven-site-plugin/migrate.html is not
up to date.
Any guidance would be appreciated.
> java.lang.NoSuchMethodError: 'void
> org.apache.maven.doxia.sink.Sink.verbatim()' updating from 3.24.0 to 3.25.0
> --
>
> Key: MPMD-406
> URL: https://issues.apache.org/jira/browse/MPMD-406
> Project: Maven PMD Plugin
> Issue Type: Bug
>Affects Versions: 3.25.0
> Environment: openjdk version "17.0.12" 2024-07-16
> OpenJDK Runtime Environment Homebrew (build 17.0.12+0)
> OpenJDK 64-Bit Server VM Homebrew (build 17.0.12+0, mixed mode, sharing)
> Apache Maven 3.9.9 (8e8579a9e76f7d015ee5ec7bfcdc97d260186937)
> Maven home: /usr/local/Cellar/maven/3.9.9/libexec
> Java version: 17.0.12, vendor: Homebrew, runtime:
> /usr/local/Cellar/openjdk@17/17.0.12/libexec/openjdk.jdk/Contents/Home
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "14.6.1", arch: "x86_64", family: "mac"
> Darwin 23.6.0 Darwin Kernel Version 23.6.0: Mon Jul 29 21:13:00 PDT
> 2024; root:xnu-10063.141.2~1/RELEASE_X86_64 x86_64
>Reporter: Gary D. Gregory
>Assignee: Michael Osipov
>Priority: Major
>
> java.lang.NoSuchMethodError: 'void
> org.apache.maven.doxia.sink.Sink.verbatim()' updating from 3.24.0 to 3.25.0
> {noformat}
> java.lang.NoSuchMethodError: 'void
> org.apache.maven.doxia.sink.Sink.verbatim()'
> at org.apache.maven.reporting.AbstractMavenReportRenderer.verbatimText
> (AbstractMavenReportRenderer.java:363)
> at org.apache.maven.plugins.pmd.CpdReportRenderer.renderDuplications
> (CpdReportRenderer.java:171)
> at org.apache.maven.plugins.pmd.CpdReportRenderer.renderBody
> (CpdReportRenderer.java:96)
> at org.apache.maven.reporting.Abst
[jira] [Commented] (MPMD-406) java.lang.NoSuchMethodError: 'void org.apache.maven.doxia.sink.Sink.verbatim()' updating from 3.24.0 to 3.25.0
[
https://issues.apache.org/jira/browse/MPMD-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17887112#comment-17887112
]
Michael Osipov commented on MPMD-406:
-
I must also admit that I complete forgot the migrate page. PRs highly
appreciated. My time is very limited these days.
> java.lang.NoSuchMethodError: 'void
> org.apache.maven.doxia.sink.Sink.verbatim()' updating from 3.24.0 to 3.25.0
> --
>
> Key: MPMD-406
> URL: https://issues.apache.org/jira/browse/MPMD-406
> Project: Maven PMD Plugin
> Issue Type: Bug
>Affects Versions: 3.25.0
> Environment: openjdk version "17.0.12" 2024-07-16
> OpenJDK Runtime Environment Homebrew (build 17.0.12+0)
> OpenJDK 64-Bit Server VM Homebrew (build 17.0.12+0, mixed mode, sharing)
> Apache Maven 3.9.9 (8e8579a9e76f7d015ee5ec7bfcdc97d260186937)
> Maven home: /usr/local/Cellar/maven/3.9.9/libexec
> Java version: 17.0.12, vendor: Homebrew, runtime:
> /usr/local/Cellar/openjdk@17/17.0.12/libexec/openjdk.jdk/Contents/Home
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "14.6.1", arch: "x86_64", family: "mac"
> Darwin 23.6.0 Darwin Kernel Version 23.6.0: Mon Jul 29 21:13:00 PDT
> 2024; root:xnu-10063.141.2~1/RELEASE_X86_64 x86_64
>Reporter: Gary D. Gregory
>Assignee: Michael Osipov
>Priority: Major
>
> java.lang.NoSuchMethodError: 'void
> org.apache.maven.doxia.sink.Sink.verbatim()' updating from 3.24.0 to 3.25.0
> {noformat}
> java.lang.NoSuchMethodError: 'void
> org.apache.maven.doxia.sink.Sink.verbatim()'
> at org.apache.maven.reporting.AbstractMavenReportRenderer.verbatimText
> (AbstractMavenReportRenderer.java:363)
> at org.apache.maven.plugins.pmd.CpdReportRenderer.renderDuplications
> (CpdReportRenderer.java:171)
> at org.apache.maven.plugins.pmd.CpdReportRenderer.renderBody
> (CpdReportRenderer.java:96)
> at org.apache.maven.reporting.AbstractMavenReportRenderer.render
> (AbstractMavenReportRenderer.java:93)
> at org.apache.maven.plugins.pmd.CpdReport.executeReport
> (CpdReport.java:140)
> at org.apache.maven.reporting.AbstractMavenReport.generate
> (AbstractMavenReport.java:354)
> at
> org.apache.maven.plugins.site.render.ReportDocumentRenderer.renderDocument
> (ReportDocumentRenderer.java:226)
> at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render
> (DefaultSiteRenderer.java:348)
> at org.apache.maven.plugins.site.render.SiteMojo.renderLocale
> (SiteMojo.java:194)
> at org.apache.maven.plugins.site.render.SiteMojo.execute
> (SiteMojo.java:143)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:126)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:328)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:316)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:174)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
> (MojoExecutor.java:75)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
> (MojoExecutor.java:162)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:159)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:105)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:73)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:53)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:118)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:261)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:173)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:101)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:906)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:283)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:206)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:77)
> at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:569)
> at org.codehaus.plexus.classworlds.laun
[jira] [Updated] (MPMD-406) java.lang.NoSuchMethodError: 'void org.apache.maven.doxia.sink.Sink.verbatim()' updating from 3.24.0 to 3.25.0
[
https://issues.apache.org/jira/browse/MPMD-406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MPMD-406:
Attachment: screenshot-1.png
> java.lang.NoSuchMethodError: 'void
> org.apache.maven.doxia.sink.Sink.verbatim()' updating from 3.24.0 to 3.25.0
> --
>
> Key: MPMD-406
> URL: https://issues.apache.org/jira/browse/MPMD-406
> Project: Maven PMD Plugin
> Issue Type: Bug
>Affects Versions: 3.25.0
> Environment: openjdk version "17.0.12" 2024-07-16
> OpenJDK Runtime Environment Homebrew (build 17.0.12+0)
> OpenJDK 64-Bit Server VM Homebrew (build 17.0.12+0, mixed mode, sharing)
> Apache Maven 3.9.9 (8e8579a9e76f7d015ee5ec7bfcdc97d260186937)
> Maven home: /usr/local/Cellar/maven/3.9.9/libexec
> Java version: 17.0.12, vendor: Homebrew, runtime:
> /usr/local/Cellar/openjdk@17/17.0.12/libexec/openjdk.jdk/Contents/Home
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "14.6.1", arch: "x86_64", family: "mac"
> Darwin 23.6.0 Darwin Kernel Version 23.6.0: Mon Jul 29 21:13:00 PDT
> 2024; root:xnu-10063.141.2~1/RELEASE_X86_64 x86_64
>Reporter: Gary D. Gregory
>Assignee: Michael Osipov
>Priority: Major
> Attachments: screenshot-1.png
>
>
> java.lang.NoSuchMethodError: 'void
> org.apache.maven.doxia.sink.Sink.verbatim()' updating from 3.24.0 to 3.25.0
> {noformat}
> java.lang.NoSuchMethodError: 'void
> org.apache.maven.doxia.sink.Sink.verbatim()'
> at org.apache.maven.reporting.AbstractMavenReportRenderer.verbatimText
> (AbstractMavenReportRenderer.java:363)
> at org.apache.maven.plugins.pmd.CpdReportRenderer.renderDuplications
> (CpdReportRenderer.java:171)
> at org.apache.maven.plugins.pmd.CpdReportRenderer.renderBody
> (CpdReportRenderer.java:96)
> at org.apache.maven.reporting.AbstractMavenReportRenderer.render
> (AbstractMavenReportRenderer.java:93)
> at org.apache.maven.plugins.pmd.CpdReport.executeReport
> (CpdReport.java:140)
> at org.apache.maven.reporting.AbstractMavenReport.generate
> (AbstractMavenReport.java:354)
> at
> org.apache.maven.plugins.site.render.ReportDocumentRenderer.renderDocument
> (ReportDocumentRenderer.java:226)
> at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render
> (DefaultSiteRenderer.java:348)
> at org.apache.maven.plugins.site.render.SiteMojo.renderLocale
> (SiteMojo.java:194)
> at org.apache.maven.plugins.site.render.SiteMojo.execute
> (SiteMojo.java:143)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:126)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:328)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:316)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:174)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
> (MojoExecutor.java:75)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
> (MojoExecutor.java:162)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:159)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:105)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:73)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:53)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:118)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:261)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:173)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:101)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:906)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:283)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:206)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:77)
> at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:569)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:255)
> at org.codehaus.plexus.classworlds.launcher.L
[jira] [Commented] (MPMD-406) java.lang.NoSuchMethodError: 'void org.apache.maven.doxia.sink.Sink.verbatim()' updating from 3.24.0 to 3.25.0
[
https://issues.apache.org/jira/browse/MPMD-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17887113#comment-17887113
]
Michael Osipov commented on MPMD-406:
-
With
{noformat}
diff --git a/pom.xml b/pom.xml
index b090ec5..d5f9167 100644
--- a/pom.xml
+++ b/pom.xml
@@ -196 +196 @@
-3.12.1
+3.20.0
{noformat}
I get
!screenshot-1.png!
You need to fix the skin before you continue to upgrade.
> java.lang.NoSuchMethodError: 'void
> org.apache.maven.doxia.sink.Sink.verbatim()' updating from 3.24.0 to 3.25.0
> --
>
> Key: MPMD-406
> URL: https://issues.apache.org/jira/browse/MPMD-406
> Project: Maven PMD Plugin
> Issue Type: Bug
>Affects Versions: 3.25.0
> Environment: openjdk version "17.0.12" 2024-07-16
> OpenJDK Runtime Environment Homebrew (build 17.0.12+0)
> OpenJDK 64-Bit Server VM Homebrew (build 17.0.12+0, mixed mode, sharing)
> Apache Maven 3.9.9 (8e8579a9e76f7d015ee5ec7bfcdc97d260186937)
> Maven home: /usr/local/Cellar/maven/3.9.9/libexec
> Java version: 17.0.12, vendor: Homebrew, runtime:
> /usr/local/Cellar/openjdk@17/17.0.12/libexec/openjdk.jdk/Contents/Home
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "14.6.1", arch: "x86_64", family: "mac"
> Darwin 23.6.0 Darwin Kernel Version 23.6.0: Mon Jul 29 21:13:00 PDT
> 2024; root:xnu-10063.141.2~1/RELEASE_X86_64 x86_64
>Reporter: Gary D. Gregory
>Assignee: Michael Osipov
>Priority: Major
> Attachments: screenshot-1.png
>
>
> java.lang.NoSuchMethodError: 'void
> org.apache.maven.doxia.sink.Sink.verbatim()' updating from 3.24.0 to 3.25.0
> {noformat}
> java.lang.NoSuchMethodError: 'void
> org.apache.maven.doxia.sink.Sink.verbatim()'
> at org.apache.maven.reporting.AbstractMavenReportRenderer.verbatimText
> (AbstractMavenReportRenderer.java:363)
> at org.apache.maven.plugins.pmd.CpdReportRenderer.renderDuplications
> (CpdReportRenderer.java:171)
> at org.apache.maven.plugins.pmd.CpdReportRenderer.renderBody
> (CpdReportRenderer.java:96)
> at org.apache.maven.reporting.AbstractMavenReportRenderer.render
> (AbstractMavenReportRenderer.java:93)
> at org.apache.maven.plugins.pmd.CpdReport.executeReport
> (CpdReport.java:140)
> at org.apache.maven.reporting.AbstractMavenReport.generate
> (AbstractMavenReport.java:354)
> at
> org.apache.maven.plugins.site.render.ReportDocumentRenderer.renderDocument
> (ReportDocumentRenderer.java:226)
> at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render
> (DefaultSiteRenderer.java:348)
> at org.apache.maven.plugins.site.render.SiteMojo.renderLocale
> (SiteMojo.java:194)
> at org.apache.maven.plugins.site.render.SiteMojo.execute
> (SiteMojo.java:143)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:126)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:328)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:316)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:174)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
> (MojoExecutor.java:75)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
> (MojoExecutor.java:162)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:159)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:105)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:73)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:53)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:118)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:261)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:173)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:101)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:906)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:283)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:206)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:77)
> at jdk.internal.reflect.DelegatingMethodAcce
[jira] [Commented] (MPMD-406) java.lang.NoSuchMethodError: 'void org.apache.maven.doxia.sink.Sink.verbatim()' updating from 3.24.0 to 3.25.0
[
https://issues.apache.org/jira/browse/MPMD-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17887114#comment-17887114
]
Gary D. Gregory commented on MPMD-406:
--
[~michael-o]
Thank you for the tips!
It is painful to deal this type of issue when the site
https://maven.apache.org/skins/index.html lists this skin as the FIRST
MAINTAINED skin!
> java.lang.NoSuchMethodError: 'void
> org.apache.maven.doxia.sink.Sink.verbatim()' updating from 3.24.0 to 3.25.0
> --
>
> Key: MPMD-406
> URL: https://issues.apache.org/jira/browse/MPMD-406
> Project: Maven PMD Plugin
> Issue Type: Bug
>Affects Versions: 3.25.0
> Environment: openjdk version "17.0.12" 2024-07-16
> OpenJDK Runtime Environment Homebrew (build 17.0.12+0)
> OpenJDK 64-Bit Server VM Homebrew (build 17.0.12+0, mixed mode, sharing)
> Apache Maven 3.9.9 (8e8579a9e76f7d015ee5ec7bfcdc97d260186937)
> Maven home: /usr/local/Cellar/maven/3.9.9/libexec
> Java version: 17.0.12, vendor: Homebrew, runtime:
> /usr/local/Cellar/openjdk@17/17.0.12/libexec/openjdk.jdk/Contents/Home
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "14.6.1", arch: "x86_64", family: "mac"
> Darwin 23.6.0 Darwin Kernel Version 23.6.0: Mon Jul 29 21:13:00 PDT
> 2024; root:xnu-10063.141.2~1/RELEASE_X86_64 x86_64
>Reporter: Gary D. Gregory
>Assignee: Michael Osipov
>Priority: Major
> Attachments: screenshot-1.png
>
>
> java.lang.NoSuchMethodError: 'void
> org.apache.maven.doxia.sink.Sink.verbatim()' updating from 3.24.0 to 3.25.0
> {noformat}
> java.lang.NoSuchMethodError: 'void
> org.apache.maven.doxia.sink.Sink.verbatim()'
> at org.apache.maven.reporting.AbstractMavenReportRenderer.verbatimText
> (AbstractMavenReportRenderer.java:363)
> at org.apache.maven.plugins.pmd.CpdReportRenderer.renderDuplications
> (CpdReportRenderer.java:171)
> at org.apache.maven.plugins.pmd.CpdReportRenderer.renderBody
> (CpdReportRenderer.java:96)
> at org.apache.maven.reporting.AbstractMavenReportRenderer.render
> (AbstractMavenReportRenderer.java:93)
> at org.apache.maven.plugins.pmd.CpdReport.executeReport
> (CpdReport.java:140)
> at org.apache.maven.reporting.AbstractMavenReport.generate
> (AbstractMavenReport.java:354)
> at
> org.apache.maven.plugins.site.render.ReportDocumentRenderer.renderDocument
> (ReportDocumentRenderer.java:226)
> at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render
> (DefaultSiteRenderer.java:348)
> at org.apache.maven.plugins.site.render.SiteMojo.renderLocale
> (SiteMojo.java:194)
> at org.apache.maven.plugins.site.render.SiteMojo.execute
> (SiteMojo.java:143)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:126)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:328)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:316)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:174)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
> (MojoExecutor.java:75)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
> (MojoExecutor.java:162)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:159)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:105)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:73)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:53)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:118)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:261)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:173)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:101)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:906)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:283)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:206)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:77)
> at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:
[jira] [Comment Edited] (MPMD-406) java.lang.NoSuchMethodError: 'void org.apache.maven.doxia.sink.Sink.verbatim()' updating from 3.24.0 to 3.25.0
[
https://issues.apache.org/jira/browse/MPMD-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17887114#comment-17887114
]
Gary D. Gregory edited comment on MPMD-406 at 10/5/24 2:43 PM:
---
[~michael-o]
Thank you for the tips!
It is painful to deal this type of issue when the site
https://maven.apache.org/skins/index.html lists this skin as the FIRST
MAINTAINED skin! :P
was (Author: garydgregory):
[~michael-o]
Thank you for the tips!
It is painful to deal this type of issue when the site
https://maven.apache.org/skins/index.html lists this skin as the FIRST
MAINTAINED skin!
> java.lang.NoSuchMethodError: 'void
> org.apache.maven.doxia.sink.Sink.verbatim()' updating from 3.24.0 to 3.25.0
> --
>
> Key: MPMD-406
> URL: https://issues.apache.org/jira/browse/MPMD-406
> Project: Maven PMD Plugin
> Issue Type: Bug
>Affects Versions: 3.25.0
> Environment: openjdk version "17.0.12" 2024-07-16
> OpenJDK Runtime Environment Homebrew (build 17.0.12+0)
> OpenJDK 64-Bit Server VM Homebrew (build 17.0.12+0, mixed mode, sharing)
> Apache Maven 3.9.9 (8e8579a9e76f7d015ee5ec7bfcdc97d260186937)
> Maven home: /usr/local/Cellar/maven/3.9.9/libexec
> Java version: 17.0.12, vendor: Homebrew, runtime:
> /usr/local/Cellar/openjdk@17/17.0.12/libexec/openjdk.jdk/Contents/Home
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "14.6.1", arch: "x86_64", family: "mac"
> Darwin 23.6.0 Darwin Kernel Version 23.6.0: Mon Jul 29 21:13:00 PDT
> 2024; root:xnu-10063.141.2~1/RELEASE_X86_64 x86_64
>Reporter: Gary D. Gregory
>Assignee: Michael Osipov
>Priority: Major
> Attachments: screenshot-1.png
>
>
> java.lang.NoSuchMethodError: 'void
> org.apache.maven.doxia.sink.Sink.verbatim()' updating from 3.24.0 to 3.25.0
> {noformat}
> java.lang.NoSuchMethodError: 'void
> org.apache.maven.doxia.sink.Sink.verbatim()'
> at org.apache.maven.reporting.AbstractMavenReportRenderer.verbatimText
> (AbstractMavenReportRenderer.java:363)
> at org.apache.maven.plugins.pmd.CpdReportRenderer.renderDuplications
> (CpdReportRenderer.java:171)
> at org.apache.maven.plugins.pmd.CpdReportRenderer.renderBody
> (CpdReportRenderer.java:96)
> at org.apache.maven.reporting.AbstractMavenReportRenderer.render
> (AbstractMavenReportRenderer.java:93)
> at org.apache.maven.plugins.pmd.CpdReport.executeReport
> (CpdReport.java:140)
> at org.apache.maven.reporting.AbstractMavenReport.generate
> (AbstractMavenReport.java:354)
> at
> org.apache.maven.plugins.site.render.ReportDocumentRenderer.renderDocument
> (ReportDocumentRenderer.java:226)
> at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render
> (DefaultSiteRenderer.java:348)
> at org.apache.maven.plugins.site.render.SiteMojo.renderLocale
> (SiteMojo.java:194)
> at org.apache.maven.plugins.site.render.SiteMojo.execute
> (SiteMojo.java:143)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:126)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:328)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:316)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:174)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
> (MojoExecutor.java:75)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
> (MojoExecutor.java:162)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:159)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:105)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:73)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:53)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:118)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:261)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:173)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:101)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:906)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:283)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:206)
> at jdk.inte
[jira] [Commented] (MPMD-406) java.lang.NoSuchMethodError: 'void org.apache.maven.doxia.sink.Sink.verbatim()' updating from 3.24.0 to 3.25.0
[
https://issues.apache.org/jira/browse/MPMD-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17887115#comment-17887115
]
Gary D. Gregory commented on MPMD-406:
--
"You need to fix the skin before you continue to upgrade."
I was trying to work around that by not using the skin in the first place :D
> java.lang.NoSuchMethodError: 'void
> org.apache.maven.doxia.sink.Sink.verbatim()' updating from 3.24.0 to 3.25.0
> --
>
> Key: MPMD-406
> URL: https://issues.apache.org/jira/browse/MPMD-406
> Project: Maven PMD Plugin
> Issue Type: Bug
>Affects Versions: 3.25.0
> Environment: openjdk version "17.0.12" 2024-07-16
> OpenJDK Runtime Environment Homebrew (build 17.0.12+0)
> OpenJDK 64-Bit Server VM Homebrew (build 17.0.12+0, mixed mode, sharing)
> Apache Maven 3.9.9 (8e8579a9e76f7d015ee5ec7bfcdc97d260186937)
> Maven home: /usr/local/Cellar/maven/3.9.9/libexec
> Java version: 17.0.12, vendor: Homebrew, runtime:
> /usr/local/Cellar/openjdk@17/17.0.12/libexec/openjdk.jdk/Contents/Home
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "14.6.1", arch: "x86_64", family: "mac"
> Darwin 23.6.0 Darwin Kernel Version 23.6.0: Mon Jul 29 21:13:00 PDT
> 2024; root:xnu-10063.141.2~1/RELEASE_X86_64 x86_64
>Reporter: Gary D. Gregory
>Assignee: Michael Osipov
>Priority: Major
> Attachments: screenshot-1.png
>
>
> java.lang.NoSuchMethodError: 'void
> org.apache.maven.doxia.sink.Sink.verbatim()' updating from 3.24.0 to 3.25.0
> {noformat}
> java.lang.NoSuchMethodError: 'void
> org.apache.maven.doxia.sink.Sink.verbatim()'
> at org.apache.maven.reporting.AbstractMavenReportRenderer.verbatimText
> (AbstractMavenReportRenderer.java:363)
> at org.apache.maven.plugins.pmd.CpdReportRenderer.renderDuplications
> (CpdReportRenderer.java:171)
> at org.apache.maven.plugins.pmd.CpdReportRenderer.renderBody
> (CpdReportRenderer.java:96)
> at org.apache.maven.reporting.AbstractMavenReportRenderer.render
> (AbstractMavenReportRenderer.java:93)
> at org.apache.maven.plugins.pmd.CpdReport.executeReport
> (CpdReport.java:140)
> at org.apache.maven.reporting.AbstractMavenReport.generate
> (AbstractMavenReport.java:354)
> at
> org.apache.maven.plugins.site.render.ReportDocumentRenderer.renderDocument
> (ReportDocumentRenderer.java:226)
> at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render
> (DefaultSiteRenderer.java:348)
> at org.apache.maven.plugins.site.render.SiteMojo.renderLocale
> (SiteMojo.java:194)
> at org.apache.maven.plugins.site.render.SiteMojo.execute
> (SiteMojo.java:143)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:126)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:328)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:316)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:174)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
> (MojoExecutor.java:75)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
> (MojoExecutor.java:162)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:159)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:105)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:73)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:53)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:118)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:261)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:173)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:101)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:906)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:283)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:206)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:77)
> at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (M
[jira] [Commented] (MPMD-406) java.lang.NoSuchMethodError: 'void org.apache.maven.doxia.sink.Sink.verbatim()' updating from 3.24.0 to 3.25.0
[
https://issues.apache.org/jira/browse/MPMD-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17887132#comment-17887132
]
Gary D. Gregory commented on MPMD-406:
--
Yep, the links are fixed and now have the same problems as all other links to
GitBox, they redirect to GitHub which is not great but a long-standing issue.
> java.lang.NoSuchMethodError: 'void
> org.apache.maven.doxia.sink.Sink.verbatim()' updating from 3.24.0 to 3.25.0
> --
>
> Key: MPMD-406
> URL: https://issues.apache.org/jira/browse/MPMD-406
> Project: Maven PMD Plugin
> Issue Type: Bug
>Affects Versions: 3.25.0
> Environment: openjdk version "17.0.12" 2024-07-16
> OpenJDK Runtime Environment Homebrew (build 17.0.12+0)
> OpenJDK 64-Bit Server VM Homebrew (build 17.0.12+0, mixed mode, sharing)
> Apache Maven 3.9.9 (8e8579a9e76f7d015ee5ec7bfcdc97d260186937)
> Maven home: /usr/local/Cellar/maven/3.9.9/libexec
> Java version: 17.0.12, vendor: Homebrew, runtime:
> /usr/local/Cellar/openjdk@17/17.0.12/libexec/openjdk.jdk/Contents/Home
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "14.6.1", arch: "x86_64", family: "mac"
> Darwin 23.6.0 Darwin Kernel Version 23.6.0: Mon Jul 29 21:13:00 PDT
> 2024; root:xnu-10063.141.2~1/RELEASE_X86_64 x86_64
>Reporter: Gary D. Gregory
>Assignee: Michael Osipov
>Priority: Major
> Attachments: screenshot-1.png
>
>
> java.lang.NoSuchMethodError: 'void
> org.apache.maven.doxia.sink.Sink.verbatim()' updating from 3.24.0 to 3.25.0
> {noformat}
> java.lang.NoSuchMethodError: 'void
> org.apache.maven.doxia.sink.Sink.verbatim()'
> at org.apache.maven.reporting.AbstractMavenReportRenderer.verbatimText
> (AbstractMavenReportRenderer.java:363)
> at org.apache.maven.plugins.pmd.CpdReportRenderer.renderDuplications
> (CpdReportRenderer.java:171)
> at org.apache.maven.plugins.pmd.CpdReportRenderer.renderBody
> (CpdReportRenderer.java:96)
> at org.apache.maven.reporting.AbstractMavenReportRenderer.render
> (AbstractMavenReportRenderer.java:93)
> at org.apache.maven.plugins.pmd.CpdReport.executeReport
> (CpdReport.java:140)
> at org.apache.maven.reporting.AbstractMavenReport.generate
> (AbstractMavenReport.java:354)
> at
> org.apache.maven.plugins.site.render.ReportDocumentRenderer.renderDocument
> (ReportDocumentRenderer.java:226)
> at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render
> (DefaultSiteRenderer.java:348)
> at org.apache.maven.plugins.site.render.SiteMojo.renderLocale
> (SiteMojo.java:194)
> at org.apache.maven.plugins.site.render.SiteMojo.execute
> (SiteMojo.java:143)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:126)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:328)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:316)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:174)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
> (MojoExecutor.java:75)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
> (MojoExecutor.java:162)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:159)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:105)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:73)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:53)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:118)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:261)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:173)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:101)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:906)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:283)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:206)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:77)
> at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.ref
[jira] [Commented] (MCOMPILER-592) IndexOutOfBoundsException when project.build.outputTimestamp is empty
[ https://issues.apache.org/jira/browse/MCOMPILER-592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17887150#comment-17887150 ] Sergey Ponomarev commented on MCOMPILER-592: This was fixed and merged so can be closed. But I think we should remove the useless validation that caused the exception https://github.com/apache/maven-compiler-plugin/pull/266 > IndexOutOfBoundsException when project.build.outputTimestamp is empty > - > > Key: MCOMPILER-592 > URL: https://issues.apache.org/jira/browse/MCOMPILER-592 > Project: Maven Compiler Plugin > Issue Type: Bug >Affects Versions: 3.12.0, 3.12.1, 3.13.0 >Reporter: Thijs Rijpert >Priority: Minor > > Due to a combination of plugins, it is possible for the > project.build.outputTimestamp property to have an empty string as a value. > This causes an IndexOutOfBoundsException on line 1242 when it tries to access > the first character in the string. > This can be fixed by doing an isEmpty check before doing the charAt check. I > will create an PR for this. > While this bug is caused by another plugin, I think this should be fixed in > the compiler because the error returned (IndexOutOfBoundsException), is vague > and hard to debug. > The workaround for this issue is setting the project.build.outputTimestamp > property with an arbitrary value. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MNG-8286) Add a condition profile based on a simple expressions
[
https://issues.apache.org/jira/browse/MNG-8286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet updated MNG-8286:
-
Description:
GitHub Pull Request: [https://github.com/apache/maven/pull/1771]
h1. Condition-Based Profile Activation in Maven
In addition to the traditional activation mechanisms (JDK version, OS
properties, file existence, etc.), Maven now supports a powerful
condition-based activation through the condition field. This new mechanism
allows for more flexible and expressive profile activation rules.
h2. Condition Syntax
The condition is specified as a string expression that can include various
functions, comparisons, and logical operators.
Some key features include:
Property access: {{{}$\{property.name{
Comparison operators: {{{}=={}}}, {{{}!={}}}, {{{}<{}}}, {{{}>{}}}, {{{}<={}}},
{{>=}}
Logical operators: {{&&}} (AND), {{||}} (OR), {{not(...)}}
Functions: {{{}exists(...){}}}, {{{}missing(...){}}}, {{{}matches(...){}}},
{{{}inrange(...){}}}, and more
h2. Supported Functions
The following functions are supported in condition expressions:
* {{{}length(string){}}}: Returns the length of the given string.
* {{{}upper(string){}}}: Converts the string to uppercase.
* {{{}lower(string){}}}: Converts the string to lowercase.
* {{{}substring(string, start, [end]){}}}: Returns a substring of the given
string.
* {{{}indexOf(string, substring){}}}: Returns the index of the first occurrence
of substring in string, or -1 if not found.
* {{{}contains(string, substring){}}}: Checks if the string contains the
substring.
* {{{}matches(string, regex){}}}: Checks if the string matches the given
regular expression.
* {{{}not(condition){}}}: Negates the given condition.
* {{{}if(condition, trueValue, falseValue){}}}: Returns trueValue if the
condition is true, falseValue otherwise.
* {{{}exists(path){}}}: Checks if the file or directory at the given path
exists.
* {{{}missing(path){}}}: Checks if the file or directory at the given path does
not exist.
* {{{}inrange(version, range){}}}: Checks if the given version is within the
specified version range.
h2. Examples
* JDK version range: {{inrange(${java.version}, '[11,)')}} (JDK 11 or higher)
* OS check: {{${os.name} == 'windows'}}
* File existence: {{exists('${project.basedir}/some-file.txt')}}
* Property check: {{${my.property} != 'some-value'}}
* Regex matching: {{matches(${os.version}, '.*aws')}}
* Complex condition: {{${os.name} == 'windows' && ${os.arch} != 'amd64' &&
inrange(${os.version}, '[10,)')}}
* String length check: {{length(${user.name}) > 5}}
* Substring with version: {{substring(${java.version}, 0, 3) == '1.8'}}
* Using indexOf: {{indexOf(${java.version}, '-') > 0}}
* Conditional logic: {{if(contains(${java.version}, '\-'),
substring(${java.version}, 0, indexOf(${java.version}, '-')), ${java.version})}}
This flexible condition mechanism allows for more precise control over profile
activation, enabling developers to create profiles that respond to a wide range
of environmental factors and project states.
This will be triggered using a new profile activation in the 4.1.0 model:
{code:xml}
inrange(${maven.version}, '[4,)')
{code}
was:
GitHub Pull Request: https://github.com/apache/maven/pull/1771
This adds a profile activation expression to the 4.1.0 model:
{code}
inrange(${maven.version}, '[4,)')
{code}
Other examples:
{code}
${os.name} == 'windows' && ${os.arch} != 'amd64' && inrange(${os.version},
'[99,)')
exists('${project.rootDirectory}/someFile.txt')
inrange(${java.version}, '[1.8,)')
{code}
> Add a condition profile based on a simple expressions
> -
>
> Key: MNG-8286
> URL: https://issues.apache.org/jira/browse/MNG-8286
> Project: Maven
> Issue Type: New Feature
>Reporter: Guillaume Nodet
>Assignee: Guillaume Nodet
>Priority: Major
> Fix For: 4.0.0-beta-5
>
>
> GitHub Pull Request: [https://github.com/apache/maven/pull/1771]
> h1. Condition-Based Profile Activation in Maven
> In addition to the traditional activation mechanisms (JDK version, OS
> properties, file existence, etc.), Maven now supports a powerful
> condition-based activation through the condition field. This new mechanism
> allows for more flexible and expressive profile activation rules.
> h2. Condition Syntax
> The condition is specified as a string expression that can include various
> functions, comparisons, and logical operators.
> Some key features include:
> Property access: {{{}$\{property.name{
> Comparison operators: {{{}=={}}}, {{{}!={}}}, {{{}<{}}}, {{{}>{}}},
> {{{}<={}}}, {{>=}}
> Logical operators: {{&&}} (AND), {{||}} (OR), {{not(...)}}
> Functions: {{{}exists(...){}}}, {{{}missing(...){}}}, {{{}matches(...){}}},
> {{{}inrange(...){}}}, and more
> h2. Support
[jira] [Assigned] (ARCHETYPE-683) [REGRESSION] groovy.json.JsonOutput not found
[
https://issues.apache.org/jira/browse/ARCHETYPE-683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Slawomir Jaranowski reassigned ARCHETYPE-683:
-
Assignee: Slawomir Jaranowski
> [REGRESSION] groovy.json.JsonOutput not found
> -
>
> Key: ARCHETYPE-683
> URL: https://issues.apache.org/jira/browse/ARCHETYPE-683
> Project: Maven Archetype
> Issue Type: Bug
> Components: Archetypes, Generator
>Affects Versions: 3.3.0
>Reporter: Dirk Rosemann
>Assignee: Slawomir Jaranowski
>Priority: Major
> Fix For: 3.3.1
>
>
> I use groovy.json.JsonOutput in partial archetype's
> archetype-post-generate.groovy, first line of my code is "import
> groovy.json.JsonOutput".
> Since archetype v3.3.0 I receive the following error on archetype:generate
> goal execution:
>
> {noformat}
> Failed to execute goal
> org.apache.maven.plugins:maven-archetype-plugin:3.3.0:generate (default-cli)
> {...}
> Script1.groovy: 1: unable to resolve class groovy.json.JsonOutput
> @ line 1, column 1.
> import groovy.json.JsonOutput
> ^
> 1 error{noformat}
> Workaround is to force usage of v3.2.1 version when using partial archetype,
> like so:
>
> {code:java}
>
>
>
> org.apache.maven.plugins
> maven-archetype-plugin
> 3.2.1
>
>
> {code}
> This issue seems to be related to
> https://issues.apache.org/jira/browse/ARCHETYPE-679.
> Please let me know if you need any additional information.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MPMD-406) java.lang.NoSuchMethodError: 'void org.apache.maven.doxia.sink.Sink.verbatim()' updating from 3.24.0 to 3.25.0
[
https://issues.apache.org/jira/browse/MPMD-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17887116#comment-17887116
]
Michael Osipov commented on MPMD-406:
-
This works for me:
{noformat}
osipovmi@deblndw011x:/tmp/commons-text (master *=)
$ git diff -U0
diff --git a/pom.xml b/pom.xml
index 419d3761..fa2c004e 100644
--- a/pom.xml
+++ b/pom.xml
@@ -23 +23 @@
-76
+77-SNAPSHOT
{noformat}
and
{noformat}
osipovmi@deblndw011x:/tmp/commons-parent (master *=)
$ git diff -U0
diff --git a/pom.xml b/pom.xml
index b090ec5..d5f9167 100644
--- a/pom.xml
+++ b/pom.xml
@@ -196 +196 @@
-3.12.1
+3.20.0
diff --git a/src/site/site.xml b/src/site/site.xml
index 017377c..a5f1171 100644
--- a/src/site/site.xml
+++ b/src/site/site.xml
@@ -54,3 +54,3 @@
-org.apache.commons
-commons-skin
-4.2
+org.apache.maven.skins
+maven-fluido-skin
+2.0.0-M11
{noformat}
As said, you need to fix the skin first and constrain it in the {{skin.xml}}.
> java.lang.NoSuchMethodError: 'void
> org.apache.maven.doxia.sink.Sink.verbatim()' updating from 3.24.0 to 3.25.0
> --
>
> Key: MPMD-406
> URL: https://issues.apache.org/jira/browse/MPMD-406
> Project: Maven PMD Plugin
> Issue Type: Bug
>Affects Versions: 3.25.0
> Environment: openjdk version "17.0.12" 2024-07-16
> OpenJDK Runtime Environment Homebrew (build 17.0.12+0)
> OpenJDK 64-Bit Server VM Homebrew (build 17.0.12+0, mixed mode, sharing)
> Apache Maven 3.9.9 (8e8579a9e76f7d015ee5ec7bfcdc97d260186937)
> Maven home: /usr/local/Cellar/maven/3.9.9/libexec
> Java version: 17.0.12, vendor: Homebrew, runtime:
> /usr/local/Cellar/openjdk@17/17.0.12/libexec/openjdk.jdk/Contents/Home
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "14.6.1", arch: "x86_64", family: "mac"
> Darwin 23.6.0 Darwin Kernel Version 23.6.0: Mon Jul 29 21:13:00 PDT
> 2024; root:xnu-10063.141.2~1/RELEASE_X86_64 x86_64
>Reporter: Gary D. Gregory
>Assignee: Michael Osipov
>Priority: Major
> Attachments: screenshot-1.png
>
>
> java.lang.NoSuchMethodError: 'void
> org.apache.maven.doxia.sink.Sink.verbatim()' updating from 3.24.0 to 3.25.0
> {noformat}
> java.lang.NoSuchMethodError: 'void
> org.apache.maven.doxia.sink.Sink.verbatim()'
> at org.apache.maven.reporting.AbstractMavenReportRenderer.verbatimText
> (AbstractMavenReportRenderer.java:363)
> at org.apache.maven.plugins.pmd.CpdReportRenderer.renderDuplications
> (CpdReportRenderer.java:171)
> at org.apache.maven.plugins.pmd.CpdReportRenderer.renderBody
> (CpdReportRenderer.java:96)
> at org.apache.maven.reporting.AbstractMavenReportRenderer.render
> (AbstractMavenReportRenderer.java:93)
> at org.apache.maven.plugins.pmd.CpdReport.executeReport
> (CpdReport.java:140)
> at org.apache.maven.reporting.AbstractMavenReport.generate
> (AbstractMavenReport.java:354)
> at
> org.apache.maven.plugins.site.render.ReportDocumentRenderer.renderDocument
> (ReportDocumentRenderer.java:226)
> at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render
> (DefaultSiteRenderer.java:348)
> at org.apache.maven.plugins.site.render.SiteMojo.renderLocale
> (SiteMojo.java:194)
> at org.apache.maven.plugins.site.render.SiteMojo.execute
> (SiteMojo.java:143)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:126)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:328)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:316)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:174)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
> (MojoExecutor.java:75)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
> (MojoExecutor.java:162)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:159)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:105)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:73)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:53)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:118)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:261)
> at
[jira] [Commented] (MPMD-406) java.lang.NoSuchMethodError: 'void org.apache.maven.doxia.sink.Sink.verbatim()' updating from 3.24.0 to 3.25.0
[
https://issues.apache.org/jira/browse/MPMD-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17887117#comment-17887117
]
Michael Osipov commented on MPMD-406:
-
[~ggregory], I agree with you on the skin. I'll change the line while it still
needs formal retirement. Given that I work more or less alone on that stuff I
miss hands everywhere :-(
> java.lang.NoSuchMethodError: 'void
> org.apache.maven.doxia.sink.Sink.verbatim()' updating from 3.24.0 to 3.25.0
> --
>
> Key: MPMD-406
> URL: https://issues.apache.org/jira/browse/MPMD-406
> Project: Maven PMD Plugin
> Issue Type: Bug
>Affects Versions: 3.25.0
> Environment: openjdk version "17.0.12" 2024-07-16
> OpenJDK Runtime Environment Homebrew (build 17.0.12+0)
> OpenJDK 64-Bit Server VM Homebrew (build 17.0.12+0, mixed mode, sharing)
> Apache Maven 3.9.9 (8e8579a9e76f7d015ee5ec7bfcdc97d260186937)
> Maven home: /usr/local/Cellar/maven/3.9.9/libexec
> Java version: 17.0.12, vendor: Homebrew, runtime:
> /usr/local/Cellar/openjdk@17/17.0.12/libexec/openjdk.jdk/Contents/Home
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "14.6.1", arch: "x86_64", family: "mac"
> Darwin 23.6.0 Darwin Kernel Version 23.6.0: Mon Jul 29 21:13:00 PDT
> 2024; root:xnu-10063.141.2~1/RELEASE_X86_64 x86_64
>Reporter: Gary D. Gregory
>Assignee: Michael Osipov
>Priority: Major
> Attachments: screenshot-1.png
>
>
> java.lang.NoSuchMethodError: 'void
> org.apache.maven.doxia.sink.Sink.verbatim()' updating from 3.24.0 to 3.25.0
> {noformat}
> java.lang.NoSuchMethodError: 'void
> org.apache.maven.doxia.sink.Sink.verbatim()'
> at org.apache.maven.reporting.AbstractMavenReportRenderer.verbatimText
> (AbstractMavenReportRenderer.java:363)
> at org.apache.maven.plugins.pmd.CpdReportRenderer.renderDuplications
> (CpdReportRenderer.java:171)
> at org.apache.maven.plugins.pmd.CpdReportRenderer.renderBody
> (CpdReportRenderer.java:96)
> at org.apache.maven.reporting.AbstractMavenReportRenderer.render
> (AbstractMavenReportRenderer.java:93)
> at org.apache.maven.plugins.pmd.CpdReport.executeReport
> (CpdReport.java:140)
> at org.apache.maven.reporting.AbstractMavenReport.generate
> (AbstractMavenReport.java:354)
> at
> org.apache.maven.plugins.site.render.ReportDocumentRenderer.renderDocument
> (ReportDocumentRenderer.java:226)
> at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render
> (DefaultSiteRenderer.java:348)
> at org.apache.maven.plugins.site.render.SiteMojo.renderLocale
> (SiteMojo.java:194)
> at org.apache.maven.plugins.site.render.SiteMojo.execute
> (SiteMojo.java:143)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:126)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:328)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:316)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:174)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
> (MojoExecutor.java:75)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
> (MojoExecutor.java:162)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:159)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:105)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:73)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:53)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:118)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:261)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:173)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:101)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:906)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:283)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:206)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:77)
> at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:4
[jira] [Commented] (MPMD-406) java.lang.NoSuchMethodError: 'void org.apache.maven.doxia.sink.Sink.verbatim()' updating from 3.24.0 to 3.25.0
[
https://issues.apache.org/jira/browse/MPMD-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17887118#comment-17887118
]
Gary D. Gregory commented on MPMD-406:
--
"Fix the skin". Where is _that_ documented? I don't know what that means :-) I
just see garbled output like your screenshot. Do I copy-paste the Fluido skink
into the Commons Skin?
If I could get rid of the custom Commons Skin, that would be best...
Based on the site, it sounds like using the current Fluido skin means using the
version 4 of site plugin, but what else is that going to break?
> java.lang.NoSuchMethodError: 'void
> org.apache.maven.doxia.sink.Sink.verbatim()' updating from 3.24.0 to 3.25.0
> --
>
> Key: MPMD-406
> URL: https://issues.apache.org/jira/browse/MPMD-406
> Project: Maven PMD Plugin
> Issue Type: Bug
>Affects Versions: 3.25.0
> Environment: openjdk version "17.0.12" 2024-07-16
> OpenJDK Runtime Environment Homebrew (build 17.0.12+0)
> OpenJDK 64-Bit Server VM Homebrew (build 17.0.12+0, mixed mode, sharing)
> Apache Maven 3.9.9 (8e8579a9e76f7d015ee5ec7bfcdc97d260186937)
> Maven home: /usr/local/Cellar/maven/3.9.9/libexec
> Java version: 17.0.12, vendor: Homebrew, runtime:
> /usr/local/Cellar/openjdk@17/17.0.12/libexec/openjdk.jdk/Contents/Home
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "14.6.1", arch: "x86_64", family: "mac"
> Darwin 23.6.0 Darwin Kernel Version 23.6.0: Mon Jul 29 21:13:00 PDT
> 2024; root:xnu-10063.141.2~1/RELEASE_X86_64 x86_64
>Reporter: Gary D. Gregory
>Assignee: Michael Osipov
>Priority: Major
> Attachments: screenshot-1.png
>
>
> java.lang.NoSuchMethodError: 'void
> org.apache.maven.doxia.sink.Sink.verbatim()' updating from 3.24.0 to 3.25.0
> {noformat}
> java.lang.NoSuchMethodError: 'void
> org.apache.maven.doxia.sink.Sink.verbatim()'
> at org.apache.maven.reporting.AbstractMavenReportRenderer.verbatimText
> (AbstractMavenReportRenderer.java:363)
> at org.apache.maven.plugins.pmd.CpdReportRenderer.renderDuplications
> (CpdReportRenderer.java:171)
> at org.apache.maven.plugins.pmd.CpdReportRenderer.renderBody
> (CpdReportRenderer.java:96)
> at org.apache.maven.reporting.AbstractMavenReportRenderer.render
> (AbstractMavenReportRenderer.java:93)
> at org.apache.maven.plugins.pmd.CpdReport.executeReport
> (CpdReport.java:140)
> at org.apache.maven.reporting.AbstractMavenReport.generate
> (AbstractMavenReport.java:354)
> at
> org.apache.maven.plugins.site.render.ReportDocumentRenderer.renderDocument
> (ReportDocumentRenderer.java:226)
> at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render
> (DefaultSiteRenderer.java:348)
> at org.apache.maven.plugins.site.render.SiteMojo.renderLocale
> (SiteMojo.java:194)
> at org.apache.maven.plugins.site.render.SiteMojo.execute
> (SiteMojo.java:143)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:126)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:328)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:316)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:174)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
> (MojoExecutor.java:75)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
> (MojoExecutor.java:162)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:159)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:105)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:73)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:53)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:118)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:261)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:173)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:101)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:906)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:283)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:206)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Nat
[jira] [Commented] (MPMD-406) java.lang.NoSuchMethodError: 'void org.apache.maven.doxia.sink.Sink.verbatim()' updating from 3.24.0 to 3.25.0
[
https://issues.apache.org/jira/browse/MPMD-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17887120#comment-17887120
]
Gary D. Gregory commented on MPMD-406:
--
Here's another wrinkle, using site 3.20.0 and if I comment out the skin
declaration in site.xml, to use the default, it blows up:
{code:java}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.20.0:site (default-site) on
project commons-parent: Execution default-site of goal
org.apache.maven.plugins:maven-site-plugin:3.20.0:site failed: skin cannot be
null -> [Help 1]
{code}
> java.lang.NoSuchMethodError: 'void
> org.apache.maven.doxia.sink.Sink.verbatim()' updating from 3.24.0 to 3.25.0
> --
>
> Key: MPMD-406
> URL: https://issues.apache.org/jira/browse/MPMD-406
> Project: Maven PMD Plugin
> Issue Type: Bug
>Affects Versions: 3.25.0
> Environment: openjdk version "17.0.12" 2024-07-16
> OpenJDK Runtime Environment Homebrew (build 17.0.12+0)
> OpenJDK 64-Bit Server VM Homebrew (build 17.0.12+0, mixed mode, sharing)
> Apache Maven 3.9.9 (8e8579a9e76f7d015ee5ec7bfcdc97d260186937)
> Maven home: /usr/local/Cellar/maven/3.9.9/libexec
> Java version: 17.0.12, vendor: Homebrew, runtime:
> /usr/local/Cellar/openjdk@17/17.0.12/libexec/openjdk.jdk/Contents/Home
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "14.6.1", arch: "x86_64", family: "mac"
> Darwin 23.6.0 Darwin Kernel Version 23.6.0: Mon Jul 29 21:13:00 PDT
> 2024; root:xnu-10063.141.2~1/RELEASE_X86_64 x86_64
>Reporter: Gary D. Gregory
>Assignee: Michael Osipov
>Priority: Major
> Attachments: screenshot-1.png
>
>
> java.lang.NoSuchMethodError: 'void
> org.apache.maven.doxia.sink.Sink.verbatim()' updating from 3.24.0 to 3.25.0
> {noformat}
> java.lang.NoSuchMethodError: 'void
> org.apache.maven.doxia.sink.Sink.verbatim()'
> at org.apache.maven.reporting.AbstractMavenReportRenderer.verbatimText
> (AbstractMavenReportRenderer.java:363)
> at org.apache.maven.plugins.pmd.CpdReportRenderer.renderDuplications
> (CpdReportRenderer.java:171)
> at org.apache.maven.plugins.pmd.CpdReportRenderer.renderBody
> (CpdReportRenderer.java:96)
> at org.apache.maven.reporting.AbstractMavenReportRenderer.render
> (AbstractMavenReportRenderer.java:93)
> at org.apache.maven.plugins.pmd.CpdReport.executeReport
> (CpdReport.java:140)
> at org.apache.maven.reporting.AbstractMavenReport.generate
> (AbstractMavenReport.java:354)
> at
> org.apache.maven.plugins.site.render.ReportDocumentRenderer.renderDocument
> (ReportDocumentRenderer.java:226)
> at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render
> (DefaultSiteRenderer.java:348)
> at org.apache.maven.plugins.site.render.SiteMojo.renderLocale
> (SiteMojo.java:194)
> at org.apache.maven.plugins.site.render.SiteMojo.execute
> (SiteMojo.java:143)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:126)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:328)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:316)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:174)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
> (MojoExecutor.java:75)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
> (MojoExecutor.java:162)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:159)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:105)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:73)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:53)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:118)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:261)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:173)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:101)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:906)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:283)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:206)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invo
[jira] [Updated] (MNG-8288) Path cannot be null while building reactor modules
[
https://issues.apache.org/jira/browse/MNG-8288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamas Cservenak updated MNG-8288:
-
Description:
Exception trace
{noformat}
org.apache.maven.InternalErrorException: Internal error:
java.lang.IllegalArgumentException: path cannot be null
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:157)
at org.apache.maven.cling.invoker.mvn.DefaultMavenInvoker.doExecute
(DefaultMavenInvoker.java:449)
at org.apache.maven.cli.DaemonMavenInvoker.doExecute
(DaemonMavenInvoker.java:135)
at org.apache.maven.cli.DaemonMavenInvoker.doExecute
(DaemonMavenInvoker.java:39)
at org.apache.maven.cling.invoker.mvn.DefaultMavenInvoker.execute
(DefaultMavenInvoker.java:104)
at org.apache.maven.cling.invoker.mvn.DefaultMavenInvoker.execute
(DefaultMavenInvoker.java:72)
at org.apache.maven.cling.invoker.LookupInvoker.doInvoke
(LookupInvoker.java:202)
at org.apache.maven.cling.invoker.LookupInvoker.invoke
(LookupInvoker.java:177)
at org.apache.maven.cli.DaemonMavenCling.main (DaemonMavenCling.java:76)
at org.mvndaemon.mvnd.daemon.Server.handle (Server.java:616)
at org.mvndaemon.mvnd.daemon.Server.client (Server.java:292)
at org.mvndaemon.mvnd.daemon.Server.lambda$accept$2 (Server.java:254)
at java.lang.Thread.run (Thread.java:1583)
Caused by: java.lang.IllegalArgumentException: path cannot be null
at org.apache.maven.api.services.BaseRequest.nonNull (BaseRequest.java:50)
at org.apache.maven.api.services.ModelSource.fromPath (ModelSource.java:57)
at org.apache.maven.api.services.ModelSource.fromPath (ModelSource.java:52)
at
org.apache.maven.internal.impl.model.DefaultModelBuilder$DefaultModelBuilderSession.doReadFileModel
(DefaultModelBuilder.java:1331)
at
org.apache.maven.internal.impl.model.DefaultModelCache$CachingSupplier.get
(DefaultModelCache.java:178)
at org.apache.maven.internal.impl.model.DefaultModelCache.computeIfAbsent
(DefaultModelCache.java:65)
at org.apache.maven.internal.impl.model.DefaultModelCache.computeIfAbsent
(DefaultModelCache.java:56)
at
org.apache.maven.internal.impl.model.DefaultModelBuilder$DefaultModelBuilderSession.cache
(DefaultModelBuilder.java:1654)
at
org.apache.maven.internal.impl.model.DefaultModelBuilder$DefaultModelBuilderSession.readFileModel
(DefaultModelBuilder.java:1170)
at
org.apache.maven.internal.impl.model.DefaultModelBuilder$DefaultModelBuilderSession.loadFilePom
(DefaultModelBuilder.java:727)
at
org.apache.maven.internal.impl.model.DefaultModelBuilder$DefaultModelBuilderSession.loadFromRoot
(DefaultModelBuilder.java:705)
at
org.apache.maven.internal.impl.model.DefaultModelBuilder$DefaultModelBuilderSession.buildBuildPom
(DefaultModelBuilder.java:652)
at org.apache.maven.internal.impl.model.DefaultModelBuilder$1.build
(DefaultModelBuilder.java:227)
at org.apache.maven.project.DefaultProjectBuilder$BuildSession.build
(DefaultProjectBuilder.java:491)
at
org.apache.maven.project.DefaultProjectBuilder$BuildSession.lambda$doBuild$5
(DefaultProjectBuilder.java:468)
at java.util.stream.ReferencePipeline$3$1.accept
(ReferencePipeline.java:197)
at java.util.Collections$2.tryAdvance (Collections.java:5073)
at java.util.Collections$2.forEachRemaining (Collections.java:5081)
at java.util.stream.AbstractPipeline.copyInto (AbstractPipeline.java:509)
at java.util.stream.AbstractPipeline.wrapAndCopyInto
(AbstractPipeline.java:499)
at java.util.stream.ReduceOps$ReduceOp.evaluateSequential
(ReduceOps.java:921)
at java.util.stream.AbstractPipeline.evaluate (AbstractPipeline.java:234)
at java.util.stream.ReferencePipeline.collect (ReferencePipeline.java:682)
at org.apache.maven.project.DefaultProjectBuilder$BuildSession.doBuild
(DefaultProjectBuilder.java:470)
at org.apache.maven.project.DefaultProjectBuilder$BuildSession.build
(DefaultProjectBuilder.java:444)
at org.apache.maven.project.DefaultProjectBuilder.build
(DefaultProjectBuilder.java:183)
at
org.apache.maven.project.collector.DefaultProjectsSelector.selectProjects
(DefaultProjectsSelector.java:61)
at
org.apache.maven.project.collector.RequestPomCollectionStrategy.collectProjects
(RequestPomCollectionStrategy.java:49)
at org.apache.maven.graph.DefaultGraphBuilder.getProjectsForMavenReactor
(DefaultGraphBuilder.java:364)
at org.apache.maven.graph.DefaultGraphBuilder.build
(DefaultGraphBuilder.java:100)
at org.apache.maven.DefaultMaven.buildGraph (DefaultMaven.java:629)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:250)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:225)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:149)
at org.apache.maven.cling.invoker.mvn.DefaultMavenInvoker.doExecute
(DefaultMavenInvoker.java:449)
at org.apache.maven.cli.DaemonMavenInvok
[jira] [Created] (MNG-8288) Path cannot be null while building reactor modules
Tamas Cservenak created MNG-8288:
Summary: Path cannot be null while building reactor modules
Key: MNG-8288
URL: https://issues.apache.org/jira/browse/MNG-8288
Project: Maven
Issue Type: Bug
Components: Core
Reporter: Tamas Cservenak
Fix For: 4.0.0-beta-5
Exception trace
{noformat}
org.apache.maven.InternalErrorException: Internal error:
java.lang.IllegalArgumentException: path cannot be null
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:157)
at org.apache.maven.cling.invoker.mvn.DefaultMavenInvoker.doExecute
(DefaultMavenInvoker.java:449)
at org.apache.maven.cli.DaemonMavenInvoker.doExecute
(DaemonMavenInvoker.java:135)
at org.apache.maven.cli.DaemonMavenInvoker.doExecute
(DaemonMavenInvoker.java:39)
at org.apache.maven.cling.invoker.mvn.DefaultMavenInvoker.execute
(DefaultMavenInvoker.java:104)
at org.apache.maven.cling.invoker.mvn.DefaultMavenInvoker.execute
(DefaultMavenInvoker.java:72)
at org.apache.maven.cling.invoker.LookupInvoker.doInvoke
(LookupInvoker.java:202)
at org.apache.maven.cling.invoker.LookupInvoker.invoke
(LookupInvoker.java:177)
at org.apache.maven.cli.DaemonMavenCling.main (DaemonMavenCling.java:76)
at org.mvndaemon.mvnd.daemon.Server.handle (Server.java:616)
at org.mvndaemon.mvnd.daemon.Server.client (Server.java:292)
at org.mvndaemon.mvnd.daemon.Server.lambda$accept$2 (Server.java:254)
at java.lang.Thread.run (Thread.java:1583)
Caused by: java.lang.IllegalArgumentException: path cannot be null
at org.apache.maven.api.services.BaseRequest.nonNull (BaseRequest.java:50)
at org.apache.maven.api.services.ModelSource.fromPath (ModelSource.java:57)
at org.apache.maven.api.services.ModelSource.fromPath (ModelSource.java:52)
at
org.apache.maven.internal.impl.model.DefaultModelBuilder$DefaultModelBuilderSession.doReadFileModel
(DefaultModelBuilder.java:1331)
at
org.apache.maven.internal.impl.model.DefaultModelCache$CachingSupplier.get
(DefaultModelCache.java:178)
at org.apache.maven.internal.impl.model.DefaultModelCache.computeIfAbsent
(DefaultModelCache.java:65)
at org.apache.maven.internal.impl.model.DefaultModelCache.computeIfAbsent
(DefaultModelCache.java:56)
at
org.apache.maven.internal.impl.model.DefaultModelBuilder$DefaultModelBuilderSession.cache
(DefaultModelBuilder.java:1654)
at
org.apache.maven.internal.impl.model.DefaultModelBuilder$DefaultModelBuilderSession.readFileModel
(DefaultModelBuilder.java:1170)
at
org.apache.maven.internal.impl.model.DefaultModelBuilder$DefaultModelBuilderSession.loadFilePom
(DefaultModelBuilder.java:727)
at
org.apache.maven.internal.impl.model.DefaultModelBuilder$DefaultModelBuilderSession.loadFromRoot
(DefaultModelBuilder.java:705)
at
org.apache.maven.internal.impl.model.DefaultModelBuilder$DefaultModelBuilderSession.buildBuildPom
(DefaultModelBuilder.java:652)
at org.apache.maven.internal.impl.model.DefaultModelBuilder$1.build
(DefaultModelBuilder.java:227)
at org.apache.maven.project.DefaultProjectBuilder$BuildSession.build
(DefaultProjectBuilder.java:491)
at
org.apache.maven.project.DefaultProjectBuilder$BuildSession.lambda$doBuild$5
(DefaultProjectBuilder.java:468)
at java.util.stream.ReferencePipeline$3$1.accept
(ReferencePipeline.java:197)
at java.util.Collections$2.tryAdvance (Collections.java:5073)
at java.util.Collections$2.forEachRemaining (Collections.java:5081)
at java.util.stream.AbstractPipeline.copyInto (AbstractPipeline.java:509)
at java.util.stream.AbstractPipeline.wrapAndCopyInto
(AbstractPipeline.java:499)
at java.util.stream.ReduceOps$ReduceOp.evaluateSequential
(ReduceOps.java:921)
at java.util.stream.AbstractPipeline.evaluate (AbstractPipeline.java:234)
at java.util.stream.ReferencePipeline.collect (ReferencePipeline.java:682)
at org.apache.maven.project.DefaultProjectBuilder$BuildSession.doBuild
(DefaultProjectBuilder.java:470)
at org.apache.maven.project.DefaultProjectBuilder$BuildSession.build
(DefaultProjectBuilder.java:444)
at org.apache.maven.project.DefaultProjectBuilder.build
(DefaultProjectBuilder.java:183)
at
org.apache.maven.project.collector.DefaultProjectsSelector.selectProjects
(DefaultProjectsSelector.java:61)
at
org.apache.maven.project.collector.RequestPomCollectionStrategy.collectProjects
(RequestPomCollectionStrategy.java:49)
at org.apache.maven.graph.DefaultGraphBuilder.getProjectsForMavenReactor
(DefaultGraphBuilder.java:364)
at org.apache.maven.graph.DefaultGraphBuilder.build
(DefaultGraphBuilder.java:100)
at org.apache.maven.DefaultMaven.buildGraph (DefaultMaven.java:629)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:250)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:225)
at org.apache.maven.Defau
[jira] [Commented] (MPMD-406) java.lang.NoSuchMethodError: 'void org.apache.maven.doxia.sink.Sink.verbatim()' updating from 3.24.0 to 3.25.0
[
https://issues.apache.org/jira/browse/MPMD-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17887122#comment-17887122
]
Michael Osipov commented on MPMD-406:
-
Regarding skins:
* General skin descriptor:
https://maven.apache.org/doxia/doxia-sitetools/doxia-skin-model/
* Regarding the Commons Skin: COMMONSSITE-165
You can constrain your to a specific Doxia Sitetools version if you know that
it does not work with others. This is what we did with our skins.
The behavior you see is correct:
https://cwiki.apache.org/confluence/display/MAVEN/Towards+Doxia+2.0.0+Stack#TowardsDoxia2.0.0Stack-DoxiaSitetools2.0.0.
A skin now is always required.
> java.lang.NoSuchMethodError: 'void
> org.apache.maven.doxia.sink.Sink.verbatim()' updating from 3.24.0 to 3.25.0
> --
>
> Key: MPMD-406
> URL: https://issues.apache.org/jira/browse/MPMD-406
> Project: Maven PMD Plugin
> Issue Type: Bug
>Affects Versions: 3.25.0
> Environment: openjdk version "17.0.12" 2024-07-16
> OpenJDK Runtime Environment Homebrew (build 17.0.12+0)
> OpenJDK 64-Bit Server VM Homebrew (build 17.0.12+0, mixed mode, sharing)
> Apache Maven 3.9.9 (8e8579a9e76f7d015ee5ec7bfcdc97d260186937)
> Maven home: /usr/local/Cellar/maven/3.9.9/libexec
> Java version: 17.0.12, vendor: Homebrew, runtime:
> /usr/local/Cellar/openjdk@17/17.0.12/libexec/openjdk.jdk/Contents/Home
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "14.6.1", arch: "x86_64", family: "mac"
> Darwin 23.6.0 Darwin Kernel Version 23.6.0: Mon Jul 29 21:13:00 PDT
> 2024; root:xnu-10063.141.2~1/RELEASE_X86_64 x86_64
>Reporter: Gary D. Gregory
>Assignee: Michael Osipov
>Priority: Major
> Attachments: screenshot-1.png
>
>
> java.lang.NoSuchMethodError: 'void
> org.apache.maven.doxia.sink.Sink.verbatim()' updating from 3.24.0 to 3.25.0
> {noformat}
> java.lang.NoSuchMethodError: 'void
> org.apache.maven.doxia.sink.Sink.verbatim()'
> at org.apache.maven.reporting.AbstractMavenReportRenderer.verbatimText
> (AbstractMavenReportRenderer.java:363)
> at org.apache.maven.plugins.pmd.CpdReportRenderer.renderDuplications
> (CpdReportRenderer.java:171)
> at org.apache.maven.plugins.pmd.CpdReportRenderer.renderBody
> (CpdReportRenderer.java:96)
> at org.apache.maven.reporting.AbstractMavenReportRenderer.render
> (AbstractMavenReportRenderer.java:93)
> at org.apache.maven.plugins.pmd.CpdReport.executeReport
> (CpdReport.java:140)
> at org.apache.maven.reporting.AbstractMavenReport.generate
> (AbstractMavenReport.java:354)
> at
> org.apache.maven.plugins.site.render.ReportDocumentRenderer.renderDocument
> (ReportDocumentRenderer.java:226)
> at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render
> (DefaultSiteRenderer.java:348)
> at org.apache.maven.plugins.site.render.SiteMojo.renderLocale
> (SiteMojo.java:194)
> at org.apache.maven.plugins.site.render.SiteMojo.execute
> (SiteMojo.java:143)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:126)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:328)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:316)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:174)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
> (MojoExecutor.java:75)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
> (MojoExecutor.java:162)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:159)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:105)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:73)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:53)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:118)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:261)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:173)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:101)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:906)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:283)
> at org.apache.maven.cli.MavenCli.main (
[jira] [Commented] (MPMD-406) java.lang.NoSuchMethodError: 'void org.apache.maven.doxia.sink.Sink.verbatim()' updating from 3.24.0 to 3.25.0
[
https://issues.apache.org/jira/browse/MPMD-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17887124#comment-17887124
]
Michael Osipov commented on MPMD-406:
-
FYI: I have changed https://maven.apache.org/skins/index.html now.
> java.lang.NoSuchMethodError: 'void
> org.apache.maven.doxia.sink.Sink.verbatim()' updating from 3.24.0 to 3.25.0
> --
>
> Key: MPMD-406
> URL: https://issues.apache.org/jira/browse/MPMD-406
> Project: Maven PMD Plugin
> Issue Type: Bug
>Affects Versions: 3.25.0
> Environment: openjdk version "17.0.12" 2024-07-16
> OpenJDK Runtime Environment Homebrew (build 17.0.12+0)
> OpenJDK 64-Bit Server VM Homebrew (build 17.0.12+0, mixed mode, sharing)
> Apache Maven 3.9.9 (8e8579a9e76f7d015ee5ec7bfcdc97d260186937)
> Maven home: /usr/local/Cellar/maven/3.9.9/libexec
> Java version: 17.0.12, vendor: Homebrew, runtime:
> /usr/local/Cellar/openjdk@17/17.0.12/libexec/openjdk.jdk/Contents/Home
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "14.6.1", arch: "x86_64", family: "mac"
> Darwin 23.6.0 Darwin Kernel Version 23.6.0: Mon Jul 29 21:13:00 PDT
> 2024; root:xnu-10063.141.2~1/RELEASE_X86_64 x86_64
>Reporter: Gary D. Gregory
>Assignee: Michael Osipov
>Priority: Major
> Attachments: screenshot-1.png
>
>
> java.lang.NoSuchMethodError: 'void
> org.apache.maven.doxia.sink.Sink.verbatim()' updating from 3.24.0 to 3.25.0
> {noformat}
> java.lang.NoSuchMethodError: 'void
> org.apache.maven.doxia.sink.Sink.verbatim()'
> at org.apache.maven.reporting.AbstractMavenReportRenderer.verbatimText
> (AbstractMavenReportRenderer.java:363)
> at org.apache.maven.plugins.pmd.CpdReportRenderer.renderDuplications
> (CpdReportRenderer.java:171)
> at org.apache.maven.plugins.pmd.CpdReportRenderer.renderBody
> (CpdReportRenderer.java:96)
> at org.apache.maven.reporting.AbstractMavenReportRenderer.render
> (AbstractMavenReportRenderer.java:93)
> at org.apache.maven.plugins.pmd.CpdReport.executeReport
> (CpdReport.java:140)
> at org.apache.maven.reporting.AbstractMavenReport.generate
> (AbstractMavenReport.java:354)
> at
> org.apache.maven.plugins.site.render.ReportDocumentRenderer.renderDocument
> (ReportDocumentRenderer.java:226)
> at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render
> (DefaultSiteRenderer.java:348)
> at org.apache.maven.plugins.site.render.SiteMojo.renderLocale
> (SiteMojo.java:194)
> at org.apache.maven.plugins.site.render.SiteMojo.execute
> (SiteMojo.java:143)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:126)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:328)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:316)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:174)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
> (MojoExecutor.java:75)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
> (MojoExecutor.java:162)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:159)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:105)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:73)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:53)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:118)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:261)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:173)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:101)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:906)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:283)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:206)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:77)
> at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:569)
> at org.codehaus.plexus.classworlds.launcher.Launch
[jira] [Commented] (MCHANGES-412) Allow an action to carry an optional scope
[
https://issues.apache.org/jira/browse/MCHANGES-412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17887107#comment-17887107
]
Gary D. Gregory commented on MCHANGES-412:
--
Ping?
> Allow an action to carry an optional scope
> --
>
> Key: MCHANGES-412
> URL: https://issues.apache.org/jira/browse/MCHANGES-412
> Project: Maven Changes Plugin
> Issue Type: New Feature
> Components: changes.xml
>Reporter: Gary D. Gregory
>Priority: Major
>
> In changes.xml, I would like an *action* to carry an optional {*}scope{*}.
> This would help users understand what changes affect which part of their
> projects.
> For example:
> Fix some bug
> Bump dependency foo
> from 1 to 2
> Bump commons-parent
> foo from 1 to 2
> The use of the scope documents where the change applies, usually runtime,
> test, or build, but it could be string maybe.
> This somewhat parallels the concept of a scope in a dependency so the value
> set could be the same as allowed for a dependency scope but that might be too
> restrictive.
> Thoughts?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (ARCHETYPE-681) [REGRESSION] Output from archetype verification is no longer logged
[
https://issues.apache.org/jira/browse/ARCHETYPE-681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Slawomir Jaranowski reassigned ARCHETYPE-681:
-
Assignee: Slawomir Jaranowski
> [REGRESSION] Output from archetype verification is no longer logged
> ---
>
> Key: ARCHETYPE-681
> URL: https://issues.apache.org/jira/browse/ARCHETYPE-681
> Project: Maven Archetype
> Issue Type: Bug
>Affects Versions: 3.3.0
>Reporter: Wolfgang Knauf
>Assignee: Slawomir Jaranowski
>Priority: Major
>
> When build an archetype project, there is a step the generates a sample
> project from the archetype.
>
> With 3.1.2, the maven output to create and build a sample project from the
> archetype was logged (see duplicated "[INFO] [INFO]" lines):
>
> {{[INFO] Project created from Archetype in dir:
> C:\Temp\github\wildfly-archetypes\wildfly-jakartaee-webapp-archetype\target\test-classes\projects\multi\project\multi}}
> {{[INFO] Invoking post-archetype-generation goals: verify}}
> {{[INFO] [INFO] Error stacktraces are turned on.}}
> {{[INFO] [INFO] Scanning for projects...}}
> {{[INFO] [INFO]}}
> {{[INFO] [INFO] -{-}{{-}}< foo.bar:multi
> >{{-}}{-}--}}
> {{[INFO] [INFO] Building multi 0.0.1-SNAPSHOT}}
> {{[INFO] [INFO] from pom.xml}}
> {{...}}
>
> With 3.3.0, there is just this output:
> {{[INFO] Project created from Archetype in dir:
> C:\Temp\github\wildfly-archetypes\wildfly-jakartaee-webapp-archetype\target\test-classes\projects\multi\project\multi}}
> {{[INFO] Invoking post-archetype-generation goals: verify}}
> {{[INFO] Post-archetype-generation invoker exit code: 0}}
> {{...}}
>
> This is not good, as building the sample project might take a long time, or
> might even fail, and you don't see a reason for the long delay after the line
> "Invoking post-archetype-generation goals: verify" is printed. I had also a
> situation where creating and building the sample project failed, and here not
> details about the error were logged.
> Could you bring back the old behavior to log the INFO output?
>
> To reproduce: you could pull the wildfly archetypes:
> [https://github.com/wildfly/wildfly-archetypes]
> At the end of the root pom.xml, change the archetype version to "3.3.0" - we
> are currently stuck with 3.1.2 due to another issue.
> Then build one of the archetype modules (invoke it in the root directory -
> building all archetypes will not work, as one has additional requirements):
> {{mvn -pl wildfly-jakartaee-webapp-archetype clean install}}
>
> Or is there a configuration option to enable logging again?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (ARCHETYPE-681) [REGRESSION] Output from archetype verification is no longer logged
[
https://issues.apache.org/jira/browse/ARCHETYPE-681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Slawomir Jaranowski updated ARCHETYPE-681:
--
Fix Version/s: 3.3.1
> [REGRESSION] Output from archetype verification is no longer logged
> ---
>
> Key: ARCHETYPE-681
> URL: https://issues.apache.org/jira/browse/ARCHETYPE-681
> Project: Maven Archetype
> Issue Type: Bug
>Affects Versions: 3.3.0
>Reporter: Wolfgang Knauf
>Assignee: Slawomir Jaranowski
>Priority: Major
> Fix For: 3.3.1
>
>
> When build an archetype project, there is a step the generates a sample
> project from the archetype.
>
> With 3.1.2, the maven output to create and build a sample project from the
> archetype was logged (see duplicated "[INFO] [INFO]" lines):
>
> {{[INFO] Project created from Archetype in dir:
> C:\Temp\github\wildfly-archetypes\wildfly-jakartaee-webapp-archetype\target\test-classes\projects\multi\project\multi}}
> {{[INFO] Invoking post-archetype-generation goals: verify}}
> {{[INFO] [INFO] Error stacktraces are turned on.}}
> {{[INFO] [INFO] Scanning for projects...}}
> {{[INFO] [INFO]}}
> {{[INFO] [INFO] -{-}{{-}}< foo.bar:multi
> >{{-}}{-}--}}
> {{[INFO] [INFO] Building multi 0.0.1-SNAPSHOT}}
> {{[INFO] [INFO] from pom.xml}}
> {{...}}
>
> With 3.3.0, there is just this output:
> {{[INFO] Project created from Archetype in dir:
> C:\Temp\github\wildfly-archetypes\wildfly-jakartaee-webapp-archetype\target\test-classes\projects\multi\project\multi}}
> {{[INFO] Invoking post-archetype-generation goals: verify}}
> {{[INFO] Post-archetype-generation invoker exit code: 0}}
> {{...}}
>
> This is not good, as building the sample project might take a long time, or
> might even fail, and you don't see a reason for the long delay after the line
> "Invoking post-archetype-generation goals: verify" is printed. I had also a
> situation where creating and building the sample project failed, and here not
> details about the error were logged.
> Could you bring back the old behavior to log the INFO output?
>
> To reproduce: you could pull the wildfly archetypes:
> [https://github.com/wildfly/wildfly-archetypes]
> At the end of the root pom.xml, change the archetype version to "3.3.0" - we
> are currently stuck with 3.1.2 due to another issue.
> Then build one of the archetype modules (invoke it in the root directory -
> building all archetypes will not work, as one has additional requirements):
> {{mvn -pl wildfly-jakartaee-webapp-archetype clean install}}
>
> Or is there a configuration option to enable logging again?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (ARCHETYPE-683) [REGRESSION] groovy.json.JsonOutput not found
[
https://issues.apache.org/jira/browse/ARCHETYPE-683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Slawomir Jaranowski closed ARCHETYPE-683.
-
Resolution: Fixed
> [REGRESSION] groovy.json.JsonOutput not found
> -
>
> Key: ARCHETYPE-683
> URL: https://issues.apache.org/jira/browse/ARCHETYPE-683
> Project: Maven Archetype
> Issue Type: Bug
> Components: Archetypes, Generator
>Affects Versions: 3.3.0
>Reporter: Dirk Rosemann
>Assignee: Slawomir Jaranowski
>Priority: Major
> Fix For: 3.3.1
>
>
> I use groovy.json.JsonOutput in partial archetype's
> archetype-post-generate.groovy, first line of my code is "import
> groovy.json.JsonOutput".
> Since archetype v3.3.0 I receive the following error on archetype:generate
> goal execution:
>
> {noformat}
> Failed to execute goal
> org.apache.maven.plugins:maven-archetype-plugin:3.3.0:generate (default-cli)
> {...}
> Script1.groovy: 1: unable to resolve class groovy.json.JsonOutput
> @ line 1, column 1.
> import groovy.json.JsonOutput
> ^
> 1 error{noformat}
> Workaround is to force usage of v3.2.1 version when using partial archetype,
> like so:
>
> {code:java}
>
>
>
> org.apache.maven.plugins
> maven-archetype-plugin
> 3.2.1
>
>
> {code}
> This issue seems to be related to
> https://issues.apache.org/jira/browse/ARCHETYPE-679.
> Please let me know if you need any additional information.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (ARCHETYPE-685) Fix namespace in modello models
[ https://issues.apache.org/jira/browse/ARCHETYPE-685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Slawomir Jaranowski closed ARCHETYPE-685. - Resolution: Fixed > Fix namespace in modello models > > > Key: ARCHETYPE-685 > URL: https://issues.apache.org/jira/browse/ARCHETYPE-685 > Project: Maven Archetype > Issue Type: Bug >Affects Versions: 3.3.0 >Reporter: Slawomir Jaranowski >Assignee: Slawomir Jaranowski >Priority: Major > Fix For: 3.3.1 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (ARCHETYPE-684) Not providing a directory element in the fileset results in a null directory instead
[
https://issues.apache.org/jira/browse/ARCHETYPE-684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Slawomir Jaranowski reassigned ARCHETYPE-684:
-
Assignee: Slawomir Jaranowski
> Not providing a directory element in the fileset results in a null directory
> instead
>
>
> Key: ARCHETYPE-684
> URL: https://issues.apache.org/jira/browse/ARCHETYPE-684
> Project: Maven Archetype
> Issue Type: Bug
> Components: Generator
>Affects Versions: 3.2.1, 3.3.0
>Reporter: Giovanni van der Schelde
>Assignee: Slawomir Jaranowski
>Priority: Major
> Attachments: reproducer.zip
>
>
> When you have a directory structure like:
> {code:java}
> src/
> main/resources/
>src/
>example.yml{code}
> And a fileSet in the archetype-descriptor like:
> {code:java}
>
>
>
> *.yml
>
> {code}
> When you generate the archetype you won't get the .yml files, but instead you
> get an empty directory with the name `null`.
> When you explicitly provide the element, the `null` directory
> disappears and the .yml file is copied.
> I think it would make sense to either;
> a) Log an error or warning that the xml is incomplete
> b) When no directory is provided, use a default (of the root directory)
> instead
> Where option B makes to most sense to me.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (ARCHETYPE-684) Not providing a directory element in the fileset results in a null directory instead
[
https://issues.apache.org/jira/browse/ARCHETYPE-684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Slawomir Jaranowski updated ARCHETYPE-684:
--
Fix Version/s: 3.3.1
> Not providing a directory element in the fileset results in a null directory
> instead
>
>
> Key: ARCHETYPE-684
> URL: https://issues.apache.org/jira/browse/ARCHETYPE-684
> Project: Maven Archetype
> Issue Type: Bug
> Components: Generator
>Affects Versions: 3.2.1, 3.3.0
>Reporter: Giovanni van der Schelde
>Assignee: Slawomir Jaranowski
>Priority: Major
> Fix For: 3.3.1
>
> Attachments: reproducer.zip
>
>
> When you have a directory structure like:
> {code:java}
> src/
> main/resources/
>src/
>example.yml{code}
> And a fileSet in the archetype-descriptor like:
> {code:java}
>
>
>
> *.yml
>
> {code}
> When you generate the archetype you won't get the .yml files, but instead you
> get an empty directory with the name `null`.
> When you explicitly provide the element, the `null` directory
> disappears and the .yml file is copied.
> I think it would make sense to either;
> a) Log an error or warning that the xml is incomplete
> b) When no directory is provided, use a default (of the root directory)
> instead
> Where option B makes to most sense to me.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ARCHETYPE-679) groovy.text.SimpleTemplateEngine Not Found
[
https://issues.apache.org/jira/browse/ARCHETYPE-679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17887103#comment-17887103
]
Slawomir Jaranowski commented on ARCHETYPE-679:
---
Afetr https://github.com/apache/maven-archetype/pull/226
we will have:
- groovy-json
- groovy-templates
- groovy-xml
- groovy-yaml
If something else are interesting please let me know
> groovy.text.SimpleTemplateEngine Not Found
> --
>
> Key: ARCHETYPE-679
> URL: https://issues.apache.org/jira/browse/ARCHETYPE-679
> Project: Maven Archetype
> Issue Type: Bug
> Components: Archetypes
>Affects Versions: 3.3.0
>Reporter: Reza Rahman
>Assignee: Slawomir Jaranowski
>Priority: Major
> Fix For: 3.3.1
>
>
> I am posting this issue on behalf of the official Jakarta EE Starter project
> at the Eclipse Foundation:
> [https://start.jakarta.ee|https://start.jakarta.ee/]. We make use of Maven
> Archetypes in the Starter under the hood and also as an API:
> [https://github.com/eclipse-ee4j/starter/tree/master/archetype.]
> We are pretty dependent on Groovy and use groovy.text.SimpleTemplateEngine
> for some critical functionality:
> [https://github.com/eclipse-ee4j/starter/blob/ca9b5028b7fe3b47ecf4b5e5c22e89bc941e99a0/archetype/src/main/resources/META-INF/archetype-post-generate.groovy#L144].
>
> A few days ago we noticed that the Archetype is suddenly broken with the
> following error:
> {{[ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-archetype-plugin:3.3.0:generate (default-cli)
> on project standalone-pom: startup failed:}}
> {{[ERROR] Script1.groovy: 144: unable to resolve class
> groovy.text.SimpleTemplateEngine}}
> {{[ERROR] @ line 144, column 18.}}
> {{[ERROR] def engine = new groovy.text.SimpleTemplateEngine()}}
> {{[ERROR] ^}}
> {{[ERROR]}}
> {{[ERROR] 1 error}}
> This seems to coincide with the 3.3.0 release of maven-archetype-plugin. Any
> idea what is going on and how to fix this?
> Please LMK if you need anything from us?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (ARCHETYPE-686) Bump org.apache.velocity:velocity-engine-core from 2.3 to 2.4
Slawomir Jaranowski created ARCHETYPE-686: - Summary: Bump org.apache.velocity:velocity-engine-core from 2.3 to 2.4 Key: ARCHETYPE-686 URL: https://issues.apache.org/jira/browse/ARCHETYPE-686 Project: Maven Archetype Issue Type: Dependency upgrade Reporter: Slawomir Jaranowski Assignee: Slawomir Jaranowski Fix For: 3.3.1 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MPMD-406) java.lang.NoSuchMethodError: 'void org.apache.maven.doxia.sink.Sink.verbatim()' updating from 3.24.0 to 3.25.0
[
https://issues.apache.org/jira/browse/MPMD-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17887110#comment-17887110
]
Michael Osipov commented on MPMD-406:
-
The Default Skin is gone. It has been removed since is has not been maintained
for 10+ years. There is an open issue to officially deprecate it. Try the
fluido skin. In some Commons issue I have expressed many years ago that the
Commons Skin needs updates from the latest Fluido first.
> java.lang.NoSuchMethodError: 'void
> org.apache.maven.doxia.sink.Sink.verbatim()' updating from 3.24.0 to 3.25.0
> --
>
> Key: MPMD-406
> URL: https://issues.apache.org/jira/browse/MPMD-406
> Project: Maven PMD Plugin
> Issue Type: Bug
>Affects Versions: 3.25.0
> Environment: openjdk version "17.0.12" 2024-07-16
> OpenJDK Runtime Environment Homebrew (build 17.0.12+0)
> OpenJDK 64-Bit Server VM Homebrew (build 17.0.12+0, mixed mode, sharing)
> Apache Maven 3.9.9 (8e8579a9e76f7d015ee5ec7bfcdc97d260186937)
> Maven home: /usr/local/Cellar/maven/3.9.9/libexec
> Java version: 17.0.12, vendor: Homebrew, runtime:
> /usr/local/Cellar/openjdk@17/17.0.12/libexec/openjdk.jdk/Contents/Home
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "14.6.1", arch: "x86_64", family: "mac"
> Darwin 23.6.0 Darwin Kernel Version 23.6.0: Mon Jul 29 21:13:00 PDT
> 2024; root:xnu-10063.141.2~1/RELEASE_X86_64 x86_64
>Reporter: Gary D. Gregory
>Assignee: Michael Osipov
>Priority: Major
>
> java.lang.NoSuchMethodError: 'void
> org.apache.maven.doxia.sink.Sink.verbatim()' updating from 3.24.0 to 3.25.0
> {noformat}
> java.lang.NoSuchMethodError: 'void
> org.apache.maven.doxia.sink.Sink.verbatim()'
> at org.apache.maven.reporting.AbstractMavenReportRenderer.verbatimText
> (AbstractMavenReportRenderer.java:363)
> at org.apache.maven.plugins.pmd.CpdReportRenderer.renderDuplications
> (CpdReportRenderer.java:171)
> at org.apache.maven.plugins.pmd.CpdReportRenderer.renderBody
> (CpdReportRenderer.java:96)
> at org.apache.maven.reporting.AbstractMavenReportRenderer.render
> (AbstractMavenReportRenderer.java:93)
> at org.apache.maven.plugins.pmd.CpdReport.executeReport
> (CpdReport.java:140)
> at org.apache.maven.reporting.AbstractMavenReport.generate
> (AbstractMavenReport.java:354)
> at
> org.apache.maven.plugins.site.render.ReportDocumentRenderer.renderDocument
> (ReportDocumentRenderer.java:226)
> at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render
> (DefaultSiteRenderer.java:348)
> at org.apache.maven.plugins.site.render.SiteMojo.renderLocale
> (SiteMojo.java:194)
> at org.apache.maven.plugins.site.render.SiteMojo.execute
> (SiteMojo.java:143)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:126)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:328)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:316)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:174)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
> (MojoExecutor.java:75)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
> (MojoExecutor.java:162)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:159)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:105)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:73)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:53)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:118)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:261)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:173)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:101)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:906)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:283)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:206)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:77)
> at jdk.internal.reflect.DelegatingMe
[jira] [Closed] (ARCHETYPE-679) groovy.text.SimpleTemplateEngine Not Found
[
https://issues.apache.org/jira/browse/ARCHETYPE-679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Slawomir Jaranowski closed ARCHETYPE-679.
-
Resolution: Fixed
> groovy.text.SimpleTemplateEngine Not Found
> --
>
> Key: ARCHETYPE-679
> URL: https://issues.apache.org/jira/browse/ARCHETYPE-679
> Project: Maven Archetype
> Issue Type: Bug
> Components: Archetypes
>Affects Versions: 3.3.0
>Reporter: Reza Rahman
>Assignee: Slawomir Jaranowski
>Priority: Major
> Fix For: 3.3.1
>
>
> I am posting this issue on behalf of the official Jakarta EE Starter project
> at the Eclipse Foundation:
> [https://start.jakarta.ee|https://start.jakarta.ee/]. We make use of Maven
> Archetypes in the Starter under the hood and also as an API:
> [https://github.com/eclipse-ee4j/starter/tree/master/archetype.]
> We are pretty dependent on Groovy and use groovy.text.SimpleTemplateEngine
> for some critical functionality:
> [https://github.com/eclipse-ee4j/starter/blob/ca9b5028b7fe3b47ecf4b5e5c22e89bc941e99a0/archetype/src/main/resources/META-INF/archetype-post-generate.groovy#L144].
>
> A few days ago we noticed that the Archetype is suddenly broken with the
> following error:
> {{[ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-archetype-plugin:3.3.0:generate (default-cli)
> on project standalone-pom: startup failed:}}
> {{[ERROR] Script1.groovy: 144: unable to resolve class
> groovy.text.SimpleTemplateEngine}}
> {{[ERROR] @ line 144, column 18.}}
> {{[ERROR] def engine = new groovy.text.SimpleTemplateEngine()}}
> {{[ERROR] ^}}
> {{[ERROR]}}
> {{[ERROR] 1 error}}
> This seems to coincide with the 3.3.0 release of maven-archetype-plugin. Any
> idea what is going on and how to fix this?
> Please LMK if you need anything from us?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MPMD-406) java.lang.NoSuchMethodError: 'void org.apache.maven.doxia.sink.Sink.verbatim()' updating from 3.24.0 to 3.25.0
[
https://issues.apache.org/jira/browse/MPMD-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17887128#comment-17887128
]
Gary D. Gregory commented on MPMD-406:
--
Thank you [~michael-o]
I'll work through this info today.
Thank you for updating the site. Note that the links to GitBox are 404s.
> java.lang.NoSuchMethodError: 'void
> org.apache.maven.doxia.sink.Sink.verbatim()' updating from 3.24.0 to 3.25.0
> --
>
> Key: MPMD-406
> URL: https://issues.apache.org/jira/browse/MPMD-406
> Project: Maven PMD Plugin
> Issue Type: Bug
>Affects Versions: 3.25.0
> Environment: openjdk version "17.0.12" 2024-07-16
> OpenJDK Runtime Environment Homebrew (build 17.0.12+0)
> OpenJDK 64-Bit Server VM Homebrew (build 17.0.12+0, mixed mode, sharing)
> Apache Maven 3.9.9 (8e8579a9e76f7d015ee5ec7bfcdc97d260186937)
> Maven home: /usr/local/Cellar/maven/3.9.9/libexec
> Java version: 17.0.12, vendor: Homebrew, runtime:
> /usr/local/Cellar/openjdk@17/17.0.12/libexec/openjdk.jdk/Contents/Home
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "14.6.1", arch: "x86_64", family: "mac"
> Darwin 23.6.0 Darwin Kernel Version 23.6.0: Mon Jul 29 21:13:00 PDT
> 2024; root:xnu-10063.141.2~1/RELEASE_X86_64 x86_64
>Reporter: Gary D. Gregory
>Assignee: Michael Osipov
>Priority: Major
> Attachments: screenshot-1.png
>
>
> java.lang.NoSuchMethodError: 'void
> org.apache.maven.doxia.sink.Sink.verbatim()' updating from 3.24.0 to 3.25.0
> {noformat}
> java.lang.NoSuchMethodError: 'void
> org.apache.maven.doxia.sink.Sink.verbatim()'
> at org.apache.maven.reporting.AbstractMavenReportRenderer.verbatimText
> (AbstractMavenReportRenderer.java:363)
> at org.apache.maven.plugins.pmd.CpdReportRenderer.renderDuplications
> (CpdReportRenderer.java:171)
> at org.apache.maven.plugins.pmd.CpdReportRenderer.renderBody
> (CpdReportRenderer.java:96)
> at org.apache.maven.reporting.AbstractMavenReportRenderer.render
> (AbstractMavenReportRenderer.java:93)
> at org.apache.maven.plugins.pmd.CpdReport.executeReport
> (CpdReport.java:140)
> at org.apache.maven.reporting.AbstractMavenReport.generate
> (AbstractMavenReport.java:354)
> at
> org.apache.maven.plugins.site.render.ReportDocumentRenderer.renderDocument
> (ReportDocumentRenderer.java:226)
> at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render
> (DefaultSiteRenderer.java:348)
> at org.apache.maven.plugins.site.render.SiteMojo.renderLocale
> (SiteMojo.java:194)
> at org.apache.maven.plugins.site.render.SiteMojo.execute
> (SiteMojo.java:143)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:126)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:328)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:316)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:174)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
> (MojoExecutor.java:75)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
> (MojoExecutor.java:162)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:159)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:105)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:73)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:53)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:118)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:261)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:173)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:101)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:906)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:283)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:206)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:77)
> at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Meth
[jira] [Commented] (MPMD-406) java.lang.NoSuchMethodError: 'void org.apache.maven.doxia.sink.Sink.verbatim()' updating from 3.24.0 to 3.25.0
[
https://issues.apache.org/jira/browse/MPMD-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17887129#comment-17887129
]
Michael Osipov commented on MPMD-406:
-
Indeed! Will fix, thanks!
> java.lang.NoSuchMethodError: 'void
> org.apache.maven.doxia.sink.Sink.verbatim()' updating from 3.24.0 to 3.25.0
> --
>
> Key: MPMD-406
> URL: https://issues.apache.org/jira/browse/MPMD-406
> Project: Maven PMD Plugin
> Issue Type: Bug
>Affects Versions: 3.25.0
> Environment: openjdk version "17.0.12" 2024-07-16
> OpenJDK Runtime Environment Homebrew (build 17.0.12+0)
> OpenJDK 64-Bit Server VM Homebrew (build 17.0.12+0, mixed mode, sharing)
> Apache Maven 3.9.9 (8e8579a9e76f7d015ee5ec7bfcdc97d260186937)
> Maven home: /usr/local/Cellar/maven/3.9.9/libexec
> Java version: 17.0.12, vendor: Homebrew, runtime:
> /usr/local/Cellar/openjdk@17/17.0.12/libexec/openjdk.jdk/Contents/Home
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "14.6.1", arch: "x86_64", family: "mac"
> Darwin 23.6.0 Darwin Kernel Version 23.6.0: Mon Jul 29 21:13:00 PDT
> 2024; root:xnu-10063.141.2~1/RELEASE_X86_64 x86_64
>Reporter: Gary D. Gregory
>Assignee: Michael Osipov
>Priority: Major
> Attachments: screenshot-1.png
>
>
> java.lang.NoSuchMethodError: 'void
> org.apache.maven.doxia.sink.Sink.verbatim()' updating from 3.24.0 to 3.25.0
> {noformat}
> java.lang.NoSuchMethodError: 'void
> org.apache.maven.doxia.sink.Sink.verbatim()'
> at org.apache.maven.reporting.AbstractMavenReportRenderer.verbatimText
> (AbstractMavenReportRenderer.java:363)
> at org.apache.maven.plugins.pmd.CpdReportRenderer.renderDuplications
> (CpdReportRenderer.java:171)
> at org.apache.maven.plugins.pmd.CpdReportRenderer.renderBody
> (CpdReportRenderer.java:96)
> at org.apache.maven.reporting.AbstractMavenReportRenderer.render
> (AbstractMavenReportRenderer.java:93)
> at org.apache.maven.plugins.pmd.CpdReport.executeReport
> (CpdReport.java:140)
> at org.apache.maven.reporting.AbstractMavenReport.generate
> (AbstractMavenReport.java:354)
> at
> org.apache.maven.plugins.site.render.ReportDocumentRenderer.renderDocument
> (ReportDocumentRenderer.java:226)
> at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render
> (DefaultSiteRenderer.java:348)
> at org.apache.maven.plugins.site.render.SiteMojo.renderLocale
> (SiteMojo.java:194)
> at org.apache.maven.plugins.site.render.SiteMojo.execute
> (SiteMojo.java:143)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:126)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:328)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:316)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:174)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
> (MojoExecutor.java:75)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
> (MojoExecutor.java:162)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:159)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:105)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:73)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:53)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:118)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:261)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:173)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:101)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:906)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:283)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:206)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:77)
> at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:569)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:255)
[jira] [Commented] (MPMD-406) java.lang.NoSuchMethodError: 'void org.apache.maven.doxia.sink.Sink.verbatim()' updating from 3.24.0 to 3.25.0
[
https://issues.apache.org/jira/browse/MPMD-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17887130#comment-17887130
]
Michael Osipov commented on MPMD-406:
-
Links fixed.
> java.lang.NoSuchMethodError: 'void
> org.apache.maven.doxia.sink.Sink.verbatim()' updating from 3.24.0 to 3.25.0
> --
>
> Key: MPMD-406
> URL: https://issues.apache.org/jira/browse/MPMD-406
> Project: Maven PMD Plugin
> Issue Type: Bug
>Affects Versions: 3.25.0
> Environment: openjdk version "17.0.12" 2024-07-16
> OpenJDK Runtime Environment Homebrew (build 17.0.12+0)
> OpenJDK 64-Bit Server VM Homebrew (build 17.0.12+0, mixed mode, sharing)
> Apache Maven 3.9.9 (8e8579a9e76f7d015ee5ec7bfcdc97d260186937)
> Maven home: /usr/local/Cellar/maven/3.9.9/libexec
> Java version: 17.0.12, vendor: Homebrew, runtime:
> /usr/local/Cellar/openjdk@17/17.0.12/libexec/openjdk.jdk/Contents/Home
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "14.6.1", arch: "x86_64", family: "mac"
> Darwin 23.6.0 Darwin Kernel Version 23.6.0: Mon Jul 29 21:13:00 PDT
> 2024; root:xnu-10063.141.2~1/RELEASE_X86_64 x86_64
>Reporter: Gary D. Gregory
>Assignee: Michael Osipov
>Priority: Major
> Attachments: screenshot-1.png
>
>
> java.lang.NoSuchMethodError: 'void
> org.apache.maven.doxia.sink.Sink.verbatim()' updating from 3.24.0 to 3.25.0
> {noformat}
> java.lang.NoSuchMethodError: 'void
> org.apache.maven.doxia.sink.Sink.verbatim()'
> at org.apache.maven.reporting.AbstractMavenReportRenderer.verbatimText
> (AbstractMavenReportRenderer.java:363)
> at org.apache.maven.plugins.pmd.CpdReportRenderer.renderDuplications
> (CpdReportRenderer.java:171)
> at org.apache.maven.plugins.pmd.CpdReportRenderer.renderBody
> (CpdReportRenderer.java:96)
> at org.apache.maven.reporting.AbstractMavenReportRenderer.render
> (AbstractMavenReportRenderer.java:93)
> at org.apache.maven.plugins.pmd.CpdReport.executeReport
> (CpdReport.java:140)
> at org.apache.maven.reporting.AbstractMavenReport.generate
> (AbstractMavenReport.java:354)
> at
> org.apache.maven.plugins.site.render.ReportDocumentRenderer.renderDocument
> (ReportDocumentRenderer.java:226)
> at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render
> (DefaultSiteRenderer.java:348)
> at org.apache.maven.plugins.site.render.SiteMojo.renderLocale
> (SiteMojo.java:194)
> at org.apache.maven.plugins.site.render.SiteMojo.execute
> (SiteMojo.java:143)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:126)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:328)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:316)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:174)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
> (MojoExecutor.java:75)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
> (MojoExecutor.java:162)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:159)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:105)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:73)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:53)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:118)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:261)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:173)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:101)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:906)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:283)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:206)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:77)
> at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:569)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:255)
> at org.
[jira] [Commented] (ARCHETYPE-681) [REGRESSION] Output from archetype verification is no longer logged
[
https://issues.apache.org/jira/browse/ARCHETYPE-681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17887134#comment-17887134
]
Slawomir Jaranowski commented on ARCHETYPE-681:
---
There is an option {{streamLogs}} but logs are not forwarded to Maven build log
so it is not working ... I will fix it.
> [REGRESSION] Output from archetype verification is no longer logged
> ---
>
> Key: ARCHETYPE-681
> URL: https://issues.apache.org/jira/browse/ARCHETYPE-681
> Project: Maven Archetype
> Issue Type: Bug
>Affects Versions: 3.3.0
>Reporter: Wolfgang Knauf
>Assignee: Slawomir Jaranowski
>Priority: Major
> Fix For: 3.3.1
>
>
> When build an archetype project, there is a step the generates a sample
> project from the archetype.
>
> With 3.1.2, the maven output to create and build a sample project from the
> archetype was logged (see duplicated "[INFO] [INFO]" lines):
>
> {{[INFO] Project created from Archetype in dir:
> C:\Temp\github\wildfly-archetypes\wildfly-jakartaee-webapp-archetype\target\test-classes\projects\multi\project\multi}}
> {{[INFO] Invoking post-archetype-generation goals: verify}}
> {{[INFO] [INFO] Error stacktraces are turned on.}}
> {{[INFO] [INFO] Scanning for projects...}}
> {{[INFO] [INFO]}}
> {{[INFO] [INFO] -{-}{{-}}< foo.bar:multi
> >{{-}}{-}--}}
> {{[INFO] [INFO] Building multi 0.0.1-SNAPSHOT}}
> {{[INFO] [INFO] from pom.xml}}
> {{...}}
>
> With 3.3.0, there is just this output:
> {{[INFO] Project created from Archetype in dir:
> C:\Temp\github\wildfly-archetypes\wildfly-jakartaee-webapp-archetype\target\test-classes\projects\multi\project\multi}}
> {{[INFO] Invoking post-archetype-generation goals: verify}}
> {{[INFO] Post-archetype-generation invoker exit code: 0}}
> {{...}}
>
> This is not good, as building the sample project might take a long time, or
> might even fail, and you don't see a reason for the long delay after the line
> "Invoking post-archetype-generation goals: verify" is printed. I had also a
> situation where creating and building the sample project failed, and here not
> details about the error were logged.
> Could you bring back the old behavior to log the INFO output?
>
> To reproduce: you could pull the wildfly archetypes:
> [https://github.com/wildfly/wildfly-archetypes]
> At the end of the root pom.xml, change the archetype version to "3.3.0" - we
> are currently stuck with 3.1.2 due to another issue.
> Then build one of the archetype modules (invoke it in the root directory -
> building all archetypes will not work, as one has additional requirements):
> {{mvn -pl wildfly-jakartaee-webapp-archetype clean install}}
>
> Or is there a configuration option to enable logging again?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ARCHETYPE-681) [REGRESSION] Output from archetype verification is no longer logged
[
https://issues.apache.org/jira/browse/ARCHETYPE-681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17887136#comment-17887136
]
Slawomir Jaranowski commented on ARCHETYPE-681:
---
[~wknauf]
{quote}
At the end of the root pom.xml, change the archetype version to "3.3.0" - we
are currently stuck with 3.1.2 due to another issue.
{quote}
What another issue blocking you for upgrade?
> [REGRESSION] Output from archetype verification is no longer logged
> ---
>
> Key: ARCHETYPE-681
> URL: https://issues.apache.org/jira/browse/ARCHETYPE-681
> Project: Maven Archetype
> Issue Type: Bug
>Affects Versions: 3.3.0
>Reporter: Wolfgang Knauf
>Assignee: Slawomir Jaranowski
>Priority: Major
> Fix For: 3.3.1
>
>
> When build an archetype project, there is a step the generates a sample
> project from the archetype.
>
> With 3.1.2, the maven output to create and build a sample project from the
> archetype was logged (see duplicated "[INFO] [INFO]" lines):
>
> {{[INFO] Project created from Archetype in dir:
> C:\Temp\github\wildfly-archetypes\wildfly-jakartaee-webapp-archetype\target\test-classes\projects\multi\project\multi}}
> {{[INFO] Invoking post-archetype-generation goals: verify}}
> {{[INFO] [INFO] Error stacktraces are turned on.}}
> {{[INFO] [INFO] Scanning for projects...}}
> {{[INFO] [INFO]}}
> {{[INFO] [INFO] -{-}{{-}}< foo.bar:multi
> >{{-}}{-}--}}
> {{[INFO] [INFO] Building multi 0.0.1-SNAPSHOT}}
> {{[INFO] [INFO] from pom.xml}}
> {{...}}
>
> With 3.3.0, there is just this output:
> {{[INFO] Project created from Archetype in dir:
> C:\Temp\github\wildfly-archetypes\wildfly-jakartaee-webapp-archetype\target\test-classes\projects\multi\project\multi}}
> {{[INFO] Invoking post-archetype-generation goals: verify}}
> {{[INFO] Post-archetype-generation invoker exit code: 0}}
> {{...}}
>
> This is not good, as building the sample project might take a long time, or
> might even fail, and you don't see a reason for the long delay after the line
> "Invoking post-archetype-generation goals: verify" is printed. I had also a
> situation where creating and building the sample project failed, and here not
> details about the error were logged.
> Could you bring back the old behavior to log the INFO output?
>
> To reproduce: you could pull the wildfly archetypes:
> [https://github.com/wildfly/wildfly-archetypes]
> At the end of the root pom.xml, change the archetype version to "3.3.0" - we
> are currently stuck with 3.1.2 due to another issue.
> Then build one of the archetype modules (invoke it in the root directory -
> building all archetypes will not work, as one has additional requirements):
> {{mvn -pl wildfly-jakartaee-webapp-archetype clean install}}
>
> Or is there a configuration option to enable logging again?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MCHANGES-412) Allow an action to carry an optional scope
[
https://issues.apache.org/jira/browse/MCHANGES-412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary D. Gregory updated MCHANGES-412:
-
Description:
In changes.xml, I would like an *action* to carry an optional {*}scope{*}.
This would help users understand what changes affect which part of their
projects.
For example:
Fix some bug
Bump dependency foo
from 1 to 2
Bump commons-parent
foo from 1 to 2
Documented this and
that
The use of the scope documents where the change applies, usually runtime, test,
or build, but it could be string maybe.
This somewhat parallels the concept of a scope in a dependency so the value set
could be the same as allowed for a dependency scope but that might be too
restrictive.
Thoughts?
was:
In changes.xml, I would like an *action* to carry an optional {*}scope{*}.
This would help users understand what changes affect which part of their
projects.
For example:
Fix some bug
Bump dependency foo
from 1 to 2
Bump commons-parent
foo from 1 to 2
The use of the scope documents where the change applies, usually runtime, test,
or build, but it could be string maybe.
This somewhat parallels the concept of a scope in a dependency so the value set
could be the same as allowed for a dependency scope but that might be too
restrictive.
Thoughts?
> Allow an action to carry an optional scope
> --
>
> Key: MCHANGES-412
> URL: https://issues.apache.org/jira/browse/MCHANGES-412
> Project: Maven Changes Plugin
> Issue Type: New Feature
> Components: changes.xml
>Reporter: Gary D. Gregory
>Priority: Major
>
> In changes.xml, I would like an *action* to carry an optional {*}scope{*}.
> This would help users understand what changes affect which part of their
> projects.
> For example:
> Fix some bug
> Bump dependency foo
> from 1 to 2
> Bump commons-parent
> foo from 1 to 2
> Documented this and
> that
> The use of the scope documents where the change applies, usually runtime,
> test, or build, but it could be string maybe.
> This somewhat parallels the concept of a scope in a dependency so the value
> set could be the same as allowed for a dependency scope but that might be too
> restrictive.
> Thoughts?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
