configuration for new plugin

View: New views
6 Messages — Rating Filter:   Alert me  

configuration for new plugin

by Max Spring :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

I'm writing my own Nexus plugin and I have a need for a configuration
functionality, i.e. for persisting certain configuration values.
I don't care about a UI.  I'm fine with editing the configuration file
manually.
I'd like the plugin to be able to pick up a configuration change without
having to restart the server.
Is there a good example I can follow?
Thanks!
-Max


---------------------------------------------------------------------
To unsubscribe, e-mail: nexus-dev-unsubscribe@...
For additional commands, e-mail: nexus-dev-help@...


Re: configuration for new plugin

by Brian Fox :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Nothing comes to mind, all the plugins we write are reconfigured with
REST calls and the config file is only used for persistence between
restarts.

On Sun, Nov 8, 2009 at 10:43 PM, Max Spring <m2spring@...> wrote:

> I'm writing my own Nexus plugin and I have a need for a configuration
> functionality, i.e. for persisting certain configuration values.
> I don't care about a UI.  I'm fine with editing the configuration file
> manually.
> I'd like the plugin to be able to pick up a configuration change without
> having to restart the server.
> Is there a good example I can follow?
> Thanks!
> -Max
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: nexus-dev-unsubscribe@...
> For additional commands, e-mail: nexus-dev-help@...
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: nexus-dev-unsubscribe@...
For additional commands, e-mail: nexus-dev-help@...


Re: configuration for new plugin

by Anders Hammar :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

I would check out how this is done in log4j. Log4j has some feature that scans if the config file has been updated.

/Anders

On Mon, Nov 9, 2009 at 15:12, Brian Fox <brianf@...> wrote:
Nothing comes to mind, all the plugins we write are reconfigured with
REST calls and the config file is only used for persistence between
restarts.

On Sun, Nov 8, 2009 at 10:43 PM, Max Spring <m2spring@...> wrote:
> I'm writing my own Nexus plugin and I have a need for a configuration
> functionality, i.e. for persisting certain configuration values.
> I don't care about a UI.  I'm fine with editing the configuration file
> manually.
> I'd like the plugin to be able to pick up a configuration change without
> having to restart the server.
> Is there a good example I can follow?
> Thanks!
> -Max
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: nexus-dev-unsubscribe@...
> For additional commands, e-mail: nexus-dev-help@...
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: nexus-dev-unsubscribe@...
For additional commands, e-mail: nexus-dev-help@...



Re: configuration for new plugin

by Max Spring :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Related question: Is there a way to pass a Java property to Nexus (at Nexus startup CLI)?
Thanks!
-Max


On 11/9/2009 6:12 AM, Brian Fox wrote:
Nothing comes to mind, all the plugins we write are reconfigured with
REST calls and the config file is only used for persistence between
restarts.

On Sun, Nov 8, 2009 at 10:43 PM, Max Spring m2spring@... wrote:
  
I'm writing my own Nexus plugin and I have a need for a configuration
functionality, i.e. for persisting certain configuration values.
I don't care about a UI.  I'm fine with editing the configuration file
manually.
I'd like the plugin to be able to pick up a configuration change without
having to restart the server.
Is there a good example I can follow?
Thanks!
-Max


---------------------------------------------------------------------
To unsubscribe, e-mail: nexus-dev-unsubscribe@...
For additional commands, e-mail: nexus-dev-help@...


    

---------------------------------------------------------------------
To unsubscribe, e-mail: nexus-dev-unsubscribe@...
For additional commands, e-mail: nexus-dev-help@...


  

--------------------------------------------------------------------- To unsubscribe, e-mail: nexus-dev-unsubscribe@... For additional commands, e-mail: nexus-dev-help@...

Re: configuration for new plugin

by Max Spring :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Just discovered the wrapper additional parameters in wrapper.conf.
This should be as good as on the CLI.
-Max

On 11/9/2009 3:42 PM, Max Spring wrote:
Related question: Is there a way to pass a Java property to Nexus (at Nexus startup CLI)?
Thanks!
-Max


On 11/9/2009 6:12 AM, Brian Fox wrote:
Nothing comes to mind, all the plugins we write are reconfigured with
REST calls and the config file is only used for persistence between
restarts.

On Sun, Nov 8, 2009 at 10:43 PM, Max Spring m2spring@... wrote:
  
I'm writing my own Nexus plugin and I have a need for a configuration
functionality, i.e. for persisting certain configuration values.
I don't care about a UI.  I'm fine with editing the configuration file
manually.
I'd like the plugin to be able to pick up a configuration change without
having to restart the server.
Is there a good example I can follow?
Thanks!
-Max


---------------------------------------------------------------------
To unsubscribe, e-mail: nexus-dev-unsubscribe@...
For additional commands, e-mail: nexus-dev-help@...


    

---------------------------------------------------------------------
To unsubscribe, e-mail: nexus-dev-unsubscribe@...
For additional commands, e-mail: nexus-dev-help@...


  

--------------------------------------------------------------------- To unsubscribe, e-mail: nexus-dev-unsubscribe@... For additional commands, e-mail: nexus-dev-help@...

--------------------------------------------------------------------- To unsubscribe, e-mail: nexus-dev-unsubscribe@... For additional commands, e-mail: nexus-dev-help@...

Re: configuration for new plugin

by Brian Fox :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Yes, that's the only way I know of if you're using the wrapper.

On Mon, Nov 9, 2009 at 3:47 PM, Max Spring <m2spring@...> wrote:

> Just discovered the wrapper additional parameters in wrapper.conf.
> This should be as good as on the CLI.
> -Max
>
> On 11/9/2009 3:42 PM, Max Spring wrote:
>
> Related question: Is there a way to pass a Java property to Nexus (at Nexus
> startup CLI)?
> Thanks!
> -Max
>
>
> On 11/9/2009 6:12 AM, Brian Fox wrote:
>
> Nothing comes to mind, all the plugins we write are reconfigured with
> REST calls and the config file is only used for persistence between
> restarts.
>
> On Sun, Nov 8, 2009 at 10:43 PM, Max Spring <m2spring@...> wrote:
>
>
> I'm writing my own Nexus plugin and I have a need for a configuration
> functionality, i.e. for persisting certain configuration values.
> I don't care about a UI.  I'm fine with editing the configuration file
> manually.
> I'd like the plugin to be able to pick up a configuration change without
> having to restart the server.
> Is there a good example I can follow?
> Thanks!
> -Max
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: nexus-dev-unsubscribe@...
> For additional commands, e-mail: nexus-dev-help@...
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: nexus-dev-unsubscribe@...
> For additional commands, e-mail: nexus-dev-help@...
>
>
>
>
> --------------------------------------------------------------------- To
> unsubscribe, e-mail: nexus-dev-unsubscribe@... For additional
> commands, e-mail: nexus-dev-help@...
>
> --------------------------------------------------------------------- To
> unsubscribe, e-mail: nexus-dev-unsubscribe@... For additional
> commands, e-mail: nexus-dev-help@...

---------------------------------------------------------------------
To unsubscribe, e-mail: nexus-dev-unsubscribe@...
For additional commands, e-mail: nexus-dev-help@...