Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mavenize JPPF #37

Open
lolocohen opened this issue Nov 20, 2021 · 0 comments · May be fixed by #38
Open

Mavenize JPPF #37

lolocohen opened this issue Nov 20, 2021 · 0 comments · May be fixed by #38
Assignees
Labels
enhancement New feature or request
Projects
Milestone

Comments

@lolocohen
Copy link
Member

What should be improved

For a very long time now, the JPPF build has been done with Apache Ant.
Ant works great, but the big issue is of course dependency management. I thought we'd be able to manage it even for the long run, but today it has become costly, in terms of maintenance and time spent, not to have an autpmated dependency managelent system.

Furthermore, JPPF artifacts are deployed to Maven Central, to kae them easily accessible and deployable as dependencies in other applications.

For these reasons, I now believe we should convert the JPPF build to Maven.
I have already started the work, and it is far from trivial. In particular, the test framework and associated tests require a lot of work to function properly.

In which release

JPPF 6.3

@lolocohen lolocohen added the enhancement New feature or request label Nov 20, 2021
@lolocohen lolocohen added this to the JPPF 6.3 milestone Nov 20, 2021
@lolocohen lolocohen self-assigned this Nov 20, 2021
@lolocohen lolocohen added this to To do in JPPF-board via automation Nov 20, 2021
@lolocohen lolocohen linked a pull request Nov 20, 2021 that will close this issue
@lolocohen lolocohen linked a pull request Nov 20, 2021 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Development

Successfully merging a pull request may close this issue.

1 participant