Deploying GlobalSight when developing | Developer's Forum | Forums

Welcome to the GlobalSight forums. Raise topics for discussion or follow ongoing discussions to keep track of what’s going on.

Select the forum that you are most interested in and join the discussion. All forums are moderated and comments are reviewed before publishing.

Please consider registering

Log In Register

Register | Lost password?
Advanced Search

— Forum Scope —


— Match —


— Forum Options —


Minimum search word length is 4 characters - maximum search word length is 84 characters

Topic RSS
Deploying GlobalSight when developing
October 12, 2016
1:53 pm
Forum Posts: 7
Member Since:
September 20, 2016


What is the recommended way of deploying GlobalSight while developing?

My current setup is:

  • A Windows machine for editing and building the sources.
  • An Ubuntu 14.04 virtual machine with a running install of GS 8.6.7 which is set up according to the instructions in the wiki. The host GS source folder is mounted in the Ubuntu file system.

What I want is a way to update the GS instance on the Ubuntu virtual machine with the changes I have developed.

What I have tried is:

  1. Edit source.
  2. Build the default ant targets.
  3. Copy the stuff from the capclasses folder in the build directory to the deployments folder on the Ubuntu machine with

    sudo rsync -uav /vagrant/globalsight/main6/tools/build/capclasses/globalsight.ear /home/jboss/GlobalSight/jboss/server/standalone/deployments/
  4. Optionally trigger a deploy by placing a globalsight.ear.dodeploy file in the JBoss deployments directory.

This works only somewhat. I do see the changes I have made to the UI (when modifying .jsp files) but it seems that the changes I have made in the back-end are not deployed. When I attach a debugger (I'm debugging from the Windows host machine using Eclipse) to a running GS instance and step through the code line by line, the currently marked line in the debugger source view does not match what is being executed on the server.

I have not tried the workflow that is suggested in the documentation - extracting the modified classes from the globalsight.jar file and placing them in the directory tree of the server - as this seems excessively complicated and not suitable for a development scenario.

November 14, 2016
4:59 pm
Karol Moran
Forum Posts: 47
Member Since:
October 28, 2014

Can you verify that you are following instructions found in source repo:

globalsightsource\main6\docs\OpenSource_GlobalSight\GlobalSight Source Code Guide
eference\tutorial\GlobalSight Deploy Guide.doc

November 30, 2016
8:41 am
Forum Posts: 7
Member Since:
September 20, 2016

No, i was not following the GlobalSight Deploy Guide document. As i said, it is really cumbersome to automatically "find out all the modified classes or resources, and then put all the new classes or resources to the corresponding directory" as said in the section "2. Patch" in the document.

Since the original post i have now also tried to follow the Deploy Guide exactly. I manually tracked down all of the modified files and copied them to the corresponding directories. This seemed to work (at least somewhat) as i managed to break some functionality related to what i was developing suggesting that there might have been some bugs in my code or that i misplaced something while copying.

Is there a way to deploy GlobalSight as a whole while developing so that i don't have to manually track down the modified files? Copying all of the compiled classes from the capclasses folder as described in the original post didn't seem to work.

December 1, 2016
6:25 am
Forum Posts: 13
Member Since:
November 5, 2014

Please replace globalsight.jar on your ubuntu vm after compiling. The individual compiled classes cannot run with JBoss.

You can find the ant buildfile build.xml at globalsightsource/main6/tools/build folder, and run 'ant globalsight.jar' in Eclipse or in command line to create it.

December 9, 2016
3:57 pm
Forum Posts: 7
Member Since:
September 20, 2016

The problem was that I was trying to deploy some intermediate source version on the master branch that seems to have been broken. Switching to branch `release/GS_8_7_2_Branch` and then building and deploying the project worked fine.

For anyone interested in the details - after switching to the correct branch and building with `ant dist` i installed the ./dist/ by repeating the installation steps described in the GlobalSight wiki. After that i was able to deploy any further changes (that don't involve changes to any resource files) by just replacing the globalsight.jar file as suggested.


Forum Timezone: UTC 0

Most Users Ever Online: 69

Currently Online:
6 Guest(s)

Currently Browsing this Page:
1 Guest(s)

Top Posters:

swami ji: 22

Alexandre De Sena Viegas: 19

varun789 kumar: 18

Amit Dave: 14

Ivy: 13

miya jabar: 13

Yves Savourel: 13

Emre Akkas: 12

Ayman Kh: 11

aman sharma: 11

Member Stats:

Guest Posters: 0

Members: 455

Moderators: 1

Admins: 3

Forum Stats:

Groups: 1

Forums: 4

Topics: 148

Posts: 299

Newest Members: Yurii Zablotskyi, aghori babaji, sourav verma, free astrology, Miente Dijkstra, aryan sharma, visu u, Andrei Karas, sneha Kaur, mehak mehra

Moderators: Karol Moran_1: 0

Administrators: waxingmedia: 3, Karol Moran: 47, gsteam: 0