We are also running projects based on the 17.12 release branch, both new projects and migrations from 12/13 releases.

I would consider it a relatively safe approach.

Regards,

Michael


Am 12.03.19 um 16:48 schrieb Ingo Wolfmayr:
Hi Pierre,

I have been testing it for the last few months (August 2018) and all issues I 
had so far apply for 16.11 as well.

 From Decembers Newsletter: "Note: The community is also working on the plan to 
release OFBiz 17.12 branch. In past one year, the community had worked on stabilizing the 
17.12 branch."

17.12 has some new features I would not like to miss like the new theming 
aproach, use of plugins a.s.o.

Additionally to that, this problem does not come up on a clean environment.  So 
I guess it may be database related.

Best regards,
Ingo

-----Ursprüngliche Nachricht-----
Von: Pierre Smits <[email protected]>
Gesendet: Dienstag, 12. März 2019 16:16
An: [email protected]
Betreff: Re: Migrate

Hi Ingo,

Are there not some risks involved?
  As far as I can tell nothing has been released yet in that branch. It maybe a 
bug unidentified.

Best regards,

Pierre Smits

*Apache Trafodion <https://trafodion.apache.org>, Vice President* *Apache Directory 
<https://directory.apache.org>, PMC Member* Apache Incubator <https://incubator.apache.org>, 
committer *Apache OFBiz <https://ofbiz.apache.org>, contributor (without privileges) since 2008* Apache 
Steve <https://steve.apache.org>, committer


On Tue, Mar 12, 2019 at 3:57 PM Ingo Wolfmayr <[email protected]>
wrote:

Hi everybody,

I am currenty working on migrating an 13.xx to 17.xx. It seems to work
fine but on some screens i get the following error message:

"java.lang.IllegalArgumentException: Error running script at location
[component://webtools/groovyScripts/service/JobDetails.groovy]:
java.lang.ClassCastException: Incompatible class:
org.apache.ofbiz.widget.renderer.VisualTheme"

For example webtools/control/JobDetails?jobId=xxxxxxx

Does anyone know where that may come from?

Thanks,
Ingo


Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to