Re: [equinox-dev] equinox console optionality of available commands

[Thomas Watson <tjwatson@xxxxxxxxxx>]

For shutdown and close I am for removing
them.  They are redundant.  The exit command is not redundant
and I have had use for it on occasion.  Would not be opposed to adding
an option to disable exit.

Tom





From:      
 Raymond Auge <raymond.auge@xxxxxxxxxxx>
To:      
 Equinox development
mailing list <equinox-dev@xxxxxxxxxxx>
Date:      
 03/26/2015 02:14 PM
Subject:    
   Re: [equinox-dev]
equinox console optionality of available commands
Sent by:    
   equinox-dev-bounces@xxxxxxxxxxx

---

On Thu, Mar 26, 2015 at 3:01 PM, Thomas Watson <tjwatson@xxxxxxxxxx>
wrote:
I understand the desire to remove exit
since that does a System.exit.  But shutdown and close just do a system
bundle stop.  You  likely don't want to disable the stop command
altogether, but if you don't the user can still easily run 'stop 0' to
get the same thing as shutdown and close.  BTW, I am fine with removing
shutdown and close altogether since they are the same as 'stop 0' really.


So, would you prefer complete removal over a property
which disables individual commands (where the default is to leave everything
published like now)?

- Ray
 

Tom





From:        Raymond
Auge <raymond.auge@xxxxxxxxxxx>
To:        Equinox
development mailing list <equinox-dev@xxxxxxxxxxx>
Date:        03/26/2015
01:35 PM 
Subject:        [equinox-dev]
equinox console optionality of available commands 
Sent by:        equinox-dev-bounces@xxxxxxxxxxx

---

Would people object to a change in equinox.console which would optionally
allow for specific commands not to be published? 

For instance, when running equinox embedded we're controlling the lifecycle
of the framework along with the lifecycle of the embedding application.

I would like to not expose the shutdown related commands which are there.


exit, close, shutdown are commands I'd like to be able to not provide.

-- 
Raymond
Augé (@rotty3000) 
Senior Software Architect Liferay,
Inc. (@Liferay) 
Board Member & EEG Co-Chair, OSGi
Alliance (@OSGiAlliance)_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/equinox-dev

_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/equinox-dev



-- 
Raymond
Augé (@rotty3000)
Senior Software Architect Liferay,
Inc. (@Liferay)
Board Member & EEG Co-Chair, OSGi
Alliance (@OSGiAlliance)_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/equinox-dev