Every night at 0h New York time.
@normen said:
Every night at 0h New York time.
Build for revision 548-550 was successfully (no errors) but I don't see shaderblow lib on available plugin list though. I don't know why it is not working. I will try to check tomorrow.
Like I said, check the console output. The build doesn’t fail when your plugin fails, its just removed from the repo.
@normen said:
Like I said, check the console output. The build doesn't fail when your plugin fails, its just removed from the repo.
Sorry to bother you again normen but I didn't find errors related with shaderblow plugin on console output for #995 (25-oct-2012 0:20:45) revision: 550
I will try to start from scratch again this afternoon and see what happen.
Hi @normen,
I was no able to make the shaderblow lib listed on update plugin list yet. I tryed different thing. Searching for how to build a library plugin on the forum I found this comment from youhttp://hub.jmonkeyengine.org/groups/community-plugins/forum/topic/simplebloxelworld/?topic_page=1&num=15#post-192394:
“When you have added the module folder please tell me so I can add it to the suite build script.”
Did you have to add the module to a build script? Have you added the shaderblow module to that script?
Thanks,
H
By the way, the module is http://code.google.com/p/jmonkeyplatform-contributions/source/browse/#svn%2Ftrunk%2Fshaderblowlib
@H said:
By the way, the module is http://code.google.com/p/jmonkeyplatform-contributions/source/browse/#svn%2Ftrunk%2Fshaderblowlib
That is not a module plugin, it cannot be added, check this thread on how to build "normal" jme projects.
http://hub.jmonkeyengine.org/groups/community-plugins/forum/topic/contribution-repository-and-building-a-suite/
Here, I made it a bit easier to build the jar projects and made some documentation about it:
https://wiki.jmonkeyengine.org/legacy/doku.php/sdk:development:setup#building_library_jar_files_on_the_server
Edit: Oh and I saw there are plugins, one at shaderlib and one at at shaderlib22, I now included the shaderlib22 in the suite build.
I now saw it was a local leftover, I added the “shaderblowlib” project now.
1 Like
@normen said:
Here, I made it a bit easier to build the jar projects and made some documentation about it:
https://wiki.jmonkeyengine.org/legacy/doku.php/sdk:development:setup#building_library_jar_files_on_the_server
Edit:Oh and I saw there are plugins, one at shaderlib and one at at shaderlib22, I now included the shaderlib22 in the suite build.
I now saw it was a local leftover, I added the "shaderblowlib" project now.
Thanks very much normen. I've added the two ant targets to the module build file. Also, I've added the following to the shaderblow project build file:
[xml]
<!-- Copy asset folder content to build folder in order to package assets on library jar file -->
<target name="-pre-jar">
<copydir dest="${build.classes.dir}" src="${assets.folder.name}"></copydir>
</target>
[/xml]
As the comment says, this ant target copies the content of the assets' folder to the build folder so the assets' folder content is packaged into the jar file when the jar file is built. I will check tomorrow if all these changes work fine.
1 Like
Thing is your shaderblow project is not a subfolder of the main module project so commits to the base library won’t up the version of the plugin…
@normen said:
Thing is your shaderblow project is not a subfolder of the main module project so commits to the base library won't up the version of the plugin..
Ok, I see.
Thats is the reason begind "./" was used on the ant target instead of "../".
I will move the Main shaderblow project into shaderblowlib module.
Thanks again normen.
1 Like
Main ShaderBlow project moved into ShaderBlowLib module project. Waiting for night build process to check if all work fine.