You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't know the rationale behind tnoodle's custom build system, and I guess changing to another one is more trouble than it's worth, but here I go anyways:
It be very useful if tnoodle was maven- or gradle-based, allowing for easy integration into other programs. My concrete usecase is including the scramble generation as a library in another java application, where including it into the classpath is currently done manually and has some cumbersome steps.
The text was updated successfully, but these errors were encountered:
Hey @Felk. There isn't a particularly great reason why I built tmt instead of using maven (I'm not sure if gradle was even an option back then). I would be supportive of changing TNoodle to use gradle, but I'm not sure it's worth the effort. Just because we have our own build system doesn't mean we can't make it easy for you to to use TNoodle in another java application, though! What can we do do make that better?
I don't know the rationale behind tnoodle's custom build system, and I guess changing to another one is more trouble than it's worth, but here I go anyways:
It be very useful if tnoodle was maven- or gradle-based, allowing for easy integration into other programs. My concrete usecase is including the scramble generation as a library in another java application, where including it into the classpath is currently done manually and has some cumbersome steps.
The text was updated successfully, but these errors were encountered: