I forgot: last but not least
we have consistency issues with parent POM and dependencyManagement POM import
downloads when repositories are defined in projects pom.xml
see https://issues.apache.org/jira/browse/MNG-6772 and linked issues
while working on all this dependencies management, it would
my own quick opinion:
1. I did not review the full email thread, so is
https://github.com/strohmattenverleger/maven/blob/MNG-4530/Dependency-Overrides.md
still the current state of the idea?
2. can you add concrete examples, please?
3. given the impact, I fear this may be for Maven 5: we clear
dependabot[bot] opened a new pull request #25:
URL: https://github.com/apache/maven-gh-actions-shared/pull/25
Bumps [actions/setup-java](https://github.com/actions/setup-java) from 2.4.0
to 2.5.0.
Release notes
Sourced from https://github.com/actions/setup-java/releases";>actions/
yliu224 commented on issue #514:
URL: https://github.com/apache/maven-mvnd/issues/514#issuecomment-999164121
Found the work around. Just unset the environment parameter first then pass
the parameter in the command line.
1. ```❯ unset JAVA_TOOL_OPTIONS```
2. ```❯ mvnd -Djava.net.pref
+1
Reproducible Build checked: reference build was done with JDK 8 on Windows
Regards,
Hervé
Le dimanche 19 décembre 2021, 20:31:58 CET Michael Osipov a écrit :
> Hi,
>
> We solved 6 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628&ve
> rsion=12350595
>
> Th
+1
Reproducible Build checked: reference build was done with JDK 8 on Windows
Regards,
Hervé
Le dimanche 19 décembre 2021, 19:46:28 CET Michael Osipov a écrit :
> Hi,
>
> We solved 5 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318122&ve
> rsion=12351097
>
> Th
Hi,
I have a project which includes the enforcer plugin with a rule to check if
some file exist. With the version 3.0.0-M3 this works fine but with version
3.0.0 I get the error message:
Some required files are missing:
/Users/xxx/workspace/mywork/project/../scripts/mykey.secure
configuration in
Hi,
For what it's worth, I would really like to see
https://issues.apache.org/jira/browse/SUREFIRE-1935 /
https://github.com/apache/maven-surefire/pull/389 merged. It adds support
for the SessionLauncher API in JUnit 5. We rely heavily on this API to
prevent expensive components being recreated fo
+1 for 3.0.0,
+1 to drop the roadmap page or keep it an internal page
+1 for java 8 requirement in the doc (and in code if needed but this is not
required)
>From what I reviewed no PR merge is strictly needed to do a 3.0.0 so we can
go as soon as we have a release manager with enough karma IMHO.
Il giorno mar 21 dic 2021 alle ore 13:49 Slawomir Jaranowski <
s.jaranow...@gmail.com> ha scritto:
> Hi,
>
> Summary for today.
>
> Decisions waiting to take:
>
> 1. What version do we want to release 3.0.0 or the next milestone?
>
3.0.0 or 3.0.1 (this should be > 3.0.0Mxx) is good for me
> 2.
Hi,
Summary for today.
Decisions waiting to take:
1. What version do we want to release 3.0.0 or the next milestone?
2. What with the road map on the first page ...?
3. JDK 8 as target - without refactor - will it be acceptable? - cause to
stop upgrading some dependencies like commons-io
4. Fina
11 matches
Mail list logo
