search

krinsdeath / CommandSuite

A complete command replacement for the default vanilla minecraft commands
1 stars 0 forks source link

Build instructions needed #7

Open bobpaul opened 13 years ago

bobpaul commented 13 years ago

Could you please post the build instructions? I'd love to help find bugs or even fill in some of the missing commands, but it's been a while since I last used java and I'm not quite sure what to do to build this properly.

krinsdeath commented 13 years ago

Ah, sorry. In order to build this you'll need Maven 3. Just checkout the repo with git clone https://github.com/krinsdeath/CommandSuite.git and run mvn package clean

Or you can just checkout the repo like I said, import the project in NetBeans or Eclipse (or whichever IDE you prefer) as an Existing Maven Project, and it'll set itself up and you can build it normally.

This project is sort of on the backburner, I have been working on my chat suite lately. I'd appreciate any help you can give, or any feature ideas or bugs you find.

Thanks!

bobpaul commented 13 years ago

"[ERROR] The goal you specified requires a project to execute but there is no POM in this directory (/home/bobpaul/CommandSuit). Please verify you invoked Maven from the correct directory."

Sounds like pom.xml is a bit like a Makefile? That should probably be checked into the repo.

krinsdeath commented 13 years ago

Yeah, it's in there now. I didn't even think about this. pom.xml tells Maven how the sources should be compiled and what the artifact the compiler creates should look like. In a sense, a makefile is pretty accurate. Anyway, go ahead and pull the upstream changes and then attempt to recompile, it should work this time.

note: tons of changes to this version, not all of which have been tested

bobpaul commented 13 years ago

Excellent. I still have errors, but they appear to be things I can solve on my own (maven can't find the craftbukkit server to link against... this is my first time building a bukkit plugin). Since I just got back from vacation, I don't really have time to do anything further right now...

Add something to the effect of "Build this project with maven3 using 'mvn package clean' " to the README.md and I'd see no reason not to close this issue.