A useful answer to your question would involve contacting the maintainer of the FreeBSD Eclipse port, who would probably have some insight into the division of labour. My guess is that the FreeBSD ports picks up the Linux port compilation infrastructure as maintained by the Eclipse Foundation, and makes a relatively small number of changes pertaining to different system locations and support libraries (and perhaps substitutes Clang for GCC).

If Oomph requires basically the same handling as Eclipse itself, but with different Java artifacts, it's probably a fairly simple matter to fork the Eclipse port.

However, if we have to dig into the Java underbelly, I don't have the expertise in the Java ecosystem to do this work effectively, and there's no guarantee the FreeBSD port maintainer is in the mood to take on an extra project, so at that point we would need somebody on the Oomph side willing to provide a bit of hand-holding.

1. Is Oomph a somewhat or radically different beast than Eclipse itself?

2. Is there enough motivation within the Oomph community to help us through the kind of split-personality difficulties an enthusiastic, not-very-good Java person collaborating with a not-really-my-own-project person (e.g. the current FreeBSD Eclipse port maintainer) would likely encounter?

Sometimes when you gather four blind men around an elephant, it somehow all works out. Sometimes it doesn't. So I'm trying to obtain a first impression here whether this particular unladen elephant is African or European.