[jira] [Created] (MNG-7907) Harmonize window title - windows
Jurrian Fahner created MNG-7907: --- Summary: Harmonize window title - windows Key: MNG-7907 URL: https://issues.apache.org/jira/browse/MNG-7907 Project: Maven Issue Type: New Feature Environment: windows Reporter: Jurrian Fahner In the mvnDebug script the window title is updated during the script. It doesn't set back the changed window title back to the original window title. But it is strange that only with the mvnDebug script the title is updated, it would be nice to have that also with other scripts as well. In this way we can monitor when the maven command is ended succesfully. This issue currently only focuses on windows, this means the following default terminals will be supported: * Windows Terminal * Windows Powershell * Command Prompt I have not yet formed an idea on what should be set to as an title, but that is open for brainstorm. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7541) Native support for PowerShell to start Maven
[ https://issues.apache.org/jira/browse/MNG-7541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17614282#comment-17614282 ] Jurrian Fahner commented on MNG-7541: - [~michael-o] Shall I create a PR based on the implementation for mvn.ps1? We also need to take care of the mvnw.cmd. Do we want to have it in one PR or can we implement the functionality in several PRs? > Native support for PowerShell to start Maven > > > Key: MNG-7541 > URL: https://issues.apache.org/jira/browse/MNG-7541 > Project: Maven > Issue Type: Improvement > Components: Command Line >Affects Versions: 3.8.3 > Environment: windows 10 / 11 >Reporter: Jurrian Fahner >Priority: Trivial > Labels: Script, Windows10, Windows11 > > Maven has two files in the bin dir: > ||command||its use|| > |mvn|POSIX shell| > |mvn.cmd|cmd.exe| > On windows there are two ways to write scripts, by using cmd.exe or using > powershell. > If you enter mvn in powershell it will look for `mvn.ps1` on the PATH first. > If it doesn't find anything it will execute `mvn.cmd` as fall-back. > When running maven for starting a server for development purposes and you do > ctrl-c to exit the server it will ask the question: Terminate batch job (Y/N)? > As far as I know it is default behaviour of cmd.exe. > Well if I don't want to terminate, I wouldn't press ctrl-c. ;) > It is not the case (as far as I know that Microsoft is going to deprecate > cmd.exe in favor of powershell: > [https://devblogs.microsoft.com/commandline/rumors-of-cmds-death-have-been-greatly-exaggerated/] > Allthough I think it would be a good move for maven to have also a powershell > script as well... It is possible to integrate elegant support for native help > in powershell, `get-help mvn`. > But it also increases the maintenance effort as well. I don't know whether > this cost outweigh the benefits, though... > By the way I would happy to contribute if it is appreciated. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7541) Native support for powershell to start maven
[ https://issues.apache.org/jira/browse/MNG-7541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17606731#comment-17606731 ] Jurrian Fahner commented on MNG-7541: - * The readability of the script can be improved because powershell is more feature rich. * It enables writing unit tests (this will improve readability and may also lower the barrier to entry): [https://pester.dev/] * Powershell is available since windows 7. Windows 10 and/or 11 are nowadays the base for many developer laptops/PCs. * We can get rid of cmd.exe script and replace it with powershell (which lowers maintainability effort), the mvn.cmd script will hold something like: PowerShell.exe -command mvn.ps1 It will likely not have a life altering impact probably... ;) > Native support for powershell to start maven > > > Key: MNG-7541 > URL: https://issues.apache.org/jira/browse/MNG-7541 > Project: Maven > Issue Type: Improvement > Components: Command Line >Affects Versions: 3.8.3 > Environment: windows 10 / 11 >Reporter: Jurrian Fahner >Priority: Trivial > Labels: Script, Windows10, Windows11 > > Maven has two files in the bin dir: > ||command||its use|| > |mvn|POSIX shell| > |mvn.cmd|cmd.exe| > On windows there are two ways to write scripts, by using cmd.exe or using > powershell. > If you enter mvn in powershell it will look for `mvn.ps1` on the PATH first. > If it doesn't find anything it will execute `mvn.cmd` as fall-back. > When running maven for starting a server for development purposes and you do > ctrl-c to exit the server it will ask the question: Terminate batch job (Y/N)? > As far as I know it is default behaviour of cmd.exe. > Well if I don't want to terminate, I wouldn't press ctrl-c. ;) > It is not the case (as far as I know that Microsoft is going to deprecate > cmd.exe in favor of powershell: > [https://devblogs.microsoft.com/commandline/rumors-of-cmds-death-have-been-greatly-exaggerated/] > Allthough I think it would be a good move for maven to have also a powershell > script as well... It is possible to integrate elegant support for native help > in powershell, `get-help mvn`. > But it also increases the maintenance effort as well. I don't know whether > this cost outweigh the benefits, though... > By the way I would happy to contribute if it is appreciated. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MNG-7541) Native support for powershell to start maven
Jurrian Fahner created MNG-7541: --- Summary: Native support for powershell to start maven Key: MNG-7541 URL: https://issues.apache.org/jira/browse/MNG-7541 Project: Maven Issue Type: Improvement Components: Command Line Affects Versions: 3.8.3 Environment: windows 10 / 11 Reporter: Jurrian Fahner Maven has two files in the bin dir: ||command||it's use|| |mvn|bash| |mvn.cmd|cmd.exe| On windows there are two ways to write scripts, by using cmd.exe or using powershell. If you enter mvn in powershell it will look for `mvn.ps1` on the PATH first. If it doesn't find anything it will execute `mvn.cmd` as fall-back. When running maven for starting a server for development purposes and you do ctrl-c to exit the server it will ask the question: Terminate batch job (Y/N)? As far as I know it is default behaviour of cmd.exe. Well if I don't want to terminate, I wouldn't press ctrl-c. ;) It is not the case (as far as I know that Microsoft is going to deprecate cmd.exe in favor of powershell: [https://devblogs.microsoft.com/commandline/rumors-of-cmds-death-have-been-greatly-exaggerated/] Allthough I think it would be a good move for maven to have also a powershell script as well... It is possible to integrate elegant support for native help in powershell, `get-help mvn`. But it also increases the maintenance effort as well. I don't know whether this cost outweigh the benefits, though... By the way I would happy to contribute if it is appreciated. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MARCHETYPES-61) Update quickstart to use JUnit 5
[
https://issues.apache.org/jira/browse/MARCHETYPES-61?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17541118#comment-17541118
]
Jurrian Fahner commented on MARCHETYPES-61:
---
[~mthmulders] my advice would be to rephrase this issue to something like:
Simplify junit depenedencies in quickstart.
> Update quickstart to use JUnit 5
>
>
> Key: MARCHETYPES-61
> URL: https://issues.apache.org/jira/browse/MARCHETYPES-61
> Project: Maven Archetype Bundles
> Issue Type: Improvement
> Components: Maven Quickstart Archetype
>Affects Versions: 1.3
>Reporter: Dmitry Timofeev
>Priority: Minor
>
> Update quickstart archetype to generate a project using JUnit 5, the next
> version of the most popular testing framework.
> Currently one has to include _at least_ two dependencies on JUnit 5 artefacts
> to enable surefire to run them: junit-jupiter-api and junit-jupiter-engine.
> Possible structure of dependencies:
> {code:java}
>
>
>
> org.junit
> junit-bom
> 5.3.1
> pom
> import
>
>
>
>
>
> org.junit.jupiter
> junit-jupiter-api
> test
>
>
> org.junit.jupiter
> junit-jupiter-engine
> test
>
>
>
> org.junit.jupiter
> junit-jupiter-params
> test
>
> {code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (MARCHETYPES-61) Update quickstart to use JUnit 5
[
https://issues.apache.org/jira/browse/MARCHETYPES-61?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17541094#comment-17541094
]
Jurrian Fahner commented on MARCHETYPES-61:
---
Archetype has been already updated in MARCHETYPES-70., but has not been
released yet.
However the change was already a while ago.
So there is no need to have junit-api and junit engine (which is still part of
the archetype), the following should be enough:
{code:xml}
org.junit.jupiter
junit-jupiter
5.8.2
test
{code}
[~dt] if you want a challenge, you can create a PR to reflect the above
change... ;)
> Update quickstart to use JUnit 5
>
>
> Key: MARCHETYPES-61
> URL: https://issues.apache.org/jira/browse/MARCHETYPES-61
> Project: Maven Archetype Bundles
> Issue Type: Improvement
> Components: Maven Quickstart Archetype
>Affects Versions: 1.3
>Reporter: Dmitry Timofeev
>Priority: Minor
>
> Update quickstart archetype to generate a project using JUnit 5, the next
> version of the most popular testing framework.
> Currently one has to include _at least_ two dependencies on JUnit 5 artefacts
> to enable surefire to run them: junit-jupiter-api and junit-jupiter-engine.
> Possible structure of dependencies:
> {code:java}
>
>
>
> org.junit
> junit-bom
> 5.3.1
> pom
> import
>
>
>
>
>
> org.junit.jupiter
> junit-jupiter-api
> test
>
>
> org.junit.jupiter
> junit-jupiter-engine
> test
>
>
>
> org.junit.jupiter
> junit-jupiter-params
> test
>
> {code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Created] (ARCHETYPE-627) Release maven archetypes
Jurrian Fahner created ARCHETYPE-627: Summary: Release maven archetypes Key: ARCHETYPE-627 URL: https://issues.apache.org/jira/browse/ARCHETYPE-627 Project: Maven Archetype Issue Type: Task Components: Plugin Affects Versions: 3.2.2 Reporter: Jurrian Fahner Last release of maven archetypes was done in 2018. Since version 1.4 there have been 20 commits, which are not available when you use org.apache.maven.plugins:maven-archetype-plugin. I think that we first need to release 1.5 and then release 3.2.2 of the plugin. So it can be part of the next minor release of maven. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (MARCHETYPES-70) Quickstart support for junit 5 and java 9+
[
https://issues.apache.org/jira/browse/MARCHETYPES-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17284415#comment-17284415
]
Jurrian Fahner commented on MARCHETYPES-70:
---
[~hboutemy] Do you know when there will be a new release created and published
for the maven archetypes? I would like to use the new
maven-archetype-quickstart.
> Quickstart support for junit 5 and java 9+
> --
>
> Key: MARCHETYPES-70
> URL: https://issues.apache.org/jira/browse/MARCHETYPES-70
> Project: Maven Archetype Bundles
> Issue Type: Improvement
> Components: Maven Quickstart Archetype
>Affects Versions: 1.3, 1.4
>Reporter: Jurrian Fahner
>Assignee: Enrico Olivelli
>Priority: Minor
> Fix For: 1.5
>
>
> Quickstart archetype is outdated due to the support for java versions below 9
> and junit 4.
> The changes needs to be made backwards compatible in order to avoid breaking
> changes for legacy projects.
> For the support of java 9+ the java version tag must change from:
> {code:xml}
>
> 1.8
> 1.8
> {code}
> to:
> {code:xml}
>
> 11
> {code}
> For junit 5 support it is needed to add junit-jupiter-api and the vintage
> plugin, to add support for large older projects (with old junit tests in it).
> Example for dependencies for junit 5 it will look like:
> {code:xml}
>
> org.junit.jupiter
> junit-jupiter-api
> 5.2.2
> test
>
>
> org.junit.jupiter
> junit-jupiter-engine
> 5.2.2
> test
>
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (MARCHETYPES-70) Quickstart support for junit 5 and java 9+
[
https://issues.apache.org/jira/browse/MARCHETYPES-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jurrian Fahner updated MARCHETYPES-70:
--
Docs Text: Quickstart supports java 9+ and junit 5. To specify the java
version and junit version set the properties javaCompilerVersion (default =
1.7) and junitVersion (default = 4.13.1) respectively.
> Quickstart support for junit 5 and java 9+
> --
>
> Key: MARCHETYPES-70
> URL: https://issues.apache.org/jira/browse/MARCHETYPES-70
> Project: Maven Archetype Bundles
> Issue Type: Improvement
> Components: Maven Quickstart Archetype
>Affects Versions: 1.3, 1.4
>Reporter: Jurrian Fahner
>Priority: Minor
>
> Quickstart archetype is outdated due to the support for java versions below 9
> and junit 4.
> The changes needs to be made backwards compatible in order to avoid breaking
> changes for legacy projects.
> For the support of java 9+ the java version tag must change from:
> {code:xml}
>
> 1.8
> 1.8
> {code}
> to:
> {code:xml}
>
> 11
> {code}
> For junit 5 support it is needed to add junit-jupiter-api and the vintage
> plugin, to add support for large older projects (with old junit tests in it).
> Example for dependencies for junit 5 it will look like:
> {code:xml}
>
> org.junit.jupiter
> junit-jupiter-api
> 5.2.2
> test
>
>
> org.junit.jupiter
> junit-jupiter-engine
> 5.2.2
> test
>
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (MARCHETYPES-70) Quickstart support for junit 5 and java 9+
Jurrian Fahner created MARCHETYPES-70:
-
Summary: Quickstart support for junit 5 and java 9+
Key: MARCHETYPES-70
URL: https://issues.apache.org/jira/browse/MARCHETYPES-70
Project: Maven Archetype Bundles
Issue Type: Improvement
Components: Maven Quickstart Archetype
Affects Versions: 1.4, 1.3
Reporter: Jurrian Fahner
Quickstart archetype is outdated due to the support for java versions below 9
and junit 4.
The changes needs to be made backwards compatible in order to avoid breaking
changes for legacy projects.
For the support of java 9+ the java version tag must change from:
{code:xml}
1.8
1.8
{code}
to:
{code:xml}
11
{code}
For junit 5 support it is needed to add junit-jupiter-api and the vintage
plugin, to add support for large older projects (with old junit tests in it).
Example for dependencies for junit 5 it will look like:
{code:xml}
org.junit.jupiter
junit-jupiter-api
5.2.2
test
org.junit.jupiter
junit-jupiter-engine
5.2.2
test
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
