...BUT there seems to be some migration problem: we had one JIRA MRESOLVER for two GH reposes (resolver and resolver-ant-tasks). This will be fixed soon (ant tasks issues moved to proper GH repo).
So if commenting, please use the PR and not MRESOLVER JIRA nor the new GH issues in resolver Thanks T On Wed, Jun 18, 2025 at 10:46 AM Tamás Cservenák <ta...@cservenak.net> wrote: > > Hi Per, > > Yes, this is the ML. > > Also, seems https://issues.apache.org/jira/browse/MRESOLVER-718 > got migrated to https://github.com/apache/maven-resolver/issues/1458 > but am not involved into this migration, as it seems you commented on > JIRA _after_ migration :) > > For starters, thank you for your contribution! > Will get to it soon. > > T > > On Wed, Jun 18, 2025 at 10:36 AM Per Nyfelt <per.nyf...@nordnet.se> wrote: > > > > Hi, > > > > I hope this is the correct mailing list for this. I created a PR here > > https://github.com/apache/maven-resolver-ant-tasks/pull/56 It fixes the > > issue reported here: > > https://github.com/apache/maven-resolver-ant-tasks/pull/56 Essentially it > > does two things 1. Adds support for a dependencymanagement section in the > > ant build file 2. defines a new task (createPom) to generate (and register) > > a pom based on the information in the ant build file. Given this it is > > possible to define any type of dependencies in the ant build file > > (including using BOMs) and resolve, install, deploy etc. using the > > maven-resolver-ant-tasks. Best regards, Per --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
