ghost commented 8 years ago

I've been spending the past day or so building a set of gradle and capsule build files and configurations to make it require less effort for people to distribute and contribute to fastDMM

I however have a few remaining questions before i submit this PR.

Should we distribute a windows executable that has been generated trough launch4j which contains all requirements to run FastDMM.
Do we want to distribute a platform independent jar file that has been generates trough capsule which contains all requirements and it's own JRE to run FastDMM.
Do we want to automate this process using travis allowing pull requests to be tested before they are merged?

PJB3005 commented 8 years ago

Do we want to automate this process using travis allowing pull requests to be tested before they are merged?

I think that's definitely a yes no matter what.

d34d10cc commented 8 years ago

I am completely positive on the Travis one. I'm leaning towards multiplatform, although most (all?) BYOND users use Windows. So, my vote goes to the independent JAR file.

ghost commented 8 years ago

@CrAzYPiLoT-SS13 we can easily do both.

d34d10cc commented 8 years ago

That would be ideal, in that case.

ghost commented 8 years ago

5 has been opened, i decided to ditch the .exe generation as it was causing some issues, this should make building and running this a lot easier :+1:

monster860 / FastDMM

Questions regarding packaging. #4

5 has been opened, i decided to ditch the .exe generation as it was causing some issues, this should make building and running this a lot easier :+1: