[jira] [Created] (MNG-6733) Package accessible from more than one module
Giovanni Lovato created MNG-6733:
Summary: Package accessible from more than one module
Key: MNG-6733
URL: https://issues.apache.org/jira/browse/MNG-6733
Project: Maven
Issue Type: Bug
Components: core
Affects Versions: 3.6.1
Reporter: Giovanni Lovato
Importing `org.apache.maven.plugin.AbstractMojo` in a project using JPMS, the
compiler gives this error:
{code:java}
The package org.apache.maven.plugin is accessible from more than one module:
maven.core, maven.plugin.api{code}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Updated] (MNG-6733) Package accessible from more than one module
[
https://issues.apache.org/jira/browse/MNG-6733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Giovanni Lovato updated MNG-6733:
-
Description:
Importing {{org.apache.maven.plugin.AbstractMojo}} in a project using JPMS, the
compiler gives this error:
{code:java}
The package org.apache.maven.plugin is accessible from more than one module:
maven.core, maven.plugin.api{code}
was:
Importing `org.apache.maven.plugin.AbstractMojo` in a project using JPMS, the
compiler gives this error:
{code:java}
The package org.apache.maven.plugin is accessible from more than one module:
maven.core, maven.plugin.api{code}
> Package accessible from more than one module
>
>
> Key: MNG-6733
> URL: https://issues.apache.org/jira/browse/MNG-6733
> Project: Maven
> Issue Type: Bug
> Components: core
>Affects Versions: 3.6.1
>Reporter: Giovanni Lovato
>Priority: Major
>
> Importing {{org.apache.maven.plugin.AbstractMojo}} in a project using JPMS,
> the compiler gives this error:
> {code:java}
> The package org.apache.maven.plugin is accessible from more than one module:
> maven.core, maven.plugin.api{code}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Updated] (MNG-6733) Package accessible from more than one module
[
https://issues.apache.org/jira/browse/MNG-6733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Giovanni Lovato updated MNG-6733:
-
Environment: OpenJDK 12.0.2
> Package accessible from more than one module
>
>
> Key: MNG-6733
> URL: https://issues.apache.org/jira/browse/MNG-6733
> Project: Maven
> Issue Type: Bug
> Components: core
>Affects Versions: 3.6.1
> Environment: OpenJDK 12.0.2
>Reporter: Giovanni Lovato
>Priority: Major
>
> Importing {{org.apache.maven.plugin.AbstractMojo}} in a project using JPMS,
> the compiler gives this error:
> {code:java}
> The package org.apache.maven.plugin is accessible from more than one module:
> maven.core, maven.plugin.api{code}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (MNG-6516) Build maven-mojo using Java9 fails
[ https://issues.apache.org/jira/browse/MNG-6516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16906578#comment-16906578 ] Giovanni Lovato commented on MNG-6516: -- [~rfscholte] Does this mean one cannot adopt JPMS in his own plugin? I have several plugins part of a Maven multi-module project which I'm porting to JPMS and the JavaDoc plugin fails to produce aggregate docs if there's even just one module not adopting JPMS. > Build maven-mojo using Java9 fails > -- > > Key: MNG-6516 > URL: https://issues.apache.org/jira/browse/MNG-6516 > Project: Maven > Issue Type: Bug > Components: Plugin API > Environment: java 9 >Reporter: Matthias Fuchs >Assignee: Robert Scholte >Priority: Major > Labels: java9, modules > > I'm upgrading my Java8 framework to Java9, but I have major problems > upgrading my mojos > (https://github.com/spot-next/spot-framework/tree/develop/spot-maven-plugin). > The problem is that my dependecies maven-artifact a maven-core contain the > same classes. This causes the java9 compiler to fail. It also seems that > those libraries haven't been upgraded to use module-info.java or at least > automatic module name in META-INF. > Expected solution: > restructure the libraries to conform to the java module system. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (MDEP-559) Java 9 bytecode cannot be parsed
[
https://issues.apache.org/jira/browse/MDEP-559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16318290#comment-16318290
]
Giovanni Lovato commented on MDEP-559:
--
Still experiencing this in 3.0.2
> Java 9 bytecode cannot be parsed
>
>
> Key: MDEP-559
> URL: https://issues.apache.org/jira/browse/MDEP-559
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: analyze
>Affects Versions: 3.0.0
> Environment: Apache Maven 3.3.9
> (NON-CANONICAL_2015-11-23T13:17:27+03:00_root; 2015-11-23T21:17:27+11:00)
> Maven home: /opt/maven
> Java version: 9-ea, vendor: Oracle Corporation
> Java home: /usr/lib/jvm/java-9-jdk
> Default locale: en_AU, platform encoding: UTF-8
> OS name: "linux", version: "4.9.11-1-arch", arch: "amd64", family: "unix"
>Reporter: Ben Alex
>Assignee: Robert Scholte
>
> Attempting to run analyze-only against source compiled with Java 9 results in:
> {noformat}
> [INFO] --- maven-dependency-plugin:3.0.0:analyze-only (config-dependency) @
> lmdbjava ---
> [DEBUG] Configuring mojo
> org.apache.maven.plugins:maven-dependency-plugin:3.0.0:analyze-only from
> plugin realm
> ClassRealm[plugin>org.apache.maven.plugins:maven-dependency-plugin:3.0.0,
> parent: jdk.internal.loader.ClassLoaders$AppClassLoader@3b764bce]
> [DEBUG] Configuring mojo
> 'org.apache.maven.plugins:maven-dependency-plugin:3.0.0:analyze-only' with
> basic configurator -->
> [DEBUG] (f) analyzer = default
> [DEBUG] (f) baseDir = /home/bpa/projects/lmdbjava
> [DEBUG] (f) failOnWarning = true
> [DEBUG] (f) ignoreNonCompile = false
> [DEBUG] (f) outputDirectory = /home/bpa/projects/lmdbjava/target
> [DEBUG] (f) outputXML = false
> [DEBUG] (f) project = MavenProject: org.lmdbjava:lmdbjava:0.0.6-SNAPSHOT @
> /home/bpa/projects/lmdbjava/dependency-reduced-pom.xml
> [DEBUG] (f) scriptableFlag = $$%%%
> [DEBUG] (f) scriptableOutput = false
> [DEBUG] (f) skip = false
> [DEBUG] (f) usedDependencies = [org.lmdbjava:lmdbjava-native-linux-x86_64,
> org.lmdbjava:lmdbjava-native-windows-x86_64,
> org.lmdbjava:lmdbjava-native-osx-x86_64]
> [DEBUG] (f) verbose = false
> [DEBUG] -- end configuration --
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 7.256 s
> [INFO] Finished at: 2017-03-17T17:32:20+11:00
> [INFO] Final Memory: 40M/132M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-dependency-plugin:3.0.0:analyze-only
> (config-dependency) on project lmdbjava: Execution config-dependency of goal
> org.apache.maven.plugins:maven-dependency-plugin:3.0.0:analyze-only failed.
> IllegalArgumentException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-dependency-plugin:3.0.0:analyze-only
> (config-dependency) on project lmdbjava: Execution config-dependency of goal
> org.apache.maven.plugins:maven-dependency-plugin:3.0.0:analyze-only failed.
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:547)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnh
[jira] [Commented] (MDEP-559) Java 9 bytecode cannot be parsed
[
https://issues.apache.org/jira/browse/MDEP-559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16372559#comment-16372559
]
Giovanni Lovato commented on MDEP-559:
--
What's the current status of this? Is there a version of the plugin I can test
with Java 9?
> Java 9 bytecode cannot be parsed
>
>
> Key: MDEP-559
> URL: https://issues.apache.org/jira/browse/MDEP-559
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: analyze
>Affects Versions: 3.0.0
> Environment: Apache Maven 3.3.9
> (NON-CANONICAL_2015-11-23T13:17:27+03:00_root; 2015-11-23T21:17:27+11:00)
> Maven home: /opt/maven
> Java version: 9-ea, vendor: Oracle Corporation
> Java home: /usr/lib/jvm/java-9-jdk
> Default locale: en_AU, platform encoding: UTF-8
> OS name: "linux", version: "4.9.11-1-arch", arch: "amd64", family: "unix"
>Reporter: Ben Alex
>Assignee: Robert Scholte
>Priority: Major
>
> Attempting to run analyze-only against source compiled with Java 9 results in:
> {noformat}
> [INFO] --- maven-dependency-plugin:3.0.0:analyze-only (config-dependency) @
> lmdbjava ---
> [DEBUG] Configuring mojo
> org.apache.maven.plugins:maven-dependency-plugin:3.0.0:analyze-only from
> plugin realm
> ClassRealm[plugin>org.apache.maven.plugins:maven-dependency-plugin:3.0.0,
> parent: jdk.internal.loader.ClassLoaders$AppClassLoader@3b764bce]
> [DEBUG] Configuring mojo
> 'org.apache.maven.plugins:maven-dependency-plugin:3.0.0:analyze-only' with
> basic configurator -->
> [DEBUG] (f) analyzer = default
> [DEBUG] (f) baseDir = /home/bpa/projects/lmdbjava
> [DEBUG] (f) failOnWarning = true
> [DEBUG] (f) ignoreNonCompile = false
> [DEBUG] (f) outputDirectory = /home/bpa/projects/lmdbjava/target
> [DEBUG] (f) outputXML = false
> [DEBUG] (f) project = MavenProject: org.lmdbjava:lmdbjava:0.0.6-SNAPSHOT @
> /home/bpa/projects/lmdbjava/dependency-reduced-pom.xml
> [DEBUG] (f) scriptableFlag = $$%%%
> [DEBUG] (f) scriptableOutput = false
> [DEBUG] (f) skip = false
> [DEBUG] (f) usedDependencies = [org.lmdbjava:lmdbjava-native-linux-x86_64,
> org.lmdbjava:lmdbjava-native-windows-x86_64,
> org.lmdbjava:lmdbjava-native-osx-x86_64]
> [DEBUG] (f) verbose = false
> [DEBUG] -- end configuration --
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 7.256 s
> [INFO] Finished at: 2017-03-17T17:32:20+11:00
> [INFO] Final Memory: 40M/132M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-dependency-plugin:3.0.0:analyze-only
> (config-dependency) on project lmdbjava: Execution config-dependency of goal
> org.apache.maven.plugins:maven-dependency-plugin:3.0.0:analyze-only failed.
> IllegalArgumentException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-dependency-plugin:3.0.0:analyze-only
> (config-dependency) on project lmdbjava: Execution config-dependency of goal
> org.apache.maven.plugins:maven-dependency-plugin:3.0.0:analyze-only failed.
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(M
[jira] [Comment Edited] (MDEP-559) Java 9 bytecode cannot be parsed
[
https://issues.apache.org/jira/browse/MDEP-559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16372559#comment-16372559
]
Giovanni Lovato edited comment on MDEP-559 at 2/22/18 9:10 AM:
---
What's the current status of this? Is there a version of the plugin I can test
with Java 9?
Current 3.0.3-SNAPSHOT fails for me with:
{code:java}
Execution default-cli of goal
org.apache.maven.plugins:maven-dependency-plugin:3.0.3-SNAPSHOT:analyze-only
failed.
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:213)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:154)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:146)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:117)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:81)
at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
(SingleThreadedBuilder.java:51)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:309)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:194)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:107)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:955)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:194)
at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:498)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
(Launcher.java:289)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch
(Launcher.java:229)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
(Launcher.java:415)
at org.codehaus.plexus.classworlds.launcher.Launcher.main
(Launcher.java:356)
Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
default-cli of goal
org.apache.maven.plugins:maven-dependency-plugin:3.0.3-SNAPSHOT:analyze-only
failed.
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
(DefaultBuildPluginManager.java:145)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:208)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:154)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:146)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:117)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:81)
at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
(SingleThreadedBuilder.java:51)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:309)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:194)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:107)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:955)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:194)
at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:498)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
(Launcher.java:289)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch
(Launcher.java:229)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
(Launcher.java:415)
at org.codehaus.plexus.classworlds.launcher.Launcher.main
(Launcher.java:356)
Caused by: java.lang.IllegalArgumentException
at org.objectweb.asm.ClassReader. (Unknown Source)
at org.objectweb.asm.ClassReader. (Unknown Source)
at org.objectweb.asm.ClassReader. (Unknown Source)
at
org.apache.maven.shared.dependency.analyzer.asm.DependencyClassFileVisitor.visitClass
(DependencyClassFileVisitor.java:65)
at
org.apache.maven.shared.dependency.analyzer.ClassFileVisitorUtils.visitClass
(ClassFileVisitorUtils.java:163)
at
org.apache.maven.shared.dependency.analyzer.ClassFileVisitorUtils.acceptDirectory
(ClassFileVisitorUtils.jav
[jira] [Commented] (ARCHETYPE-492) Underscore in filenames problematic due to greedy regex
[
https://issues.apache.org/jira/browse/ARCHETYPE-492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16374383#comment-16374383
]
Giovanni Lovato commented on ARCHETYPE-492:
---
This is an issue also for archetypes which contains Flyway database migration
files, which has a specific filename pattern, e.g. \{{V2__my-schema.sql}} (i.e.
version + _ + _ + description). So if I include in the archetype a file named
{{V2rootArtifactId__-schema.sql}} I would expect it to be created as
{{V2__my-artifact-schema.sql}}.
> Underscore in filenames problematic due to greedy regex
> ---
>
> Key: ARCHETYPE-492
> URL: https://issues.apache.org/jira/browse/ARCHETYPE-492
> Project: Maven Archetype
> Issue Type: Bug
> Components: Plugin
>Affects Versions: 2.4
> Environment: Windows 7, Sun JDK
>Reporter: Oliver Dungey
>Priority: Major
>
> If you have a file in a project with an underscore adjacent to a substitution
> variable, the substitution will fail i.e.
> if {{artifactId}} is 'Test' and a target file is to be named
> {{something_test.txt}} the file in the template should be named
> {{somethingartifactId__.txt}} (3 underscores in the middle) but the
> result is an error stating that the property {{_artifactId}} cannot be found.
> This is because the term inside the regex is a greedy .* - a simple fix
> would be to change this to something like __[^_]*___ which would only match
> non-underscore characters.
> Fixing this issue would allow the use of underscores in filenames in all
> circumstances rather than the current situation where you may get lucky. The
> only down side to fixing this issue is that properties with leading or
> trailing underscores will not be valid - this seems a far more preferable
> situation.
> A patch for this issue was put on this bug back in 01//2009 but somehow got
> ignored - see [~maslovalex] patch and comments at the end of this issue:
> https://issues.apache.org/jira/browse/ARCHETYPE-191
> Apologies for the formatting - it appears double underscores are an issue :-)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (ARCHETYPE-492) Underscore in filenames problematic due to greedy regex
[
https://issues.apache.org/jira/browse/ARCHETYPE-492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16374383#comment-16374383
]
Giovanni Lovato edited comment on ARCHETYPE-492 at 2/23/18 2:06 PM:
This is an issue also for archetypes which contains Flyway database migration
files, which has a specific filename pattern, e.g. {{V2__my-schema.sql}} (i.e.
version + _ + _ + description). So if I include in the archetype a file named
{{V2rootArtifactId__-schema.sql}} I would expect it to be created as
{{V2__my-artifact-schema.sql}}.
was (Author: heruan):
This is an issue also for archetypes which contains Flyway database migration
files, which has a specific filename pattern, e.g. \{{V2__my-schema.sql}} (i.e.
version + _ + _ + description). So if I include in the archetype a file named
{{V2rootArtifactId__-schema.sql}} I would expect it to be created as
{{V2__my-artifact-schema.sql}}.
> Underscore in filenames problematic due to greedy regex
> ---
>
> Key: ARCHETYPE-492
> URL: https://issues.apache.org/jira/browse/ARCHETYPE-492
> Project: Maven Archetype
> Issue Type: Bug
> Components: Plugin
>Affects Versions: 2.4
> Environment: Windows 7, Sun JDK
>Reporter: Oliver Dungey
>Priority: Major
>
> If you have a file in a project with an underscore adjacent to a substitution
> variable, the substitution will fail i.e.
> if {{artifactId}} is 'Test' and a target file is to be named
> {{something_test.txt}} the file in the template should be named
> {{somethingartifactId__.txt}} (3 underscores in the middle) but the
> result is an error stating that the property {{_artifactId}} cannot be found.
> This is because the term inside the regex is a greedy .* - a simple fix
> would be to change this to something like __[^_]*___ which would only match
> non-underscore characters.
> Fixing this issue would allow the use of underscores in filenames in all
> circumstances rather than the current situation where you may get lucky. The
> only down side to fixing this issue is that properties with leading or
> trailing underscores will not be valid - this seems a far more preferable
> situation.
> A patch for this issue was put on this bug back in 01//2009 but somehow got
> ignored - see [~maslovalex] patch and comments at the end of this issue:
> https://issues.apache.org/jira/browse/ARCHETYPE-191
> Apologies for the formatting - it appears double underscores are an issue :-)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (ARCHETYPE-492) Underscore in filenames problematic due to greedy regex
[
https://issues.apache.org/jira/browse/ARCHETYPE-492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16374383#comment-16374383
]
Giovanni Lovato edited comment on ARCHETYPE-492 at 2/23/18 2:07 PM:
This is an issue also for archetypes which contains Flyway database migration
files, which has a specific filename pattern, e.g. {{V2\_\_my-schema.sql}}
(i.e. version + {{\_}} + {{\_}} + description). So if I include in the
archetype a file named {{V2\_\_\_\_rootArtifactId\_\_-schema.sql}} I would
expect it to be created as {{V2\_\_my-artifact-schema.sql}}.
was (Author: heruan):
This is an issue also for archetypes which contains Flyway database migration
files, which has a specific filename pattern, e.g. {{V2__my-schema.sql}} (i.e.
version + _ + _ + description). So if I include in the archetype a file named
{{V2rootArtifactId__-schema.sql}} I would expect it to be created as
{{V2__my-artifact-schema.sql}}.
> Underscore in filenames problematic due to greedy regex
> ---
>
> Key: ARCHETYPE-492
> URL: https://issues.apache.org/jira/browse/ARCHETYPE-492
> Project: Maven Archetype
> Issue Type: Bug
> Components: Plugin
>Affects Versions: 2.4
> Environment: Windows 7, Sun JDK
>Reporter: Oliver Dungey
>Priority: Major
>
> If you have a file in a project with an underscore adjacent to a substitution
> variable, the substitution will fail i.e.
> if {{artifactId}} is 'Test' and a target file is to be named
> {{something_test.txt}} the file in the template should be named
> {{somethingartifactId__.txt}} (3 underscores in the middle) but the
> result is an error stating that the property {{_artifactId}} cannot be found.
> This is because the term inside the regex is a greedy .* - a simple fix
> would be to change this to something like __[^_]*___ which would only match
> non-underscore characters.
> Fixing this issue would allow the use of underscores in filenames in all
> circumstances rather than the current situation where you may get lucky. The
> only down side to fixing this issue is that properties with leading or
> trailing underscores will not be valid - this seems a far more preferable
> situation.
> A patch for this issue was put on this bug back in 01//2009 but somehow got
> ignored - see [~maslovalex] patch and comments at the end of this issue:
> https://issues.apache.org/jira/browse/ARCHETYPE-191
> Apologies for the formatting - it appears double underscores are an issue :-)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MDEP-559) Java 9 bytecode cannot be parsed
[
https://issues.apache.org/jira/browse/MDEP-559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16377100#comment-16377100
]
Giovanni Lovato commented on MDEP-559:
--
Great, thank you! Which repository URL should I use to test the snapshot with
the fix?
> Java 9 bytecode cannot be parsed
>
>
> Key: MDEP-559
> URL: https://issues.apache.org/jira/browse/MDEP-559
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: analyze
>Affects Versions: 3.0.0
> Environment: Apache Maven 3.3.9
> (NON-CANONICAL_2015-11-23T13:17:27+03:00_root; 2015-11-23T21:17:27+11:00)
> Maven home: /opt/maven
> Java version: 9-ea, vendor: Oracle Corporation
> Java home: /usr/lib/jvm/java-9-jdk
> Default locale: en_AU, platform encoding: UTF-8
> OS name: "linux", version: "4.9.11-1-arch", arch: "amd64", family: "unix"
>Reporter: Ben Alex
>Assignee: Robert Scholte
>Priority: Major
> Fix For: 3.1.0
>
>
> Attempting to run analyze-only against source compiled with Java 9 results in:
> {noformat}
> [INFO] --- maven-dependency-plugin:3.0.0:analyze-only (config-dependency) @
> lmdbjava ---
> [DEBUG] Configuring mojo
> org.apache.maven.plugins:maven-dependency-plugin:3.0.0:analyze-only from
> plugin realm
> ClassRealm[plugin>org.apache.maven.plugins:maven-dependency-plugin:3.0.0,
> parent: jdk.internal.loader.ClassLoaders$AppClassLoader@3b764bce]
> [DEBUG] Configuring mojo
> 'org.apache.maven.plugins:maven-dependency-plugin:3.0.0:analyze-only' with
> basic configurator -->
> [DEBUG] (f) analyzer = default
> [DEBUG] (f) baseDir = /home/bpa/projects/lmdbjava
> [DEBUG] (f) failOnWarning = true
> [DEBUG] (f) ignoreNonCompile = false
> [DEBUG] (f) outputDirectory = /home/bpa/projects/lmdbjava/target
> [DEBUG] (f) outputXML = false
> [DEBUG] (f) project = MavenProject: org.lmdbjava:lmdbjava:0.0.6-SNAPSHOT @
> /home/bpa/projects/lmdbjava/dependency-reduced-pom.xml
> [DEBUG] (f) scriptableFlag = $$%%%
> [DEBUG] (f) scriptableOutput = false
> [DEBUG] (f) skip = false
> [DEBUG] (f) usedDependencies = [org.lmdbjava:lmdbjava-native-linux-x86_64,
> org.lmdbjava:lmdbjava-native-windows-x86_64,
> org.lmdbjava:lmdbjava-native-osx-x86_64]
> [DEBUG] (f) verbose = false
> [DEBUG] -- end configuration --
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 7.256 s
> [INFO] Finished at: 2017-03-17T17:32:20+11:00
> [INFO] Final Memory: 40M/132M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-dependency-plugin:3.0.0:analyze-only
> (config-dependency) on project lmdbjava: Execution config-dependency of goal
> org.apache.maven.plugins:maven-dependency-plugin:3.0.0:analyze-only failed.
> IllegalArgumentException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-dependency-plugin:3.0.0:analyze-only
> (config-dependency) on project lmdbjava: Execution config-dependency of goal
> org.apache.maven.plugins:maven-dependency-plugin:3.0.0:analyze-only failed.
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.la
[jira] [Commented] (MDEP-559) Java 9 bytecode cannot be parsed
[
https://issues.apache.org/jira/browse/MDEP-559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16380480#comment-16380480
]
Giovanni Lovato commented on MDEP-559:
--
Just tried lastest 3.0.3-SNAPSHOT and it seems to work!
> Java 9 bytecode cannot be parsed
>
>
> Key: MDEP-559
> URL: https://issues.apache.org/jira/browse/MDEP-559
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: analyze
>Affects Versions: 3.0.0
> Environment: Apache Maven 3.3.9
> (NON-CANONICAL_2015-11-23T13:17:27+03:00_root; 2015-11-23T21:17:27+11:00)
> Maven home: /opt/maven
> Java version: 9-ea, vendor: Oracle Corporation
> Java home: /usr/lib/jvm/java-9-jdk
> Default locale: en_AU, platform encoding: UTF-8
> OS name: "linux", version: "4.9.11-1-arch", arch: "amd64", family: "unix"
>Reporter: Ben Alex
>Assignee: Robert Scholte
>Priority: Major
> Fix For: 3.1.0
>
>
> Attempting to run analyze-only against source compiled with Java 9 results in:
> {noformat}
> [INFO] --- maven-dependency-plugin:3.0.0:analyze-only (config-dependency) @
> lmdbjava ---
> [DEBUG] Configuring mojo
> org.apache.maven.plugins:maven-dependency-plugin:3.0.0:analyze-only from
> plugin realm
> ClassRealm[plugin>org.apache.maven.plugins:maven-dependency-plugin:3.0.0,
> parent: jdk.internal.loader.ClassLoaders$AppClassLoader@3b764bce]
> [DEBUG] Configuring mojo
> 'org.apache.maven.plugins:maven-dependency-plugin:3.0.0:analyze-only' with
> basic configurator -->
> [DEBUG] (f) analyzer = default
> [DEBUG] (f) baseDir = /home/bpa/projects/lmdbjava
> [DEBUG] (f) failOnWarning = true
> [DEBUG] (f) ignoreNonCompile = false
> [DEBUG] (f) outputDirectory = /home/bpa/projects/lmdbjava/target
> [DEBUG] (f) outputXML = false
> [DEBUG] (f) project = MavenProject: org.lmdbjava:lmdbjava:0.0.6-SNAPSHOT @
> /home/bpa/projects/lmdbjava/dependency-reduced-pom.xml
> [DEBUG] (f) scriptableFlag = $$%%%
> [DEBUG] (f) scriptableOutput = false
> [DEBUG] (f) skip = false
> [DEBUG] (f) usedDependencies = [org.lmdbjava:lmdbjava-native-linux-x86_64,
> org.lmdbjava:lmdbjava-native-windows-x86_64,
> org.lmdbjava:lmdbjava-native-osx-x86_64]
> [DEBUG] (f) verbose = false
> [DEBUG] -- end configuration --
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 7.256 s
> [INFO] Finished at: 2017-03-17T17:32:20+11:00
> [INFO] Final Memory: 40M/132M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-dependency-plugin:3.0.0:analyze-only
> (config-dependency) on project lmdbjava: Execution config-dependency of goal
> org.apache.maven.plugins:maven-dependency-plugin:3.0.0:analyze-only failed.
> IllegalArgumentException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-dependency-plugin:3.0.0:analyze-only
> (config-dependency) on project lmdbjava: Execution config-dependency of goal
> org.apache.maven.plugins:maven-dependency-plugin:3.0.0:analyze-only failed.
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.
[jira] [Commented] (MJAVADOC-517) NPE under Java 10 RC
[
https://issues.apache.org/jira/browse/MJAVADOC-517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16407619#comment-16407619
]
Giovanni Lovato commented on MJAVADOC-517:
--
Which repository should I use to test 3.0.1? At
[https://repository.apache.org/content/groups/snapshots/org/apache/maven/plugins/maven-javadoc-plugin/3.0.1-SNAPSHOT/]
there are old snapshots.
> NPE under Java 10 RC
>
>
> Key: MJAVADOC-517
> URL: https://issues.apache.org/jira/browse/MJAVADOC-517
> Project: Maven Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 3.0.0
>Reporter: Ian Young
>Assignee: Robert Scholte
>Priority: Major
> Fix For: 3.0.1
>
>
> Under Java 10 RC, the plugin generates the following exception:
> {code:java}
> Caused by: java.lang.NullPointerException
> at org.apache.commons.lang3.SystemUtils.isJavaVersionAtLeast
> (SystemUtils.java:1626)
> at
> org.apache.maven.plugins.javadoc.AbstractJavadocMojo.getJavadocExecutable
> (AbstractJavadocMojo.java:3683)
> at org.apache.maven.plugins.javadoc.AbstractJavadocMojo.executeReport
> (AbstractJavadocMojo.java:2001)
> at org.apache.maven.plugins.javadoc.JavadocJar.doExecute
> (JavadocJar.java:190)
> {code}
> This seems to be down to the version string:
> {code:java}
> java version "10" 2018-03-20
> Java(TM) SE Runtime Environment 18.3 (build 10+43)
> Java HotSpot(TM) 64-Bit Server VM 18.3 (build 10+43, mixed mode)
> {code}
> {{commons-lang3}} version 3.5 can't deal with this, see
> https://issues.apache.org/jira/browse/LANG-1365
> Inserting an explicit dependency on {{commons-lang3}} version 3.7 for the
> plugin works round the issue, and changing the dependency seems like the
> right fix for the next release of this plugin.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
