If we have 2 or more j-cook generated components, we'll have 2 or more JDOM copies in the same joomla installation.

Why don't add JDOM as library in joomla and use just ONE copy of JDOM for all the j-cook generated components (and not only)?

this will avoid probable conflicts and will allow us to easily use JDOM anywhere in joomla.

This is true.
I am gonna make a plugin soon.

I'm just making it right now, because I need it soon, I can post it here, if you want. it's almost done, I just need to test it.

Great !
I will focus on dates...

here the plugin

it's a first release, done with a bit of hurry, but it works, surely can be written better, maybe moving the postflight body to each single task function, and it also keep track of the jdom version and the WILL of the user.
let me know what you think.

I just saw now, in the JDOM there are few calls to the component is using it (for example the component helper), so it's not fully working as standalone library.

Why don't you put JDOM on github?
it would be easier to get help in the development.

Thank you very much for your talents.

I've putted on gitHub under MIT License.
I am now integrating the plugin in the generated component and handle all the details.


I have loved the way you parameter the upgrade of JDom because the 3 possible cases are very usefull. (Always, Never, If newer)

github.com/Cook-Self-Service/JDom

K+++