Hi Yashwant,
Sorry I couldn't get back to you earlier.
The issue has been fixed. But, I will need your help to understand the core
reason behind it.
It was fixed when I changed the name of my plugin from pascal case to small
case. I did not understand how it did the trick. Initially, I thought it
was due to the latest trunk pull, but it was the issue of naming
conventions.
What is bugging me is that there were multiple other groovy files, which
were working fine while having the plugin name in the pascal case. I had to
comment on 4 different files for the project to build earlier. I traced the
issue down to two simple lines in one of the file. When these two lines
were commented in this particular file, the build was successfully made,
else it was a failure.
For example, there was an iteration on keyset as given below:
returnableItems.keySet().each { orderItem ->
Under the iteration, there was variable assignment, as given below:
itemCount = orderItem.quantity
itemPrice = orderItem.unitPrice
When I was commenting on these variable assignments, the build was
being successfully built.
Now, all files are uncommented, and the build is successfully built. I
just do not understand the reasoning behind this one.
I tried now to generate the issue by reverting the name back to pascal
case, but the issue does not seem to be coming anymore.
I would like to know what the root cause of this issue was and how
come what I did later on fixed the issue. Any insights would be
helpful.
Thanks. Regards
Anshul Goyal
On Thu, 3 Apr 2025, 16:07 Yashwant Dhakad, <
[email protected]> wrote:
> Hi Anshul,
> The log you provided does not contain enough details to identify the root
> cause of the issue. Could you please run the build in debug mode (--debug
> flag) and share the complete error logs? This will help us analyze the
> exact reason for the failure.
>
> On Wed, Apr 2, 2025 at 7:24 PM Anshul Goyal <[email protected]> wrote:
>
> > Hi Yashwant,
> > Below mentioned are the error log that I was getting.
> >
> > parsing failed
> > > Task :compileGroovy FAILED
> > FAILURE: Build failed with an exception.
> > * What went wrong:
> > Execution failed for task ':compileGroovy'.
> > > Compilation failed; see the compiler error output for details.
> >
> > On Wed, 2 Apr 2025, 19:22 Yashwant Dhakad, <
> > [email protected]> wrote:
> >
> > > Hi Anshul,
> > >
> > > The image did not load in the mailing list. Could you please share the
> > > error logs or create a ticket in Jira?
> > >
> > > On Wed, Apr 2, 2025 at 6:20 PM Anshul Goyal <[email protected]>
> wrote:
> > >
> > > > Hi community,
> > > > I have been using the default version of trunk in one of the projects
> > and
> > > > the build was being successfully created. But in the recent weeks, I
> > > > updated ofbiz-framework and plugins to the latest version of trunk,
> and
> > > > since then I have been facing issues while building the project.
> > > >
> > > > This is certainly an interesting issue, as while commenting on
> > particular
> > > > groovy files which I customely made, the build of the project is
> being
> > > > successful , while the uncommented file is building the project well
> in
> > > the
> > > > previous versions of trunk. What triggered it I guess is that there
> > might
> > > > be some changes in dependencies related to gradle and groovy. But, I
> am
> > > not
> > > > sure what the actual cause is and how it could be solved.
> > > >
> > > > Below is the image of the error that I have been facing. If anyone
> has
> > > any
> > > > idea of what this issue might be and how it could be solved, I will
> be
> > > > very grateful. Any help would be greatly appreciated.
> > > >
> > > > [image: image.png]
> > > >
> > > > Best regards
> > > > Anshul Goyal
> > > >
> > >
> > >
> > > --
> > > Kind Regards,
> > > Yashwant Dhakad
> > >
> >
>
>
> --
> Kind Regards,
> Yashwant Dhakad
>
