Move to GitHub and Gradle

@danielwegener thanks I’ll give a shot in the gradle build; having the transitive dependency jme3-jogg -> j-ogg would be nice.

@normen: does jme use a patched version? if so, has a patch been sent upstream / where can i find it? the lib distributed in the git repo is unversioned.

@ggraz said: @danielwegener thanks I'll give a shot in the gradle build; having the transitive dependency jme3-jogg -> j-ogg would be nice.

@normen: does jme use a patched version? if so, has a patch been sent upstream / where can i find it? the lib distributed in the git repo is unversioned.

https://code.google.com/p/jbullet-jme/source/browse/#svn%2Fbranches%2Fjbullet

@normen said: https://code.google.com/p/jbullet-jme/source/browse/#svn%2Fbranches%2Fjbullet

Is that a fork you maintain of jbullet, or can it be considered mainstream?
Would make sense to move that as well inside main jme repo?
Thx for having committed the jogg change already.

@ggraz said: Is that a fork you maintain of jbullet, or can it be considered mainstream? Would make sense to move that as well inside main jme repo? Thx for having committed the jogg change already.

Its a fork and its well kept where it is.

@normen said: Its a fork and its well kept where it is.

Fair enough. So it looks like this jbullet fork is a direct dependency for jme3-jbullet; how is the versioning of this dependency managed given the jar is unversioned in the jme tree?

@ggraz said: Fair enough. So it looks like this jbullet fork is a direct dependency for jme3-jbullet; how is the versioning of this dependency managed given the jar is unversioned in the jme tree?

Exactly as you say, its unversioned in the source tree.

Guys i have a question: will contribution repo be moved to github?
I mean this one http://code.google.com/p/jmonkeyplatform-contributions/

From what i get there is a whole new plugin system (if not ready it’s in the pipeline)

Afaik you can upload to any github repository, add a configuration file and submit the repository.

Here are some more details:

https://wiki.jmonkeyengine.org/legacy/doku.php/sdk:plugin-submission

@mifth said: Guys i have a question: will contribution repo be moved to github? I mean this one http://code.google.com/p/jmonkeyplatform-contributions/
@zzuegg said: From what i get there is a whole new plugin system (if not ready it's in the pipeline)

Afaik you can upload to any github repository, add a configuration file and submit the repository.

Here are some more details:

https://wiki.jmonkeyengine.org/legacy/doku.php/sdk:plugin-submission

Afacis this new system isn’t in place yet though, the plugins are still built from the svn repo.

Thanks guys.

@H Could you help me with thhis? As you did our plugin for ShaderBlow. Where we will put the ShaderBlow?

@mifth said: Thanks guys.

@H Could you help me with thhis? As you did our plugin for ShaderBlow. Where we will put the ShaderBlow?

So far I know, we need to continue using current plugin repository (Google Code Archive - Long-term storage for Google Code Project Hosting.) because the new “plugin contribution system” described here is not ready yet.

In order to move shaderblow to github, we need to copy the content of trunk/shaderblowlib/ShaderBlow folder to a github repository and follow a few steps from https://wiki.jmonkeyengine.org/legacy/doku.php/sdk:plugin-submission. That is all we need to do.

I think we should move out test’s file to a different project. Having shaderblow-plugin project and shaderblow-test project. But it is just an idea.

@H said: So far I know, we need to continue using current plugin repository (https://code.google.com/p/jmonkeyplatform-contributions/) because the new "plugin contribution system" described here is not ready yet.

In order to move shaderblow to github, we need to copy the content of trunk/shaderblowlib/ShaderBlow folder to a github repository and follow a few steps from https://wiki.jmonkeyengine.org/legacy/doku.php/sdk:plugin-submission. That is all we need to do.

I think we should move out test’s file to a different project. Having shaderblow-plugin project and shaderblow-test project. But it is just an idea.

Yeah, good idea to move tests to a different project. I think we will do it.

Ok, i get you! We will be on google repo till the github repo is unfinished. :slight_smile: