Hi Michael, All,
Yes, of course. I'm an intuitive person, a good night is best to clarify
The issue I perceived and was not clear in my mind, is we have the informal concept of stable, next and trunk. That's initially a demo concept but it
has reality roots.
When we will release 24.09.01, so officially defines 24.09 as replacing 18.12 as stable,
it makes sense to create a new "next".
After soon 7 years of efforts, It would be better if OFBiz "next" branch eventually has replaced all Minilang by Groovy. As we did long ago for
Beanshell.*
There is also an implication for demo: what will be "next"?
As the "next" concept is informal, it's not a big deal. We could have no next
for a moment, or either use 24.09 as next (much easier).
As I'm more than often the demo maintainer I'd quite prefer to use 24.09 as
next, with an information about it of course.
Other ideas?
TIA
Jacques
* I'm not only an intuitive person, I'm also a perfectionist (some say maniac,
but results make me feel good ;)
The Beanshell word is still present in code once and the word bsh twice.
Should we not clean that?
Note: it seems the presence of the later in BirtServices::overrideReportForm
makes sense. Even if the flexible reports are now unavailable.
Because even if the Birt component is disabled and viewservlet.jar likely
dead for security reason (OFBIZ-5744)
flexible reports can still be used in a safe situation (no Internet
connections) . And I guess that presence does not bother anyone.
They also appears in log (that was that which initially questioned me):
2025-01-03 08:00:12,458 |Test worker |ScriptUtil |I| The following 3
scripting engines were found:
2025-01-03 08:00:12,459 |Test worker |ScriptUtil |I| Engine name:BeanShell
Engine
2025-01-03 08:00:12,459 |Test worker |ScriptUtil |I| Version: 1.0
2025-01-03 08:00:12,459 |Test worker |ScriptUtil |I| Language: BeanShell
2025-01-03 08:00:12,459 |Test worker |ScriptUtil |I| Engine supports the
following extensions:
2025-01-03 08:00:12,459 |Test worker |ScriptUtil |I| bsh
2025-01-03 08:00:12,459 |Test worker |ScriptUtil |I| java
2025-01-03 08:00:12,459 |Test worker |ScriptUtil |I| Engine has the
following short names:
2025-01-03 08:00:12,459 |Test worker |ScriptUtil |I| beanshell
2025-01-03 08:00:12,459 |Test worker |ScriptUtil |I| bsh
2025-01-03 08:00:12,460 |Test worker |ScriptUtil |I| java
As I did not find any import in code, that could be due to an external
dependencies. So hard, if even possible, to change.
<classpathentry
sourcepath="Z:/Gradle/caches/modules-2/files-2.1/org.apache-extras.beanshell/bsh/2.0b6/76a65f674e8f2df409934824c49ca338987c63ae/bsh-2.0b6-sources.jar"
kind="lib"
path="Z:/Gradle/caches/modules-2/files-2.1/org.apache-extras.beanshell/bsh/2.0b6/fb418f9b33a0b951e9a2978b4b6ee93b2707e72f/bsh-2.0b6.jar">
Is that perfectionism or mania? :D
Le 03/01/2025 à 17:49, Michael Brohl a écrit :
+1
The deprecation of mini lang is not a bug and hence no showstopper for a new
release IMO.
Best wishes for the new year,
Michael
Am 03.01.25 um 15:02 schrieb gil.portenseigne:
Hello Jacques, All,
I think releasing is a priority, reading the "why" list below
Waiting for those task parts that were taken several years ago could
lead us to be more and more late.
We will finish the effort in trunk for the next release, is that more
reasonable ?
Thanks
On 03/01/25 02:36, Jacques Le Roux wrote:
Hi Nicolas, All,
Best wishes for this new year to all too.
Nicolas, should we not way to close https://issues.apache.org/jira/browse/OFBIZ-9350, including https://issues.apache.org/jira/browse/OFBIZ-11232,
before?
Is that reasonable, maybe a lot of work still?
Jacques
Le 03/01/2025 à 11:54, Nicolas Malin a écrit :
Hello and greatest years for all !
The time go head fast and months pass by.
On this year begging I propose the plan de publication of 24.09.01 the
next week or two weeks the time to let any contributor the check this
news versions.
What do you thinks ?
Nicolas
Le 03/09/2024 à 15:21, Nicolas Malin a écrit :
Hello,
After going through this thread [1], I propose to go ahead with the
creation of the `release24` branch in a few weeks, and the release
of the next official version 2 or 3 weeks later.
Why:
* We've decided to leave release22.01 unpublished.
* The trunk has been stable for a long time (integration tests are working
well).
* The current version is over 6 years old
* If we wait another year for stabilization, there's a chance that
a lot of work-in-progress will be added, and as with release 22,
we'll probably miss the release stage.
* We have a lot of work to do on the trunk :D
If there are no major objection, I'll put the release24 branch creation to the
vote in a few days.
Nicolas
[1] https://lists.apache.org/thread/k903dobd1z0hm9qxo3prn8gzc71jrnx1
