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

2019-08-15 Thread Samael Bate (JIRA)


 [ 
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] [Updated] (MPLUGINTESTING-62) use maven API 3.6.0 and Plexus 2.0.0

2019-08-15 Thread Samael Bate (JIRA)


 [ 
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] [Created] (MPLUGINTESTING-64) broken links on website

2019-08-15 Thread Samael Bate (JIRA)
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] [Commented] (MPLUGINTESTING-63) AbstractMojoTestCase should return correct type

2019-08-11 Thread Samael Bate (JIRA)


[ 
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

2019-08-11 Thread Samael Bate (JIRA)
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] (MPLUGINTESTING-62) target maven 3.6.0 API

2019-08-11 Thread Samael Bate (JIRA)
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] (MCOMPILER-376) Change default source/target to 1.7 (new minimum for JDK 12)

2019-08-11 Thread Samael Bate (JIRA)


[ 
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] (MPOM-222) update target JDK from 6 to 8

2019-08-11 Thread Samael Bate (JIRA)
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] (MPLUGINTESTING-61) Require Java 7

2019-08-11 Thread Samael Bate (JIRA)


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