Release Notes - Petals ESB CLI - Version 2.1.0 - HTML format

Configure Release Notes

Bug

[PETALSESBCLI-38] - Unable to define a configuration property on command deploy
[PETALSESBCLI-39] - If a component installer is loaded, Petals CLI can't deploy it in a second step
[PETALSESBCLI-40] - The command 'list' does not return components that have only their installer loaded
[PETALSESBCLI-41] - Command arguments are refused on the command line
[PETALSESBCLI-42] - The option '--file' is not recognized
[PETALSESBCLI-45] - No error occurs on command 'deploy' without option
[PETALSESBCLI-49] - If a component is in state 'SHUTDOWN', the command 'undeploy' should succeed
[PETALSESBCLI-51] - If a component is in state 'STOPPED', the command 'stop-artifact' should fail
[PETALSESBCLI-54] - If a service assembly is in state 'SHUTDOWN', the command 'undeploy' should succeed
[PETALSESBCLI-55] - No error occurs starting a component already started
[PETALSESBCLI-56] - No error occurs starting a service assembly already started
[PETALSESBCLI-61] - No confirmation is asked shutdowning a container in command line mode

Improvement Request

[PETALSESBCLI-11] - Unrecognized arguments are used as properties
[PETALSESBCLI-43] - Improve error messages
[PETALSESBCLI-44] - Petals CLI should respect IEEE 1003.1 and POSIX Conventions
[PETALSESBCLI-46] - If a component is in state 'SHUTDOWN', the command deploy should succeed uninstalling the component first
[PETALSESBCLI-47] - Add support of Java Logging
[PETALSESBCLI-48] - If a component is in state 'STARTED' or 'STOPPED', no stack trace should occur on the Petals node side
[PETALSESBCLI-50] - Improve the error message when stopping a component in state 'SHUTDOWN'
[PETALSESBCLI-52] - Improve the error message when stopping a component for which only the component installer is loaded
[PETALSESBCLI-57] - If a service assembly is in state 'STARTED' or 'STOPPED', no stack trace should occur on the Petals node side
[PETALSESBCLI-58] - Add an extension mechanism to add custom command
[PETALSESBCLI-63] - The command 'undeploy' does not permit to undeploy a list of artifact in bulk mode

Task

[PETALSESBCLI-62] - The argument 'container' on command 'stop' is not needed

Edit/Copy Release Notes

The text area below allows the project release notes to be edited and copied to another document.

Release Notes - Petals ESB CLI - Version 2.1.0
    
<h2>        Bug
</h2>
<ul>
<li>[<a href='https://jira.petalslink.com/browse/PETALSESBCLI-38'>PETALSESBCLI-38</a>] -         Unable to define a configuration property on command deploy
</li>
<li>[<a href='https://jira.petalslink.com/browse/PETALSESBCLI-39'>PETALSESBCLI-39</a>] -         If a component installer is loaded, Petals CLI can&#39;t deploy it in a second step
</li>
<li>[<a href='https://jira.petalslink.com/browse/PETALSESBCLI-40'>PETALSESBCLI-40</a>] -         The command &#39;list&#39; does not return components that have only their installer loaded
</li>
<li>[<a href='https://jira.petalslink.com/browse/PETALSESBCLI-41'>PETALSESBCLI-41</a>] -         Command arguments are refused on the command line
</li>
<li>[<a href='https://jira.petalslink.com/browse/PETALSESBCLI-42'>PETALSESBCLI-42</a>] -         The option &#39;--file&#39; is not recognized
</li>
<li>[<a href='https://jira.petalslink.com/browse/PETALSESBCLI-45'>PETALSESBCLI-45</a>] -         No error occurs on command &#39;deploy&#39; without option
</li>
<li>[<a href='https://jira.petalslink.com/browse/PETALSESBCLI-49'>PETALSESBCLI-49</a>] -         If a component is in state &#39;SHUTDOWN&#39;, the command &#39;undeploy&#39; should succeed
</li>
<li>[<a href='https://jira.petalslink.com/browse/PETALSESBCLI-51'>PETALSESBCLI-51</a>] -         If a component is in state &#39;STOPPED&#39;, the command &#39;stop-artifact&#39; should fail
</li>
<li>[<a href='https://jira.petalslink.com/browse/PETALSESBCLI-54'>PETALSESBCLI-54</a>] -         If a service assembly is in state &#39;SHUTDOWN&#39;, the command &#39;undeploy&#39; should succeed
</li>
<li>[<a href='https://jira.petalslink.com/browse/PETALSESBCLI-55'>PETALSESBCLI-55</a>] -         No error occurs starting a component already started
</li>
<li>[<a href='https://jira.petalslink.com/browse/PETALSESBCLI-56'>PETALSESBCLI-56</a>] -         No error occurs starting a service assembly already started
</li>
<li>[<a href='https://jira.petalslink.com/browse/PETALSESBCLI-61'>PETALSESBCLI-61</a>] -         No confirmation is asked shutdowning a container in command line mode
</li>
</ul>
                
<h2>        Improvement Request
</h2>
<ul>
<li>[<a href='https://jira.petalslink.com/browse/PETALSESBCLI-11'>PETALSESBCLI-11</a>] -         Unrecognized arguments are used as properties
</li>
<li>[<a href='https://jira.petalslink.com/browse/PETALSESBCLI-43'>PETALSESBCLI-43</a>] -         Improve error messages
</li>
<li>[<a href='https://jira.petalslink.com/browse/PETALSESBCLI-44'>PETALSESBCLI-44</a>] -         Petals CLI should respect IEEE 1003.1 and POSIX Conventions
</li>
<li>[<a href='https://jira.petalslink.com/browse/PETALSESBCLI-46'>PETALSESBCLI-46</a>] -         If a component is in state &#39;SHUTDOWN&#39;, the command deploy should succeed uninstalling the component first
</li>
<li>[<a href='https://jira.petalslink.com/browse/PETALSESBCLI-47'>PETALSESBCLI-47</a>] -         Add support of Java Logging
</li>
<li>[<a href='https://jira.petalslink.com/browse/PETALSESBCLI-48'>PETALSESBCLI-48</a>] -         If a component is in state &#39;STARTED&#39; or &#39;STOPPED&#39;, no stack trace should occur on the Petals node side
</li>
<li>[<a href='https://jira.petalslink.com/browse/PETALSESBCLI-50'>PETALSESBCLI-50</a>] -         Improve the error message when stopping a component in state &#39;SHUTDOWN&#39;
</li>
<li>[<a href='https://jira.petalslink.com/browse/PETALSESBCLI-52'>PETALSESBCLI-52</a>] -         Improve the error message when stopping a component for which only the component installer is loaded
</li>
<li>[<a href='https://jira.petalslink.com/browse/PETALSESBCLI-57'>PETALSESBCLI-57</a>] -         If a service assembly is in state &#39;STARTED&#39; or &#39;STOPPED&#39;, no stack trace should occur on the Petals node side
</li>
<li>[<a href='https://jira.petalslink.com/browse/PETALSESBCLI-58'>PETALSESBCLI-58</a>] -         Add an extension mechanism to add custom command
</li>
<li>[<a href='https://jira.petalslink.com/browse/PETALSESBCLI-63'>PETALSESBCLI-63</a>] -         The command &#39;undeploy&#39; does not permit to undeploy a list of artifact in bulk mode
</li>
</ul>
                    
<h2>        Task
</h2>
<ul>
<li>[<a href='https://jira.petalslink.com/browse/PETALSESBCLI-62'>PETALSESBCLI-62</a>] -         The argument &#39;container&#39; on command &#39;stop&#39; is not needed
</li>
</ul>