Teamserver failed to pick up new library

I updated a custom java action with the new library. The project worked locally, but updating the team server proved to be problamatic. Allthough the project was committed creating a deployment archive would always result in an error that the library could not be found. I had to use SVN to add the library to the team server. But then the deployement archive could not be made because of this error: The selected revision was created with another Modeler version ((unknown)). Please use that Modeler version to create the deployment archive. So after a bogus update of the teamserver I finally could create a deployment archive. Did I do something wrong in this process? Or is there some other reason why the teamserver did not pick up the change in the userlib?
3 answers

I give a reply to the last comment of Arjan here to give some screenshots.

What I did is this: Downloaded from the team server the application to a new directory. Updated the userlib directory with a new .jar file. In this example with a new jasperreports-4.1.2.jar. Made some changes to the application and did a commit to the team server. As you can see from the picture the .jar file is not synchronised. userlib


Here again an answer because of the limited comment possibilities. You triggered me to look in the history section and this is what I noticed:

The jar file was there already there when I committed revision 39. I know this for sure because of the comment I made to this revision. But the file only started to appear in revision 41.

I have checked the teamserver again by downloading it to a new directory and the file is there. Strange though that the original directory still gives me the above picture that the .jar file is not synchronized. I do not know what is causing the delay.


If you replace a library with a newer version and the commit using the Modeler, the library should appear in the "Changes on disk" tab page of the commit dialog. Does it appear there if you try it again? If it does not, it is a bug but I cannot imagine that there is a bug in that functionality.

If you commit outside the Modeler meta-information is missing and the Modeler cannot determine with which version was used to commit. To get around that you can do a bogus commit (change the canvas width of an arbitrary form) and the next revision will have the correct meta-information again.