maven module separation about javet HOT 3 OPEN

This is the decision that I've being thinking of for long time, but haven't convinced myself on.

The current approach only requires one dependency. A one line config can exclude the duplicated code from 2+ dependencies.

The new approach requires at least 2 dependencies. That adds more work to the users and to me because I'll have to package all of them separately. As the release publishing process is not completely automated, I'll spend 2x-3x more time on that. Please consider I've been doing that for free for many years.

As end users, curl + zip commands can simply help build out the ideal package at will, as javet-core is designed for that. That's a one-time set up in the CI/CD systems.

from javet.

Thank you.
Full publishing automation would be of great help for yourself of course.

Don't get me wrong: I highly appreciate your great work!

I will consider implementing your proposal in our CI/CD pipeline.

from javet.

Thank you.

Some other users also tweak their CI/CD systems this way.

Complete automation currently is impossible for me.

1. Some OS / CPU Arch require special build env and process that github doesn't support.
2. I don't have the resource to set up everything locally.

from javet.