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.
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