slawekjaranowski commented on pull request #1:
URL:
https://github.com/apache/maven-wrapper-plugin/pull/1#issuecomment-980633392
Of course, `wrapperUrl` in properties is wrong, but release (even staging)
should resolve it
```
slawekjaranowski commented on pull request #1:
URL:
https://github.com/apache/maven-wrapper-plugin/pull/1#issuecomment-980632912
in `maven-wrapper`
```
mvn clean install -P run-its
```
and in other project
```
mvn
slawekjaranowski commented on pull request #1:
URL:
https://github.com/apache/maven-wrapper-plugin/pull/1#issuecomment-980598578
@hboutemy great job.
I've tested by:
- build project - unit and IT test are executed, plugin and artifacts are
installed
- use in another project
slawekjaranowski commented on pull request #1:
URL:
https://github.com/apache/maven-wrapper-plugin/pull/1#issuecomment-970426760
From wrapper perspective should not be important what `mvn` command is and
what happen inside `mvn`.
We should assume that `mvn` command from Maven
slawekjaranowski commented on pull request #1:
URL:
https://github.com/apache/maven-wrapper-plugin/pull/1#issuecomment-952590460
I think that running `mvn` from Maven distribution will be better ...
Some change to maven scripts can be depend on Maven core code like:
slawekjaranowski commented on pull request #1:
URL:
https://github.com/apache/maven-wrapper-plugin/pull/1#issuecomment-951775639
Another idea ... why not simply call `mvn*` scripts from Maven distribution
... of course after needed job for wrapper like downloading
In this case code
