[ 
https://issues.apache.org/jira/browse/MRELEASE-897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16648532#comment-16648532
 ] 

Carsten Klein edited comment on MRELEASE-897 at 10/12/18 10:41 PM:
-------------------------------------------------------------------

[~michael-o] OFFTOPIC: you may have discussed this already, but maven-parent@33 
is still relying on java 6 for both the sources and the compiled target, is 
this feasible? May we move on to newer versions of the Java language? Yet, the 
maven-release plugin already makes use of features of version 7, namely 
java.util.Objects and others.

I mean, maven, the premier build management tool should be a spear head when it 
comes to integrating new features of the language, should it not?

I would be willing in helping out in migrating existing plugins and also the 
maven core to at least support the newest language features by resolving any 
incompatibilities with say Java 8/9, at least.

Also, migrating from junit4 to the newest junit5 must be a mandatory step.


was (Author: silkentrance):
[~michael-o] OFFTOPIC: you may have discussed this already, but maven-parent@33 
is still relying on java 6 for both the sources and the compiled target, is 
this feasible? May we move on to newer versions of the Java language?

I mean, maven, the premier build management tool should be a spear head when it 
comes to integrating new features of the language, should it not?

I would be willing in helping out in migrating existing plugins and also the 
maven core to at least support the newest language features by resolving any 
incompatibilities with say Java 8/9, at least.

Also, migrating from junit4 to the newest junit5 must be a mandatory step.

> support multiple release versions
> ---------------------------------
>
>                 Key: MRELEASE-897
>                 URL: https://issues.apache.org/jira/browse/MRELEASE-897
>             Project: Maven Release Plugin
>          Issue Type: Improvement
>            Reporter: Romain Manni-Bucau
>            Priority: Major
>
> In some project multiple versions are used (tomee release = tomee + openejb 
> releases for instance). It is not always possible to split the project in sub 
> projects and then it is not possible to use maven release plugin. Idea would 
> be to support a whitelist of artifacts (a list of patterns would be great).
> {code}
> <releaseVersions>
>   <releaseVersion>org.superbiz.component:*:1.0.1</releaseVersion>
>   <releaseVersion>org.superbiz.component:*:4.5.8</releaseVersion>
> </releaseVersions>
> {code}
> For instance or even:
> {code}
> <releaseVersions>
>   
> <releaseVersion>org.superbiz.component:*:@major.@minor.@patch</releaseVersion>
>   <releaseVersion>org.superbiz.component:*:(@major + 
> 3).@minor.@patch</releaseVersion>
> </releaseVersions>
> {code}
> to avoid to change it for each release.
> This of course would imply the CLI to ask for the multiple versions and not 
> only one even when autoSubModules is set to true (it would just group by 
> versions)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to