Hi All,
Again, sorry for the flood. I don't know what happened.
I finally received all the related messages "from the ML" between 17h00 and
17h40.
Luckily, I'm seing the image attached at
https://lists.apache.org/thread/yxmdxy81ywwhldg8ml4foqls5df0hy8s:
https://s.apache.org/zw3b8
So it eventually worked.
Michael,
I have not yet looked at a solution for .settings. That"s indeed absolutely
needed for JDK 17 to work properly in Eclipse (from 2023-03 version).
Leila,
sadly I tried to put a breakpoint at "CommunicationEventServices.groovy:489" without success (no stop) so far even when putting the stop at the top of
the sendEmailDated method.
I wonder if it's no due to the OFBIZ-12801 specific error in the context of
Codenarc...
Also I realised that the .classpath file I had before was approximatively the same than the new one generated using all the "Add" options (I see now 3
"Remove" ones)
The (kind="src") add for the groovy file was a mistake. It's only an interchange between
(kind="src") and (output="bin/main").
I though see this 3 lines at bottom:
<classpathentry kind="con" path="GROOVY_DSL_SUPPORT"/>
<classpathentry kind="con" path="GROOVY_SUPPORT"/>
<classpathentry kind="output" path="bin/default"/>
The last one was at top before. So only the 1st 2 are new in the file.
I'll try more :)
Jacques
Le 17/04/2023 à 12:11, Jacques Le Roux a écrit :
Le 15/04/2023 à 08:56, Jacques Le Roux a écrit :
Le 14/04/2023 à 21:53, Michael Brohl a écrit :
Additionally, I realized that the settings file is (re)generated by the Gradle eclipse task and the property vanished during the process. It would
be necessary to add the setting during the build.
Yes, as I could not get it working, I did not dig into that yet. As I said it's not stopping me to debug, but Groovy, so unrelated to JDK 17. I use
the last Eclipse ( 2023-03) and all last Eclipse plugins.
Good news at https://github.com/eclipse-jdt/eclipse.jdt/issues/57 closed :)
Maybe it's could also be due to a trick Leila gave me and I just applied.
Here is the copy of her message translated (Leila knows stuff but is a bit shy
I think ;)
<<On the other hand, in relation to your breakpoint concern, I know that it can come from the config of your project if in the classpath the groovy
libraries are not added (or the source is badly configured).
If you see options with add instead of remove:
- add groovy dsl support
- add groovy libraries to classpath>>
Hopefully the image will pass (I doubt). If not, it's only a matter of using the "Add" options from the project "Groovy" option (like you have
"team" there for instance )
Here is my answer to Leila so far:
<<Thank you Leila,
Indeed I remember now, I had already written about this problem but the
solution was much more tedious than what you propose.
It had to be done by hand. What I had done before and worked, then without
success since the Eclipse updates.
I just tried that and see that the .classpath file has been updated with added
(kind="src") in the groovy files, which I didn't have before.>>
HTH
Jacques
