| Vrigo tooling does not copy static resources to 'work' after change [message #1037449] |
Tue, 09 April 2013 15:15  |
 Jay Huang
Messages: 20
Registered: February 2012 |
Junior Member |
|
|
Hi, I've been having a strange problem with the virgo tooling . Whenever I update static resources( javascript and css), the tooling says something like "Publishing to virgo server...." in the eclipse progress bar, and the "servers" view shows the bundle is refreshing. However,after all, the updated file is not copied to the "work" directory of virgo. I used to solve this by using a script to copy the resource folder to the 'work' dir when the deploy path was fixed for every bundle. But now, the paths are dynamic, I have to redeply the whole bundle every time i make a change.
I am using VTS 3.6.0.M2, Tooling :
Eclipse Virgo Tools 1.0.1.201302270038-RELEASE org.eclipse.virgo.ide.feature.feature.group Eclipse Virgo
Thanks.
[Updated on: Fri, 19 April 2013 02:09] Report message to a moderator |
|
|
|
|
|
| Re: Vrigo tooling does not copy static resources to 'work' after change [message #1220704 is a reply to message #1037449] |
Fri, 13 December 2013 08:25  |
GianMaria Romanato
Messages: 72
Registered: July 2009 |
Member |
|
|
Hi,
I had similar issues with non non class-file resources.
In my experience, the best approach consists in disabling auto-publish completely.
In this way, Virgo Tools will perform auto-publish when you start the server, but any subsequent change executed during development will not be published automatically.
For Java sources, the JVM will help you here: in debug mode the JVM will replace the class definition when you build, provided that the class "interface" is not changed. If the JVM fails to do the bytecode replacement because you added a method, changed a signature, etc, you can manually perform a publish via CTRL-ALT-P or the context menu. To the contrary if you keep auto-publish enabled and publish on build or on save, you'll have the bundle redeployed any time a trivial class file change is performed, which results in a waste of time.
Also, I am using this approach in combination with a little eclipse plug-in I wrote that allows me to use the Virgo Tools with Eclipse PDE. In this way I use PDE for development, and Virgo Tools just for publishing artefacts and starting the server.
https://github.com/giamma/pde2virgo/
GianMaria.
|
|
|
|
Powered by
FUDForum. Page generated in 0.03196 seconds
] 
Search
Help
Register
Login
Home
