[
https://issues.apache.org/jira/browse/MWRAPPER-155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephan Kölle updated MWRAPPER-155:
-----------------------------------
Description:
The developer build stability provided by {{mvnw}} is excellent, and I’d like
to suggest a small enhancement that aligns with its convenience.
By adding the following snippet to the {{mvnw}} script:
{code:java}
if [ -f ./.jabbarc ] && [ -f ./jabbaw ]; then
export $(./jabbaw env | grep JAVA_HOME)
fi{code}
This integrates with [[Jabba||https://github.com/Jabba-Team/jabba]
[https://github.com/Jabba-Team/jabba] []|https://github.com/Jabba-Team/jabba],
specifically its "install-less" variant
([[jabbaw||https://github.com/Jabba-Team/jabba/blob/main/jabbaw.md]
[https://github.com/Jabba-|https://github.com/Jabba-Team/jabba/blob/main/jabbaw.md)]
[Team/jabba/blob/main/jabbaw.md|https://github.com/Jabba-Team/jabba/blob/main/jabbaw.md)]
[]|https://github.com/Jabba-Team/jabba/blob/main/jabbaw.md]), to define a JDK
version via the {{.jabbarc}} configuration file.
This addition would make it easy to ensure a consistent JDK setup directly from
the {{mvnw}} script, which could be particularly useful for teams or projects
requiring precise JDK versioning without additional manual setup.
was:
The developer build stability provided by {{mvnw}} is excellent, and I’d like
to suggest a small enhancement that aligns with its convenience.
By adding the following snippet to the {{mvnw}} script:
if [ -f ./.jabbarc ] && [ -f ./jabbaw ]; then
export $(./jabbaw env | grep JAVA_HOME)
fi
{{}}
This integrates with [[Jabba||https://github.com/Jabba-Team/jabba]
[https://github.com/Jabba-Team/jabba] []|https://github.com/Jabba-Team/jabba],
specifically its "install-less" variant
([[jabbaw||https://github.com/Jabba-Team/jabba/blob/main/jabbaw.md]
[https://github.com/Jabba-|https://github.com/Jabba-Team/jabba/blob/main/jabbaw.md)]
[Team/jabba/blob/main/jabbaw.md|https://github.com/Jabba-Team/jabba/blob/main/jabbaw.md)]
[]|https://github.com/Jabba-Team/jabba/blob/main/jabbaw.md]), to define a JDK
version via the {{.jabbarc}} configuration file.
This addition would make it easy to ensure a consistent JDK setup directly from
the {{mvnw}} script, which could be particularly useful for teams or projects
requiring precise JDK versioning without additional manual setup.
> add jabbaw to mvnw
> ------------------
>
> Key: MWRAPPER-155
> URL: https://issues.apache.org/jira/browse/MWRAPPER-155
> Project: Maven Wrapper
> Issue Type: Wish
> Components: Maven Wrapper Scripts
> Affects Versions: 3.3.2
> Reporter: Stephan Kölle
> Priority: Trivial
>
> The developer build stability provided by {{mvnw}} is excellent, and I’d like
> to suggest a small enhancement that aligns with its convenience.
> By adding the following snippet to the {{mvnw}} script:
> {code:java}
> if [ -f ./.jabbarc ] && [ -f ./jabbaw ]; then
> export $(./jabbaw env | grep JAVA_HOME)
> fi{code}
>
>
> This integrates with [[Jabba||https://github.com/Jabba-Team/jabba]
> [https://github.com/Jabba-Team/jabba]
> []|https://github.com/Jabba-Team/jabba], specifically its "install-less"
> variant ([[jabbaw||https://github.com/Jabba-Team/jabba/blob/main/jabbaw.md]
> [https://github.com/Jabba-|https://github.com/Jabba-Team/jabba/blob/main/jabbaw.md)]
>
> [Team/jabba/blob/main/jabbaw.md|https://github.com/Jabba-Team/jabba/blob/main/jabbaw.md)]
> []|https://github.com/Jabba-Team/jabba/blob/main/jabbaw.md]), to define a
> JDK version via the {{.jabbarc}} configuration file.
> This addition would make it easy to ensure a consistent JDK setup directly
> from the {{mvnw}} script, which could be particularly useful for teams or
> projects requiring precise JDK versioning without additional manual setup.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
