[TIMOB-17689] CLI: Hook system shows warning 'bad plugin hook that failed to load' at build time
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | Low |
| Status | Closed |
| Resolution | Cannot Reproduce |
| Resolution Date | 2020-01-30T09:04:04.000+0000 |
| Affected Version/s | Release 3.4.0 |
| Fix Version/s | n/a |
| Components | CLI |
| Labels | qe-3.4.0 |
| Reporter | Khushbu Agrawal |
| Assignee | Chris Barber |
| Created | 2014-09-14T14:24:51.000+0000 |
| Updated | 2020-02-04T11:04:49.000+0000 |
Description
Attachments
| File | Date | Size |
|---|---|---|
| batman.zip | 2014-09-14T14:24:51.000+0000 | 2731 |
Is this not supposed to fail? I believe this example is from TIMOB-16153, which specifically has a bad hook.
[~ingo] The issue is linked with the Jira ticket TIMOB-15735 in which a new cli:go hook was implemented for supporting incoming arguments. The project build successfully with this hook but it shows a mentioned warning on the console.
I'm confused. If the ticket was related to TIMOB-15735, we should have related it directly. Regardless, the example here comes directly from TIMOB-16153, and does not reference cli:go. I don't see how the two are related.
Actually the test case for testing the new cli:go hook uses the example from Jira ticket TIMOB-16153.
Unable to reproduce with Appc CLI 7.1.2 and Titanium CLI 5.2.2. Plugin looks fine and loads fine.
Closing ticket as unable to reproduce. Using latest APPC CLI.