Split: fbx importer - using gradle

Sorry for offtopic, but how do i open jme sources in eclipse for make changes? is it possible?

you have to clone the repo from github GitHub - jMonkeyEngine/jmonkeyengine: A complete 3D game development suite written purely in Java. (see “the https clone url” on the right)

I’m so waiting for this,
this will allow to use most assets from unity store (have to recheck their license, but if I remember correctly as long as used for games it is fine to use with other engine)

@nehon said: you have to clone the repo from github https://github.com/jMonkeyEngine/jmonkeyengine (see "the https clone url" on the right)
But i have this and i don't know what to do with it. I guess, i need this "graddle" for eclipse. Sorry for newbie questions... Well, i will find out...

I don’t know how to work with this in eclipse, please halp :frowning:

@Eirenliel said: I don't know how to work with this in eclipse, please halp :(
Well I don't know neither because I use the SDK and not eclipse, but I guess that you need a gradle plugin for eclipse, yes. Check this http://marketplace.eclipse.org/content/gradle-integration-eclipse-37-43#.U-599fl_vDE
@nehon said: Well I don't know neither because I use the SDK and not eclipse
It is possible to contribute to jme through SDK? I can't find a way to do it.

@nehon, it will be nice if you explain how u personally work with jme sources, so i could do the same next time. I intend to contribute some more features later (very-very later).

well, nothing fancy, I use SourceTree (atlassian free software) to manage the git repo.
I cloned the repo locally.
My SDk have a gradle plugin so It can open the engine project.
Then I just modify and run the code in the SDK and commit and push with SourceTree.

SourceTree is not mandatory, you can use Netbeans git integration, I use it for several reasons :

  • Netbeans’ git integration is the bare minimum. And kind of tries to make you think git is as easy as SVN…but it’s not and at some point you’re stuck. (like you can’t force a rebase on a pull)
  • You can easily see and manage Pull Requests in SourceTree
  • It works pretty well :stuck_out_tongue:

Well I use eclipse so here is what I do ( all cmd)

install git
install gradle

-> cmd: git clone githubjurl
drink a coffee while it downloads :slight_smile:
-> edit the gradl.properties, and disable native bullet
-> cmd: gradle build

-> If his works so far, you can basically edit the source with whatever and build via gradle,
nowfor the eclipse integration:

-> open the main build.gradle
-> add “apply plugin: ‘eclipse’” iin the subprojects part.

Should look similar to this then

subprojects {
        // Don't add to native builds
        //    if(!project.name.endsWith('native')){
        apply from: rootProject.file('common.gradle')
        //    }
    apply plugin: 'eclipse'
}

Don’t try to think why that line is not in it by default (i would say some in the jme community dislike eclipse a litte to much).

-> cmd: gradle eclipse
gradle will now create the project files download dependencys ect for eclipse,
after this you can import the projects in eclipse.

If you want to use IDEA the workflow is similar, but with the ‘idea’ plugin
for netbeans/jmesdk (not used by me so cannot say it works)
the integration is done from the netbeans side, apparently there is a gralde plugin there

Note many of the above mentioned IDEs might have other ways of grade integration, eg IDEA can load and understand grade build files mostly out of the box. The way I mentioned here is the pure gradle based way, as I had less problems with it.

BTW do not use the eclipse git integration, while it supports mostly all, eclipse thinks in projects and has great problems with the structure of multipart gradle builds. (eg it makes way more work to commit the build file in the main folder wich itself is not eclipse project)

My suggest is to stay plain with git for pulling and for commiting with git gui, as it is everywhere were git is installed available, on all platforms.

I add “apply plugin: ‘eclipse’” in the beginning, but it did not work. Now i see.

Thanks, it works perfectly now, jme community can expect more cool things from us in the future :3

@Empire Phoenix said: Don't try to think why that line is not in it by default (i would say some in the jme community dislike eclipse a litte to much).

Back to the old conspiracy theories eh? The NetBeans gradle plugin applies this by itself, it uses the IDEA plugin, as you say IDEA can also open the project without the explicit import. I don’t know why eclipse cannot apply its own plugin by itself… Really, the only reason why we don’t “support” Eclipse is because it always needs an “Extrawurst” and none of us use it so we cannot check when its finally pleased :wink:

It is not very convenient, as i can see. Strange errors, shitty structure… But i still love eclipse :smiley:

https://dl.dropboxusercontent.com/u/101385537/screens/eclipse_jme_20140816.png

@normen said: Back to the old conspiracy theories eh? The NetBeans gradle plugin applies this by itself, it uses the IDEA plugin, as you say IDEA can also open the project without the explicit import. I don't know why eclipse cannot apply its own plugin by itself.. Really, the only reason why we don't "support" Eclipse is because it always needs an "Extrawurst" and none of us use it so we cannot check when its finally pleased ;)

Well thanks to gradle it works out of the box this time, it is really only that one line missing.
Anyway was not a try to start the discussion again, just a explanation why it is not out of the box