Slick Forums

Wow, thanks. I'll take a look at your changes. And the reason that the default is the outdated Maven 2 was a copy paste error from a really old maven pom I wrote. I was being lazy, oops.

Second, the change to Maven 3 may break some of the plugins. I'll look into that, if you haven't already.

The Maven reporting plugin is useful of course, but I was trying to emulate the old build scripts as exactly as possible, and then look at optimizations + additions. Convincing the devs that prefer Ant that Maven is so much better may be difficult, so I wanted the build script behaviors to be as exactly the same as possible.

EDIT: Why do I see binaries in the repo? Please get them out ><. It's so so so anti-Maven to include the dist/libs in the source. It also violates just about every source repo paradigm. I was trying to get Slick away from this.

Regarding the binaries, I know that keeping them in the tree is bad practice. I wanted to keep a record for the moment so I would make sure that I would deal with them, especially the jnlp. Note that they are in your repo as well.

And so they are. Wtf.

DAMN YOU MERCURIAL.

My local repo doesn't have them in the source tree. This is my mercurial n00bness showing, as I have really never used it before Slick. Somehow my local and remote repos are out of sync.

I'll just wait on your fork. It'll make merging easier, since the directory changes make everything complicated.

I pulled the current tip of your branch into my repo.

Cool. Thanks! There is still a lot of work to be done and I plan to work on it this week.

Dave

Hi all,

I have made progress on the Maven build system. I still need to work out the webstart stuff though. One question, since ibxm is the only core dependency that is not in the Maven Central repo can we drop it from Slick? I understand that is only used in the ModSound class which is not used.

Dave

Why don't I take a look at that class and see if we can replace it's functionality with a class based of a different dependency?

Ah, I knew I forgot a bullet point

It would also make versioning better: The current system of having Ant increment the version number is working when you're working alone on the project, but doesn't work anymore as soon as 2 developers are contributing ! It's frustrating not knowing which is the version that is downloadable from the Slick2d website, where to find the corresponding Javadoc and sources in the same version, etc.
Having proper version numbers (1.2.3) with Maven would help, and publish those artifacts using the Maven release system would make it easier for people to know which version they're using. It might also help with bug reports because you can't really know which version the user is running when a bug is reported...

Cheers,

Nico

+1, just only for slick version !

_________________
| Last game

Since there doesn't seem to be much interest in switching to Maven for building Slick (no answer to my previous post or my pull request) I've taken a different approach: Package a Maven distribution separately and keep the sources in sync with the development branch (from BitBucket).

Check it out: https://github.com/nguillaumin/slick2d-maven

I also implemented a Maven archetype to get a basic game skeleton going in two commands. This also deals with properly packaging the game with all the dependencies. Eclipse integration is made really easy (zero config) with the Maven Native plugin. The URL above has all the details.

Comment and feedback welcome !

I just open an issue, hope helps!

_________________
| Last game