bw6-plugin-maven icon indicating copy to clipboard operation
bw6-plugin-maven copied to clipboard

Exposing RemoteDeployer's deployApplication(..startOnDeploy...) as plugin parameter

Open benynagy opened this issue 6 years ago • 5 comments

Maven Plugin version: 2.1.0+

Maven version: 3.6.0+

Product : Either of TIBCO ActiveMatrix Businessworks 6 OR TIBCO Businessworks Container edition

Product version:

Component: Either of Maven Eclipse Plugin or Maven build plugin

Steps to reproduce the issue: 1. 2. 3.

Additional environment details if any:

Describe the results you received:

RemoteDeployer -> deployApplication -> param: final boolean startOnDeploy

  • this parameter is hardcoded to "true"

Describe the results you expected:

Hello, Would you please consider exposing the startOnDeploy parameter of RemoteDeployer -> deployApplication method as parameter of Mojos (BWDeploy, BWEARInstaller), similar to the other params... (also a default=true if null) would be great.

I am deploying the applications w/ Jenkins, but there are cases in the early stages, e.g. various Mock Apps, which could benefit from the flexibility of not starting the App immediately.

Thanks

Additional information you deem important (e.g. issue happens only occasionally):

benynagy avatar Jul 26 '19 13:07 benynagy

Hi,

I would also like this evolution. Do you know if you can put this evolution on the next realease?

Thanks

damienRiv avatar Nov 19 '19 08:11 damienRiv

Hello,

I would like to deploy my application without starting it, can you fix this issue please ?

Thanks, Simo

medsiim avatar Nov 19 '19 09:11 medsiim

@medsiim @damienRiv We would plan this issue for next maven release

SujataDarekar avatar Nov 19 '19 10:11 SujataDarekar

Hello Guys, Gr8 work for the plugin :)

I would love this feature too : could you pass the autostart parameter as a property ?

Cause in our env, when it is autostarting, it is crashing the OSGI context of the appNode and nothing is exploitable after... it seems that a temporization should be needed... because we have forked plugin source and passed the autostart parameter to false and it is working. We will test in the meantime the adding of a tempo when autostrating to see if it resolve our issue and propose a new enhacement for the plugin...

In advance thank you,

/Dav

chtidav avatar Nov 19 '19 10:11 chtidav

@medsiim @damienRiv We would plan this issue for next maven release

Thank you @SujataDarekar. i appreciate your contributions :) (y)

medsiim avatar Nov 19 '19 10:11 medsiim