The default implementation of these hook scripts are empty but they are there for you to carry out any extra tasks that you might want to complete as part of the standard build or build-serve processes. For example you might want to automatically package your /web output directory into a WAR file every time that you do a release build so that you can then deploy that artefact to an application server.
Now, as with any programming, it’s just possible that you might make a mistake and need to be able to debug these hooks scripts. There is only so much that you can do with console.log() after all!
I use these ojet hook scripts a lot (and occasionally make mistakes), so I though that I’d share my setup for effectively debugging them. I’m going to explain how to do it, based on my O/S and preferred editing environment for write node code. I’m not telling you that this is the "correct" way to do it, other IDEs and editors are available and of course details will differ from O/S to O/S. However, you should be able to apply the same principle to your chosen combination of O/S and editing environment.
Debugging in My Setup
For regular information become a member in the WebLogic Partner Community please visit: http://www.oracle.com/partners/goto/wls-emea ( OPN account required). If you need support with your account please contact the Oracle Partner Business Center.