On our local machines we use a piece of simple SQL to upload the plugin into the database after it's been built.. restarting the application then deploys it.
You can also add plugin folders from the file system in the web/pom.xml file, e.g.
That second method means those plugins will be locked down in the admin console, preventing you from uploading new versions on the fly.. i.e. they always have to come from the file system.
Thanks for Providing the valuable inputs. Can you please clarify the below two queries ?
01. how to identify a plugin already exist, whether i need to handle in the shell script and do a insertion / update accordingly ?!! How i can make this dynamic, based on the code sync, i need to identify the unique plugins and trigger this action right ?!
02. The location of the created custom plugin jar files will get resided ?!! because i m only seeing the .class files in the application/sbs/home folder .