Skip to main content

(Important) Updated core module version numbers to v0.5

1 reply [Last post]
Joined: 2006-01-05

In trunk rev 4330, I updated all of the "core" modules to have a version number (0.5) that matches the WL version number (previously they were versioned either 1.0 or 1.1, which is not what we want).

There's a number of complications that arise from this change, which you should be aware of:

1. You'll probably want to do an "ant clean; ant" just to make sure everything gets built.

2. When you do an "ant run" again, not all of the modules get re-installed. (There's a bug in the module system code that does not properly resolve dependencies). To fix this, make sure you click "Restart All" (under Manage Servers) one extra time. To confirm, make sure there are no Pending modules (under Manage Modules).

3. You probably want to take a snapshot of your world before you do this, since (according to my tests), it'll "cold" start the server and delete any existing state.

4. There are some non-core modules whose dependencies I need to update, in particular security-session-auth/ since it seems a bunch of people are using this. I'll need to upload a new version to the Warehouse, I'll let you know when I do.

Note that most of the modules should have version 0.5 now. Some will not (e.g. whiteboard) which are not considered core. We may re-assign their version numbers at some point in the future.

If all else fails, and you still have modules that are stuck in "Pending", you can remove ~/.wonderland-server/0.5-dev/run/content/modules/. However, note that this removes any manually installed modules and any 3D models you have imported via Insert -> Model.

Sorry for this minor earthquake in the trunk -- we need to make sure all of the version numbers for the modules are correct, otherwise, it'll cause far greater headaches down the road.

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
Joined: 2006-01-05

The security-session-auth/ module depended upon old core module versions. I updated the security-session-auth/ module to depend upon the v0.5 versioned modules. I updated the source code and the Module Warehouse.

Just as a note: none of the code has changed. The only thing changing here is the version of the core modules upon which security-session-auth/ depends. If you already have security-session-auth/ installed, it will remain installed even if you update to the latest trunk.