# \[ANN\] MlFront - A Java-like package system for OCaml

**URL:** <https://discuss.ocaml.org/t/ann-mlfront-a-java-like-package-system-for-ocaml/15072>\
**Category:** Ecosystem\
**Tags:** dkcoder, mlfront, announce\
**Created:** [August 2, 2024, 4:41pm UTC](https://discuss.ocaml.org/t/ann-mlfront-a-java-like-package-system-for-ocaml/15072 "2024-08-02T16:41:32Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![edwin](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ocaml.org/edwin/32/627_2.png) [@edwin](https://discuss.ocaml.org/u/edwin)\
**Post date:** [August 2, 2024, 8:42pm UTC](https://discuss.ocaml.org/t/ann-mlfront-a-java-like-package-system-for-ocaml/15072/2 "2024-08-02T20:42:31Z")

</div>

The inconsistent naming across various build and packaging systems in OCaml is a real problem, and source of confusion for newcomers to a project.

I think there have been attempts at solving related problems in the past, under the “namespacing” umbrella: [Previous discussions on namespaces? - #3 by yawaramin](https://discuss.ocaml.org/t/previous-discussions-on-namespaces/3318/3) [https://gallium.inria.fr/~scherer/namespaces/spec.pdf](https://gallium.inria.fr/~scherer/namespaces/spec.pdf)

I haven’t compared the proposals in detail.

There has also been some activity around better package management integration into Dune too, but there is probably still a long way to go: [OCaml Platform Newsletter - June 2024 - HackMD](https://hackmd.io/@ocaml/rkMi31YDA#Dune-Exploring-Package-Management-in-Dune-W4)

---

_[View the full topic](https://discuss.ocaml.org/t/ann-mlfront-a-java-like-package-system-for-ocaml/15072)._