Hi Ramesh,
Please ask the user ML for such questions. See why here
http://ofbiz.apache.org/mailing-lists.html.
You will get a better support. There is a wider audience there.
Thanks
This said, did you follow? (please answer on user ML)
https://cwiki.apache.org/confluence/display/OFBIZ/OFBiz+Tutorial+-+A+Beginners+Development+Guide+for+18.12
Jacques
Le 02/01/2023 à 13:15, Ramesh Pillai a écrit :
Hi Jac,
Im new to ofbiz.
I Want to build and customize ofbiz as per my business need.
I had seen a lot of help videos , but I was a little bit confused.
Can you guide me in setup project ,customise , database configure etc
*
*
*Currently*
1. I'm using Windows 11 machine
2. Using intellij
On Mon, 2 Jan 2023 at 17:41, Ernest Hocking <ernest.hock...@computer.org> wrote:
Hi Jacques,
I;m probably too late in the piece to contribute to the decision.
However I'm just starting an implementation project and have spent a
couple of days using v18.12.05. I'd be keen to use v 22 and report and
issues encountered during the implementation/testing as there would be
little rework needed to load data etc into v22 at this stage
thanks and regards
Ernest
On Mon, Jan 2, 2023 at 5:17 PM Jacques Le Roux
<jacques.le.r...@les7arts.com>
wrote:
> Hi Nicolas, All,
>
> Thanks Nicolas for your opinions. I'm surprised that we are only 5 to
> express opinions about this important decision.
>
> Is nobody else interested ?
>
> Thanks
>
> Jacques
>
>
> Le 30/12/2022 à 16:04, Nicolas Malin a écrit :
> > Hello Jacques,
> >
> > I did the migration from my part with your suggest and I confirm that
> ofbiz test passed with success. I also didn't detect any problem on
> standard
> > process for ordering and invoicing during manual simulation.
> >
> > However, I didn't realize any loading test.
> >
> > So no worries from my part to move forward.
> >
> > Thanks for the works !
> >
> > Nicolas
> >
> >
> > On 22/12/2022 19:02, Jacques Le Roux wrote:
> >> Hi Team,
> >>
> >> So far, we have only Michael's, Eugen's and Daniel's opinions about
> releasing the 22.01.01 version under Gradle 7.6 and JDK 17 (OFBIZ-12400).
> >>
> >> To summarize, Michael is against, Eugen and Daniel are for. Daniel
> suggests that we can use workarounds but need to later update OFBiz to
> handle
> >> strong encapsulation.
> >>
> >> Michael, I was surprised by your opinion, because of
> https://markmail.org/message/fq3fpxeg5yfshjwz where you said 1 year ago:
> >>
> >> <<I am also in favor of a 22.01. branch and releasing a first stable
> version during the year 2022.>>
> >>
> >> And that led me to closely verify the situation. Fortunately, after
> OFBIZ-12726 (integration tests), I believe we can trust using Gradle 7.6
> and
> >> JDK 17 by using temporary workarounds.
> >>
> >> So my question is, should we vote for releasing the 22.01.01 version
> under Gradle 7.6 and JDK 17 or should we wait 22.01.02?
> >>
> >> I have decided on my side to update GH, BuildBot and demos to run under
> Gradle 7.6 and JDK 17. If nobody is against of course.
> >> This will take some time, but I don't expect much. For that we need to
> push the workarounds in all supported branches. It's not a big deal:
> >>
> >> - // jdk.serialFilter is to "Prevent possible DOS attack done using
> Java deserialisation" (OFBIZ-12592)
> >> applicationDefaultJvmArgs = project.hasProperty('jvmArgs')
> >> ? jvmArgs.tokenize()
> >> - :
>
['-Xms128M','-Xmx1024M','-Djdk.serialFilter=maxarray=100000;maxdepth=20;maxrefs=1000;maxbytes=500000']
> >> + : ['-Xms128M','-Xmx1024M',
> >> +
>
'-Djdk.serialFilter=maxarray=100000;maxdepth=20;maxrefs=1000;maxbytes=500000',
> // OFBIZ-12592 and OFBIZ-12716
> >> + '--add-exports=java.base/sun.util.calendar=ALL-UNNAMED', //
> OFBIZ-12721
> >> + '--add-opens=java.base/java.util=ALL-UNNAMED' //
> OFBIZ-12726
> >> + ]
> >>
> >> To release w/o the workarounds it is enough to remove the 2
> "ALL-UNNAMED" lines.
> >>
> >> It also would be great to freeze a 23.01 branch and use it as next
> demos while replacing the 18.12 by 22.01 as stable.
> >>
> >> Looking forward for opinions...
> >>
> >> Thanks
> >>
> >> Jacques
> >>
>
--
Regards,
*Ramesh Pillai **■***
*Manager - IT*
*M: +91 8169032006 | Email Id: **ramesh.pil...@blox.xyz*
<mailto:ramesh.pil...@blox.xyz>
05.png
*Website <http://blox.xyz/> | LinkedIn
<https://www.linkedin.com/company/blox-xyz>*
*Head Office: Method & Madness Pvt. Ltd.,****1107, Lodha Supremus, Senapati
Bapat Marg, Lower Parel, Mumbai - 400013**.*
Disclaimer: The information contained in this e-mail message and / or
attachments to it may contain confidential or privileged information of
the Method & Madness Pvt. Ltd and / or its group companies. If you are not
the intended recipient, any dissemination, use, review, distribution,
printing or copying of the information contained in this e-mail message and
/ or attachments to it is strictly prohibited. If you have received
this communication in error, please notify us by reply e-mail or telephone
and immediately delete / destroy the message and / or any attachments
permanently.__Warning-Computer viruses can be transmitted via e-mail. The
recipient should check this e-mail and any attachment for the presence
of viruses. The company has taken every reasonable precaution to minimize
this risk, and is not liable for any damage you may sustain as a
result of any virus in this e-mail. You should carry out your own virus
checks before acting upon the e-mail o
Disclaimer: The information contained in this e-mail message and / or attachments to it may contain confidential or privileged information of the
Method & Madness Technology Pvt. Ltd and / or its group companies. If you are not the intended recipient, any dissemination, use, review,
distribution, printing or copying of the information contained in this e-mail message and / or attachments to it is strictly prohibited. If you have
received this communication in error, please notify us by reply e-mail or telephone and immediately delete / destroy the message and / or any
attachments permanently.__Warning-Computer viruses can be transmitted via e-mail. The recipient should check this e-mail and any attachment for the
presence of viruses. The company has taken every reasonable precaution to minimize this risk, and is not liable for any damage you may sustain as a
result of any virus in this e-mail. You should carry out your own virus checks before acting upon the e-mail or any attachment to it.
