What is the status of Contributions libraries update center for 3.1

User Code & Projects
1

Hi core team,

I’m just updated my codebase to 3.1 and find no update for all of them. The google code are closing in a few months and the old 3.0 update center will not work because some changes has been made for core classes. Vector3f for example.

What is the status of Contributions libraries update center for 3.1 now? If there are changes in core libraries that make them not work anymore, should there be a github repo or something to refactor them? Can we folk one by one acording to license of each lib (a lot of type of licenses available).

I will help to refactor some libraries i’m using and if I have them online should that will be great:

Painter:
com.zero_separation.plugins.imagepainter
Folk: https://github.com/atomixnmc/jME3-ImagePainter

Forester:
se.fojop.theforester
Folk: https://github.com/atomixnmc/Forester

Shaderblow

2

All of the google code projects that were in jme-contrib were already moved. You may have missed the post a month or two ago.

I don’t know the status of the plugins build… @jayfella was working on a cool system where we can easily add stuff from github repos but I don’t know where that left off and he’s been mostly absent lately.

3

Thanks for fast reply, the question is we will continue to host all the libraries together like in the old SVN repo?

Should we separate them into many repositories and have only one repo for the xml of the update center.

Edit: sorry for being dumb, they are separated already. So where will the update center xml stored at?

4

The old way won’t really work anymore since we’d like to support any github repo.

@jayfella was working on a cool system where we can easily add stuff from github
repos but I don’t know where that left off and he’s been mostly absent lately.

As I recall, it was to the “please try it out” phase but I never tried it myself.

5

The built plugins will be hosted basically the same way as they are now but the repos can be separate gihub repos that are combined in a github repo that links them which is then built by our build server similar to how it is now.

1 Like
6

Some of the libs and examples (MonkeyTrap for ex) currenly not compile-able with 3.1 alpha, i upgraded them a little bit, so I have to fork and make pull requests, who will merge them, the core team or the original contributor? And also the old contributor have to be granted full permission on their project?

7

Well, Monkey Trap is my project so that’s a poor example. :smile:

For the others, we could try to randomly guess github user names until we get them right… or we can wait for the authors to contact us. I think the latter will take less time.