status, maven & plugin lifecycle management

[Kenneth L]

1) I notice that there is very little activity on this project. Is it dead? Or can we exect any maintenance releases. Will contributions be accepted?

2) Are there any maven repos that I can point to for downloading JSPF or is the only alternative to install it in my own repo manually?

3) The simplicity and cut-the-crap mentality of JSPF is really appealing. However, at least in my case, a basic requirement is that my plugin architecture needs to be able to deregister any plugins that are already loaded (uninstall) and it should also be possible to update to newer versions of a plugin. If one prevents dependencies between plugins and also makes sure the plugins are stateless, my intuition is that this should not be impossible to achieve. Can you think of any showstoppers to this?

/Kenneth

[Ralf Biedert]

cut-the-crap mentality

I like that one … :)

Regarding your other questions:

Am 06.09.2013 um 09:47 schrieb Kenneth L <ken...@leine.cc>:

1) I notice that there is very little activity on this project. Is it dead? Or can we exect any maintenance releases. Will contributions be accepted?

Tough one. I am working on completely different tasks at the moment and I barely come to program. While JSPF is not dead to me in general, I probably won't contribute to it, at least this year.

Generally, version 1.x will only be maintained for really critical bugs: It still does its job really nicely, but it does not support or allow for some often-requested features such as unloading plugins.

Some time ago I started working on version 2.0, called "JSPF Nexus". The code can be found here:

https://github.com/ralfbiedert/jspf

2) Are there any maven repos that I can point to for downloading JSPF or is the only alternative to install it in my own repo manually?

I don't know. I have no "business" with Maven. Some people wanted to look into it, but I never heard anything about it again. I leave the Maven part to the community. Feel free to add Maven support. As long as it leaves the ant build untouched, does not look ugly and the rest of the users endorse it, it will be accepted.

3) The simplicity and cut-the-crap mentality of JSPF is really appealing. However, at least in my case, a basic requirement is that my plugin architecture needs to be able to deregister any plugins that are already loaded (uninstall) and it should also be possible to update to newer versions of a plugin. If one prevents dependencies between plugins and also makes sure the plugins are stateless, my intuition is that this should not be impossible to achieve. Can you think of any showstoppers to this?

Not for version 1.x, the architecture is not flexible enough to add it without breaking / messing up too many things. Version 2.x is intended to have support for it right from the start; but don't wait for it at the moment.

Quality contributions to 2.x, however, will be very much appreciated. 

Best,

Ralf

[Kenneth L]

Thanks for the answer. I will take a look at your github project then...