[jira] [Commented] (MPLUGINTESTING-62) use maven API 3.6.0 and Plexus 2.0.0

2024-05-23 Thread ASF GitHub Bot (Jira)


[ 
https://issues.apache.org/jira/browse/MPLUGINTESTING-62?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17848933#comment-17848933
 ] 

ASF GitHub Bot commented on MPLUGINTESTING-62:
--

gnodet closed pull request #8: [MPLUGINTESTING-62] target maven 3.6.0 and 
Plexus 2.0.0
URL: https://github.com/apache/maven-plugin-testing/pull/8




> 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.10#820010)


[jira] [Commented] (MPLUGINTESTING-62) use maven API 3.6.0 and Plexus 2.0.0

2023-12-23 Thread ASF GitHub Bot (Jira)


[ 
https://issues.apache.org/jira/browse/MPLUGINTESTING-62?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17800051#comment-17800051
 ] 

ASF GitHub Bot commented on MPLUGINTESTING-62:
--

SingingBush opened a new pull request, #8:
URL: https://github.com/apache/maven-plugin-testing/pull/8

   pretty frustrating that in 2019 people are still targeting ancient Java 
versions. In this pull request I've set JDK 8 as the target and also updated to 
a more recent maven api level and updated junit to the newer 
`org.junit.vintage:junit-vintage-engine` equivelant.
   
   Any change of a new release? 3.3.0 was released years ago




> 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.10#820010)


[jira] [Commented] (MPLUGINTESTING-62) use maven API 3.6.0 and Plexus 2.0.0

2022-04-25 Thread Samael Bate (Jira)


[ 
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)