Bug 801415

Could we keep it and document its experimental/not-supported feature? There are plenty of other tools such as jbpm plugin in JBDS were we document what nodes for example in the stencil set are considered supported and which are not. Why have to remove it completely?

(In reply to comment #1)
> Could we keep it and document its experimental/not-supported feature? There are
> plenty of other tools such as jbpm plugin in JBDS were we document what nodes
> for example in the stencil set are considered supported and which are not. Why
> have to remove it completely?

I think that's up to Prakash to decide.

Ok, how do we ask him to decide sooner than later, because this would require  some work to make it enabled in community and not for product.

Tiho, I see your point.  This migration support is a hot topic.  It is a tough call we need to make to avoid too much burden on GSS.  We rather encourage people to opt-in by including documentation on how to enable that plugin.
By default enabling it opens up lot of questions.

So, lets disable it by default.  In the docs we can show steps on how to enable to and clearly state that it is a preview in this release and not fully supported.

Ok, I'll work on this next week and externalize it into its own plugin and allow user-configuration to add it. In community this will be "on" by default so product build will have to disable a line of xml in jbpm.xml (which they already later for the differences in URLs between drools-guvnor and jboss-brms). Hope this is OK solution for everyone.

(In reply to comment #5)
> Ok, I'll work on this next week and externalize it into its own plugin and
> allow user-configuration to add it. In community this will be "on" by default
> so product build will have to disable a line of xml in jbpm.xml (which they
> already later for the differences in URLs between drools-guvnor and
> jboss-brms). Hope this is OK solution for everyone.

Sounds good.

Ok.. lets make sure Ryan (productization) team picks it up well in advance, so that it starts appearing in the early builds.
Please ping Ryan when you have it done.

jpdl migration feature has been externalized to its own plugin. for the product to remove it please make sure that the:

<plugin name="ORYX.Plugins.JPDLMigration"/>

definition in $designer_war/profiles/jbpm.xml is commented. i have left it uncommented for the community

this fix is checked into designer master and 2.1.x branch.

Update status to ON_QA. Please verify them against ER6.

jPDL migration plugin can be disabled in ER6 but designer comes with this plugin enabled. The plugin element

> <plugin name="ORYX.Plugins.JPDLMigration"/>

must be commented out, which needs to be covered in the build process. Assigning to Ryan.

This is done for next release.
svn ci -m "BZ 801415 disable jPDL migration tool"
Sending        src/main/patches/processdesigner/patch_designer_conf.xml
Transmitting file data .
Committed revision 11008.

Re-assign to Lee for documentation updates.
Lee, this might need to add some guide in documentations for how to enable function "Migrate jPDL 3.2 to BPMN2" as Prakash mentioned in comments 4.

The steps to enable it is change the line in brms-standalone-5.3.0/jboss-as/server/${conf}/deploy/designer.war/profiles/jbpm.xml
from
<!--plugin name="ORYX.Plugins.JPDLMigration"/-->
to 
<plugin name="ORYX.Plugins.JPDLMigration"/>

And restart the server, the function/button should be able to appear in the toolbar and be enabled used.

I attached a screen shot for your reference.
By default, the button is not present.

Created attachment 583202 [details]
jPDL_migration_button

The fixed for this issue should be included in ER7. Please do verification on it.

Verified fixed in 5.3.0 ER7. JPDL migration is disabled by default. Doc-stage is down right now, so I will verify the documentation when its up and then set the status to verified.

Closing as status already set to verified.