JBossDeveloper

@cammunda I hadn't heard of the ChangeProcessInstanceVersionCommand. It wasn't mentioned in the User Guide so we never noticed it (this is a pity).

Based on what I have read though, our library is more powerful than this command (although to be fair, I have only take a quick look). The jbpm-migrator uses mappings provided by the developer to handle situations where a node has been removed. It will migrate all sub-processes, and it will also migrate the TaskContextInstance. It has the potential for much more, but we limited it's functionality to the essentials.

As for the version issue, I haven't had a chance to look at JBPM 4 at all, but I'm assuming it can be adapted for it. In any case, it's exists in our code base as a standalone component, so it could always be release as a separate download for those using version 3.

@tom.baeyens sounds great Tom. I will post a reply as soon as I can.

Regards,

Caleb

As for the version issue, I haven't had a chance to look at JBPM 4 at all, but I'm assuming it can be adapted for it. In any case, it's exists in our code base as a standalone component, so it could always be release as a separate download for those using version 3.

Hi,

I just wanted to let you know that I have made a request to open source the jbpm-migrator project. It may take a little while to get an answer, as we are currently in the middle of kicking of some new development work. I will let you know as soon as I have some news.

Regards,

Caleb

Hi,

I've been given permission by my employer to open source the jbpm-migrator project! Please let me know what the next steps are.

Cheers!

Caleb

Hey, that's really great news.

And please have a look in the ChangeProcessInstanceVersionCommand. maybe you can leverage that? Or at least merge the stuff that would be duplicated?

There should be tests for it as well if I remember it right (otherwise ping me, than the tests are here in the customers code).

Okay. But i expect it to be very different in 4 ;-) At least much easier...

Hi Tom,

the CEO of my company has asked me for a brief explanation of what it means to contribute this code - from a legal point of view - to JBPM.

I know that we will be releasing the code under the terms of the LGPL. Are there any other considerations I should be aware of? I looked on the JBoss site but I couldn't find any FAQ or other document that explained this. Is it possible for me to provide him with a copy of the Contributor agreement (I will be using the Corporate agreement type)?

Caleb,

Let me explain you my limited knowledge of this agreement.

It means that there is a shared copyright for the contributed code. Red Hat wants to have the ability to do stuff with the contributed code (such as for instance change the license to GPL or APL) without having to ask the formal agreement from each contributor. If this contributor agreement would not be there and if you (or your company) would not agree to e.g. change the license to APL than this would not be possible with LGPL.
Btw, you yourself still have the right to distribute your contributed code under another (whether commercial or open source) license than LGPL.

I hope this helps (and that it's somewhat correct ;-) )

Cheers,
Koen

This is indeed the most important part of the agreement and correct afair

Thanks for the feedback!