trocar LFS por releases about jfstmerge HOT 13 OPEN

@jvcoutinho do you have any step-by-step guide on how the generate the release (the new binary files, installer, and so on...) ?

from jfstmerge.

@jvcoutinho is the procedure detailed in the README?

from jfstmerge.

@jvcoutinho can we close this?

from jfstmerge.

@jvcoutinho can we close this?

from jfstmerge.

@pauloborba yes.

from jfstmerge.

@jvcoutinho that's important and should be in the README

from jfstmerge.

Fine! I will put there.

Before that, I would like for us to discuss an idea I've had. Currently, the release generation process is very manual. One has to manually build the code, inject it in the installer framework and push it to Github. The installer has an option to check for updates, but I couldn't use it with Github's releases, as far as I remember.

How about if the installation was included in the s3m's binary, like a script? One could invoke with
java -jar jFSTMerge.jar --integrate-with-git, for example. This way, we can make the release generation automatic due to Travis. Instead of pushing only the binary, we could push a zip containing the test files also.

from jfstmerge.

@jvcoutinho I like the idea of automating the whole process, but I'm not sure about adding the release generation process as an s3m command line option. What would be the drawback of implementing that as a separate script, say s3mIntegrateWithGit.jar?

@guilhermejccavalcanti what's your opinion here?

from jfstmerge.

@jvcoutinho None, it just needs to be accessible from the main repository.

from jfstmerge.

@guilhermejccavalcanti ?

from jfstmerge.

from jfstmerge.

@jvcoutinho relatos de problema no instalador:

não sai dessa tela.

from jfstmerge.

@jvcoutinho alguma dica do que possa ser isso?

from jfstmerge.