[jira] [Created] (MPLUGINTESTING-64) broken links on website
Samael Bate created MPLUGINTESTING-64: - Summary: broken links on website Key: MPLUGINTESTING-64 URL: https://issues.apache.org/jira/browse/MPLUGINTESTING-64 Project: Maven Plugin Testing Issue Type: Task Reporter: Samael Bate Some links on [https://maven.apache.org/plugin-testing/maven-plugin-testing-harness/] are invalid. On the [https://maven.apache.org/plugin-testing/maven-plugin-testing-harness/source-repository.html] page the github url is [https://github.com/apache/maven-plugin-testing/maven-plugin-testing-harness/] but it should simply be [https://github.com/apache/maven-plugin-testing/] Also on the [https://maven.apache.org/plugin-testing/maven-plugin-testing-harness/issue-tracking.html] page it has a link to [http://jira.codehaus.org/browse/MPLUGINTESTING] which is wrong as it should point to this Jira -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (MPLUGINTESTING-62) use maven API 3.6.0 and Plexus 2.0.0
[ https://issues.apache.org/jira/browse/MPLUGINTESTING-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samael Bate updated MPLUGINTESTING-62: -- Summary: use maven API 3.6.0 and Plexus 2.0.0 (was: target maven 3.6.0 API) > use maven API 3.6.0 and Plexus 2.0.0 > > > Key: MPLUGINTESTING-62 > URL: https://issues.apache.org/jira/browse/MPLUGINTESTING-62 > Project: Maven Plugin Testing > Issue Type: Improvement >Reporter: Samael Bate >Priority: Major > > To get this plugin working well with more recent versions of Maven (and Java) > it makes sense to do this and MPLUGINTESTING-61 -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (MPLUGINTESTING-62) use maven API 3.6.0 and Plexus 2.0.0
[ https://issues.apache.org/jira/browse/MPLUGINTESTING-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samael Bate updated MPLUGINTESTING-62: -- Description: Along with updating to use Java 7 (MPLUGINTESTING-61) the plugin should use a recent maven API. As there is no 3.6.0 for maven-aether-provider it will need be set to 3.3.9 was:To get this plugin working well with more recent versions of Maven (and Java) it makes sense to do this and MPLUGINTESTING-61 > use maven API 3.6.0 and Plexus 2.0.0 > > > Key: MPLUGINTESTING-62 > URL: https://issues.apache.org/jira/browse/MPLUGINTESTING-62 > Project: Maven Plugin Testing > Issue Type: Improvement >Reporter: Samael Bate >Priority: Major > > Along with updating to use Java 7 (MPLUGINTESTING-61) the plugin should use a > recent maven API. > As there is no 3.6.0 for maven-aether-provider it will need be set to 3.3.9 -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (MPLUGINTESTING-61) Require Java 7
[ https://issues.apache.org/jira/browse/MPLUGINTESTING-61?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16904677#comment-16904677 ] Samael Bate commented on MPLUGINTESTING-61: --- I'd agrue that 8 should now be the minimum. > Require Java 7 > -- > > Key: MPLUGINTESTING-61 > URL: https://issues.apache.org/jira/browse/MPLUGINTESTING-61 > Project: Maven Plugin Testing > Issue Type: Improvement >Reporter: Robert Scholte >Assignee: Robert Scholte >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (MPOM-222) update target JDK from 6 to 8
Samael Bate created MPOM-222: Summary: update target JDK from 6 to 8 Key: MPOM-222 URL: https://issues.apache.org/jira/browse/MPOM-222 Project: Maven POMs Issue Type: Improvement Reporter: Samael Bate currently the maven-pom set's compiler source and compiler target to JDK 6. Java 6 is already EOL and even 7 is old. Please just jump straight to setting Java 8 as the target. Otherwise all the projects that inherit it are stuck trying to support jdk 6, 7, 8, 9, 10, 11, 12, and 13 which is bound to be a burden. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (MCOMPILER-376) Change default source/target to 1.7 (new minimum for JDK 12)
[ https://issues.apache.org/jira/browse/MCOMPILER-376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16904679#comment-16904679 ] Samael Bate commented on MCOMPILER-376: --- The JDK is moving far quicker than tooling. The compiler plugin should jump straight to Java 8 as minimum. It's been years since I've needed to work on a project that didn't use at least JDK 8 and anyone that needs older is already covered by current releases. If the compiler plugin jumps to JDK8 as minimum for next release or 2 then jumps to JDK 11 that would be ideal. Just keep to the LTS versions. > Change default source/target to 1.7 (new minimum for JDK 12) > > > Key: MCOMPILER-376 > URL: https://issues.apache.org/jira/browse/MCOMPILER-376 > Project: Maven Compiler Plugin > Issue Type: Improvement >Reporter: Robert Scholte >Assignee: Robert Scholte >Priority: Major > > With the statement "It must be possible to build a Hello World application > with the latest JDK + latest Maven + minimum pom" the default value for > source+target must be lifted to 1.7 -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (MPLUGINTESTING-62) target maven 3.6.0 API
Samael Bate created MPLUGINTESTING-62: - Summary: target maven 3.6.0 API Key: MPLUGINTESTING-62 URL: https://issues.apache.org/jira/browse/MPLUGINTESTING-62 Project: Maven Plugin Testing Issue Type: Improvement Reporter: Samael Bate To get this plugin working well with more recent versions of Maven (and Java) it makes sense to do this and MPLUGINTESTING-61 -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (MPLUGINTESTING-63) AbstractMojoTestCase should return correct type
[
https://issues.apache.org/jira/browse/MPLUGINTESTING-63?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16904742#comment-16904742
]
Samael Bate commented on MPLUGINTESTING-63:
---
seems we cannot get the goal name via the annotation as _Mojo_ has
_RetentionPolicy.CLASS_ and is therefore not available at runtime.
> AbstractMojoTestCase should return correct type
> ---
>
> Key: MPLUGINTESTING-63
> URL: https://issues.apache.org/jira/browse/MPLUGINTESTING-63
> Project: Maven Plugin Testing
> Issue Type: Improvement
>Reporter: Samael Bate
>Priority: Major
>
> the _AbstractMojoTestCase_ class has numerous methods that simply return
> _Mojo._ An exmaple of which would be:
> {code:java}
> protected Mojo lookupConfiguredMojo( MavenProject project, String goal )
> throws Exception
> {
> return lookupConfiguredMojo( newMavenSession( project ),
> newMojoExecution( goal ) );
> }{code}
>
> It would be to deprecate these methods and replace them with typed
> equivelant, so the aboce would become:
> {code:java}
> protected T lookupConfiguredMojo( MavenProject project,
> Class type ){code}
> as noted by [~rfscholte] on [github PR
> 8|https://github.com/apache/maven-plugin-testing/pull/8#issuecomment-520251983],
> the name of the goal could be obtained from the Mojo's annotation
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Created] (MPLUGINTESTING-63) AbstractMojoTestCase should return correct type
Samael Bate created MPLUGINTESTING-63:
-
Summary: AbstractMojoTestCase should return correct type
Key: MPLUGINTESTING-63
URL: https://issues.apache.org/jira/browse/MPLUGINTESTING-63
Project: Maven Plugin Testing
Issue Type: Improvement
Reporter: Samael Bate
the _AbstractMojoTestCase_ class has numerous methods that simply return
_Mojo._ An exmaple of which would be:
{code:java}
protected Mojo lookupConfiguredMojo( MavenProject project, String goal )
throws Exception
{
return lookupConfiguredMojo( newMavenSession( project ), newMojoExecution(
goal ) );
}{code}
It would be to deprecate these methods and replace them with typed equivelant,
so the aboce would become:
{code:java}
protected T lookupConfiguredMojo( MavenProject project,
Class type ){code}
as noted by [~rfscholte] on [github PR
8|https://github.com/apache/maven-plugin-testing/pull/8#issuecomment-520251983],
the name of the goal could be obtained from the Mojo's annotation
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Created] (MCOMPILER-448) release 3.9.0
Samael Bate created MCOMPILER-448: - Summary: release 3.9.0 Key: MCOMPILER-448 URL: https://issues.apache.org/jira/browse/MCOMPILER-448 Project: Maven Compiler Plugin Issue Type: Task Reporter: Samael Bate The last release was over a year ago and since then there's been fixes such as MCOMPILER-359 that people like myself are waiting for. What's the ETA on doing an actual release build of 3.9.0? How about an xmas release? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MPLUGINTESTING-62) use maven API 3.6.0 and Plexus 2.0.0
[ https://issues.apache.org/jira/browse/MPLUGINTESTING-62?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17527641#comment-17527641 ] Samael Bate commented on MPLUGINTESTING-62: --- When I raised the [PR for this|https://github.com/apache/maven-plugin-testing/pull/8] back in 2019, there was push back because people did not want to break compatibility with old Java/Maven versions. Now that a few years have passed is this still the case? Is there any appetite for these changes? I'd like to be able to use plugin testing > use maven API 3.6.0 and Plexus 2.0.0 > > > Key: MPLUGINTESTING-62 > URL: https://issues.apache.org/jira/browse/MPLUGINTESTING-62 > Project: Maven Plugin Testing > Issue Type: Dependency upgrade >Reporter: Samael Bate >Priority: Major > Labels: close-pending > > Along with updating to use Java 7 (MPLUGINTESTING-61) the plugin should use a > recent maven API. > As there is no 3.6.0 for maven-aether-provider it will need be set to 3.3.9 -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (MPLUGINTESTING-71) Require Java 8
[ https://issues.apache.org/jira/browse/MPLUGINTESTING-71?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17527651#comment-17527651 ] Samael Bate commented on MPLUGINTESTING-71: --- Updating codebase to support more recent Java will likely require updates to min Maven version and Plexus. See related PR for MPLUGINTESTING-62 that was done in 2019. > Require Java 8 > -- > > Key: MPLUGINTESTING-71 > URL: https://issues.apache.org/jira/browse/MPLUGINTESTING-71 > Project: Maven Plugin Testing > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Priority: Minor > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (MPLUGINTESTING-72) release 3.4.0
Samael Bate created MPLUGINTESTING-72: - Summary: release 3.4.0 Key: MPLUGINTESTING-72 URL: https://issues.apache.org/jira/browse/MPLUGINTESTING-72 Project: Maven Plugin Testing Issue Type: Wish Reporter: Samael Bate the master branch is passing all builds. There hasn't been a release since 2014. What's the reasoning for not publishing a new release? There are numerous dependency updates as well as documentation fixes. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (MJAR-294) adding module-info causes build to fail due to invalid date
[
https://issues.apache.org/jira/browse/MJAR-294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Samael Bate updated MJAR-294:
-
Description:
I added a module-info.java to my project and found that the build was failing.
In the log output I found the following error (which seems to come from
maven-archiver):
{code:java}
date 1970-01-01T00:00:10Z is not within the valid range 1980-01-01T00:00:02Z to
2099-12-31T23:59:59Z {code}
This is odd and I have no idea what is trying to set a date to Jan 1st 1970 but
I'm positive that something about maven-jar-plugin and modular jars can get
broken somehow.
Simply renaming _module-info.java_ to _module-info.txt_ fixed the build but of
course I want to modularise the project.
I ran _mvn clean package -X_ here i the output:
{code:java}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-jar-plugin:3.3.0:jar (default-jar) on project
my-project: Error assembling JAR: Could not create modular JAR file. The JDK
jar tool exited with 1 -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
org.apache.maven.plugins:maven-jar-plugin:3.3.0:jar (default-jar) on project
my-project: Error assembling JAR
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
(MojoExecutor.java:375)
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
(MojoExecutor.java:351)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:215)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:171)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:163)
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:56)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:294)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:960)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:293)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:196)
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:568)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
(Launcher.java:282)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch
(Launcher.java:225)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
(Launcher.java:406)
at org.codehaus.plexus.classworlds.launcher.Launcher.main
(Launcher.java:347)
Caused by: org.apache.maven.plugin.MojoExecutionException: Error assembling JAR
at org.apache.maven.plugins.jar.AbstractJarMojo.createArchive
(AbstractJarMojo.java:281)
at org.apache.maven.plugins.jar.AbstractJarMojo.execute
(AbstractJarMojo.java:305)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
(DefaultBuildPluginManager.java:137)
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
(MojoExecutor.java:370)
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
(MojoExecutor.java:351)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:215)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:171)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:163)
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:56)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:294)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:960)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:293)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:196)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0
[jira] [Commented] (MJAR-294) adding module-info causes build to fail due to invalid date
[
https://issues.apache.org/jira/browse/MJAR-294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17731117#comment-17731117
]
Samael Bate commented on MJAR-294:
--
Seems my root pom had an invalid value set for
{code:java}
10 {code}
so removing that fixes the build properly so that I now use the module-info.
The weird thing with this is I don't know how it didn't fail before.
> adding module-info causes build to fail due to invalid date
> ---
>
> Key: MJAR-294
> URL: https://issues.apache.org/jira/browse/MJAR-294
> Project: Maven JAR Plugin
> Issue Type: Bug
>Affects Versions: 3.3.0
>Reporter: Samael Bate
>Priority: Major
>
> I added a module-info.java to my project and found that the build was
> failing. In the log output I found the following error (which seems to come
> from maven-archiver):
> {code:java}
> date 1970-01-01T00:00:10Z is not within the valid range 1980-01-01T00:00:02Z
> to 2099-12-31T23:59:59Z {code}
> This is odd and I have no idea what is trying to set a date to Jan 1st 1970
> but I'm positive that something about maven-jar-plugin and modular jars can
> get broken somehow.
> Simply renaming _module-info.java_ to _module-info.txt_ fixed the build but
> of course I want to modularise the project.
> I ran _mvn clean package -X_ here i the output:
> {code:java}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-jar-plugin:3.3.0:jar (default-jar) on project
> my-project: Error assembling JAR: Could not create modular JAR file. The JDK
> jar tool exited with 1 -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-jar-plugin:3.3.0:jar (default-jar) on
> project my-project: Error assembling JAR
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:375)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:351)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:215)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:171)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:163)
> 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:56)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:294)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:960)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:293)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:196)
> 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:568)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:282)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:225)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:406)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main
> (Launcher.java:347)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Error assembling
> JAR
> at org.apache.maven.plugins.jar.AbstractJarMojo.createArchive
> (AbstractJarMojo.java:281)
> at org.apache.maven.plugins.jar.AbstractJarMojo.execute
> (AbstractJarMojo.java:305)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:137)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:370)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:351)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:215)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:171)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:163)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
>
[jira] [Created] (MJAR-294) adding module-info causes build to fail due to invalid date
Samael Bate created MJAR-294:
Summary: adding module-info causes build to fail due to invalid
date
Key: MJAR-294
URL: https://issues.apache.org/jira/browse/MJAR-294
Project: Maven JAR Plugin
Issue Type: Bug
Affects Versions: 3.3.0
Reporter: Samael Bate
I added a module-info.java to my project and found that the build was failing.
In the log output I found the following error:
{code:java}
date 1970-01-01T00:00:10Z is not within the valid range 1980-01-01T00:00:02Z to
2099-12-31T23:59:59Z {code}
This is odd and I have no idea what is trying to set a date to Jan 1st 1970 but
I'm positive that something about maven-jar-plugin and modular jars can get
broken somehow.
Simply renaming _module-info.java_ to _module-info.txt_ fixed the build but of
course I want to modularise the project.
I ran _mvn clean package -X_ here i the output:
{code:java}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-jar-plugin:3.3.0:jar (default-jar) on project
my-project: Error assembling JAR: Could not create modular JAR file. The JDK
jar tool exited with 1 -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
org.apache.maven.plugins:maven-jar-plugin:3.3.0:jar (default-jar) on project
my-project: Error assembling JAR
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
(MojoExecutor.java:375)
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
(MojoExecutor.java:351)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:215)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:171)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:163)
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:56)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:294)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:960)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:293)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:196)
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:568)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
(Launcher.java:282)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch
(Launcher.java:225)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
(Launcher.java:406)
at org.codehaus.plexus.classworlds.launcher.Launcher.main
(Launcher.java:347)
Caused by: org.apache.maven.plugin.MojoExecutionException: Error assembling JAR
at org.apache.maven.plugins.jar.AbstractJarMojo.createArchive
(AbstractJarMojo.java:281)
at org.apache.maven.plugins.jar.AbstractJarMojo.execute
(AbstractJarMojo.java:305)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
(DefaultBuildPluginManager.java:137)
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
(MojoExecutor.java:370)
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
(MojoExecutor.java:351)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:215)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:171)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:163)
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:56)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:294)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:960)
at org.apache.maven.cli.MavenCli.doMain
[jira] [Comment Edited] (MPLUGINTESTING-72) release 3.4.0
[ https://issues.apache.org/jira/browse/MPLUGINTESTING-72?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17800050#comment-17800050 ] Samael Bate edited comment on MPLUGINTESTING-72 at 12/23/23 1:03 PM: - How come this is closed, there's still no release that is targeting a maven 3.* release published in the last few years. After the 3.3.0 release in 2014, there's nothing until this year targeting alpha builds of Maven 4. Before focusing on supporting unreleased maven versions can't we get a release that's suitable for Maven 3.6.* I've been trying to get this since 2019 [https://github.com/apache/maven-plugin-testing/pull/8] MPLUGINTESTING-62 was (Author: singingbush): How come this is closed, there's still no release that is targeting a maven 3.* release published in the last few years. After the 3.3.0 release in 2014, there's nothing until this year targeting alpha builds of Maven 4. Before focusing on supporting unreleased maven versions can't we get a release that's suitable for Maven 3.6.* I've been trying to get this since 2019 https://github.com/apache/maven-plugin-testing/pull/8 > release 3.4.0 > - > > Key: MPLUGINTESTING-72 > URL: https://issues.apache.org/jira/browse/MPLUGINTESTING-72 > Project: Maven Plugin Testing > Issue Type: Wish >Reporter: Samael Bate >Priority: Major > > the master branch is passing all builds. There hasn't been a release since > 2014. What's the reasoning for not publishing a new release? There are > numerous dependency updates as well as documentation fixes. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MPLUGINTESTING-72) release 3.4.0
[ https://issues.apache.org/jira/browse/MPLUGINTESTING-72?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17800050#comment-17800050 ] Samael Bate commented on MPLUGINTESTING-72: --- How come this is closed, there's still no release that is targeting a maven 3.* release published in the last few years. After the 3.3.0 release in 2014, there's nothing until this year targeting alpha builds of Maven 4. Before focusing on supporting unreleased maven versions can't we get a release that's suitable for Maven 3.6.* I've been trying to get this since 2019 https://github.com/apache/maven-plugin-testing/pull/8 > release 3.4.0 > - > > Key: MPLUGINTESTING-72 > URL: https://issues.apache.org/jira/browse/MPLUGINTESTING-72 > Project: Maven Plugin Testing > Issue Type: Wish >Reporter: Samael Bate >Priority: Major > > the master branch is passing all builds. There hasn't been a release since > 2014. What's the reasoning for not publishing a new release? There are > numerous dependency updates as well as documentation fixes. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MPLUGINTESTING-72) release 3.4.0
[ https://issues.apache.org/jira/browse/MPLUGINTESTING-72?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17800932#comment-17800932 ] Samael Bate commented on MPLUGINTESTING-72: --- ok thanks, I've updated maven-plugin-testing-harness to 4.0.0-alpha-2 and after some initial pain with dependencies, mostly with the _org.apache.maven.reporting_ artifacts my plugin needs, I was able to get a build passing with a basic test. > release 3.4.0 > - > > Key: MPLUGINTESTING-72 > URL: https://issues.apache.org/jira/browse/MPLUGINTESTING-72 > Project: Maven Plugin Testing > Issue Type: Wish >Reporter: Samael Bate >Priority: Major > > the master branch is passing all builds. There hasn't been a release since > 2014. What's the reasoning for not publishing a new release? There are > numerous dependency updates as well as documentation fixes. -- This message was sent by Atlassian Jira (v8.20.10#820010)
