On Sat, Jan 7, 2023 at 10:13 AM Eric Bresie <ebre...@gmail.com> wrote:
> > On Sat, Dec 31, 2022 at 11:18 AM Ernie Rael <err...@raelity.com> wrote: > > My solution, considering that ant is essentially deprecated in NetBeans, >> was to convert projects to Maven or Gradle. > > Well when working new projects the preference seems to be "not ant" but what about existing ant projects (i.e. Netbeans)? That is a bigger philosophical/paradigm change here. Are there any longer term plans to migrate the Netbeans codebase build from ant to something other (Maven or Gradle)? It seems like if changed then handling the "external" dependencies can be handled a little easier via the maven or gradle means using the applicable repos (except for any legacy dependencies no longer available) It may allow flexibility to use the plugins available (i.e. for quality, security, etc. checks) in the process. I know there was a "Mavenized" branch of contribs items available (1) at some point, but not sure anything further came of it after that. Maybe as an interim, there are "maven" plugins and ways to allow usage of "ant" tasks as part of the migration process (2),(3),(4),(5) . Maybe some initial basic maven poms can be introduced and leverage on the existing ant and over time convert clusters or items from ant to say maven. Or leveraging gradle (6). Thoughts? Eric Bresie ebre...@gmail.com (1) https://github.com/timboudreau/netbeans-contrib (2) https://stackoverflow.com/questions/1456901/how-to-wrap-an-ant-build-with-maven (3) https://maven.apache.org/guides/mini/guide-using-ant.html (4) https://maven.apache.org/plugins/maven-antrun-plugin/ (5) https://books.sonatype.com/mcookbook/reference/ch04s03.html (6) https://docs.gradle.org/current/userguide/ant.html
