You are hilarious… for one thing we are talking about users who would prefer to point-and-click.
So let me fix yours…
with git(4)
download git
install git
magic git command cut and pasted from somewhere with something I have to edit
cd myproject
rm -Rf .git
./gradlew run
With download
magic curl command (or use the GUI)
unzip -e basics_3.1.zip -d myproject (or use the GUI)
cd myproject
Screw it… anyway… you are changing while I’m typing. There is a fundamental disconnect with this conversation so I’m kind of done with this circular arguments that IGNORE THE ENTIRE POINT.
Yes, but the point you completely miss 100000% of the time is that I am talking about users who are afraid of the command line. The users who have git installed already are not afraid of the command line. Any solution we put out is fine.
We’re talking about users who are lost without the SDK. They need “download this” “do this” “import it into your IDE like this.” Three steps max.
A zip file could do that. So arguing that git clone is better than a zip file continues to miss the point.
Yes, it’s fine for some users… then say that. Stop suggesting that it is better than a zip file for users who would rather shoot their own mother then open up cmd.exe. It’s dumb.
Which reminds me of the fact that some’s didn’t have a JRE/JDK installed at all.
However what about something like a few Screenshots on how to simple add jar dependencies to IDE X (and then simply download the jme-core.jar etc)
Last week I managed to create a file named “*”… don’t ask how… it was in my user folder on osx (where I have pretty much everything)
When I tried to delete it I typed “rm *”, and just before hitting enter…it clicked…
The thing is, as I was noticing it, it already had deleted stuff from /bin, so I was missing all bash/busybox stuff leading to an unusuable system
I am curious why that didn’t happen more often to me.
Well I learnt to use TAB for everything
This is effectively how we do it. Although we put the asset folders inside the src/main/resources folder which means that when the build runs it automatically adds them to tower-assets.jar in this case.
We build using Maven though but the principle is the same.
Similar…except I kept the exact same structure as a regular JME build. There are no extra project files. No extra directories… and you still get an assets.jar in the end. (Which you can easily rename in the main build file.)
I don’t think it can be done with maven. It is intentionally not as flexible.
You can just set the src dir in the Maven build file as well as the name of the output file without use of additional plugins. Of course you’d need the pom.xml for that module but oh well.